Table Of Contents
Release Notes for Data Migration Assistant (DMA) Release 6.1(3a)
August 25, 2009
This document comprises the new features that are included and caveats that are resolved in Data Migration Assistant (DMA) Release 6.1(3a).
These release notes discuss the following topics:
•Important Notes, including
Data Migration Assistant (DMA) Release 6.1(3a) collects application data from Unified Communications Manager Releases 4.1(3), 4.2(3), or 4.3(2) system for upgrade to Cisco Unified Communications Manager Release 6.1(3). DMA exports data in the current Windows-based system (with SQL server database) that later gets imported to the Linux-based system (with Informix database).
Data Migration Assistant Release 6.1(3a) also collects application data from a Cisco Emergency Responder (CER) 1.3 system for upgrade to CER 2.0.
DMA saves the data that it exports in a tape archive (.tar) file in a location that you specify.
In addition to creating an export, DMA also performs a set of migration compatibility tests (data validation) on the exported Unified CM 4.x data
•If DMA discovers issues, either in the export itself, or in the data validation, DMA may report some type of "Failure." Do not consider such a message to be alarming.
•Even when DMA completes successfully, but especially if any "Error" or "Warning" occurs, the user should examine the generated messages. These messages may comprise
–Simply information about auto-data-correction that will be performed in the migration.
–Alerts to let you know the problems that DMA encountered as it attempted to check the data.
Generally, these problems require user expertise to determine how best to alter the data to remove the migration incompatibility.
Note You must install and run DMA Release 6.1(3a) on the Cisco Unified Communications Manager publisher server before you upgrade to Cisco Unified Communications Manager Release 6.1(3). If you make any configuration changes to Cisco Unified Communications Manager after you run DMA, the system does not retain these changes when you upgrade.
Note Do not consider the DMA Export a substitute for a system backup. You cannot use it to restore your Cisco Unified Communications Manager system in the unlikely event that you cannot complete your upgrade.
The following sections include important information that you should read prior to using to DMA 6.1(3a):
Before You Begin
Note Be aware that it is important that you run DMA early - possibly as early as weeks before the actual upgrade window to allow time to fix any noncompliant data.
A successful DMA run does not completely prepare you for migration and upgrade.
To understand critical tasks that must be completed, Cisco recommends that you read the "Before You Begin" section of the Data Migration Assistant User Guide Release 6.1(3) before you use DMA to export data from the Windows system.
To understand critical upgrade tasks that must be completed, Cisco also recommends that you refer to Upgrading to Cisco Unified Communications Manager Release 6.1(3) from Cisco Unified Communications Manager 4.x Releases.
Find these documents at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html.
Cisco Security Agent (CSA)
Before the DMA export begins, check the system CSA version by right-clicking the red CSA flag in the systray and, from the options that display, click About.
If the CSA version equals
•Less than 2.0(5), DMA stops CSA automatically during the export.
•Less than 3.0(3) but greater than 2.0(5), you must manually disable CSA before you run DMA.
•3.0(3) or higher, CSA can remain enabled while DMA runs.
Completion Status Recognition
DMA completion reflects four possible outcomes:
•Export Success & Validation Success
Note If your DMA run results in one of the following three outcomes, you must fix the inconsistencies and rerun DMA.
•Export Success & Validation Success but with Warnings
•Export Success & Validation Failure
You can access the DMA log files from the final status window. Use them to see what needs to be fixed.
Caveats That Are Resolved in Data Migration Assistant 6.1(3x)
This section contains a partial list of the defects that are resolved in this release of Data Migration Assistant. You can obtain a full list by reviewing and implementing the information in "UsingBug Toolkit" section.
•CSCsy54153 DMA pre-migration to CM 4.2.2 occurs for all incoming CM 4.0 versions.
•CSCso69307 DMA install does not populate SIP profile field on SIP trunks.
•CSCso77371 DMA DirExport failed to migrate PersonalAddressBook.
•CSCsq00704 DMA export fails to export IPMA users.
•CSCsq21832 End User to Device Mappings during DirExport contain multiple records.
•CSCsq71657 CIPC device configuration does not include More Softkey Timer and AutoCallSelect.
•CSCsr52317 Uninstalling DMA gets stuck at "Cleaningup ISM files..." window.
•CSCsl85152 Errors Log button opens an error file that displays no error.
•CSCsr06635 DMA export does not return proper error logs in a network outage scenario.
•CSCsr80272 DMA export fails without proper error log.
•CSCsq77338 During an upgrade from DMA 4.1.3 to 18.104.22.16801-63 user, multi device associations get lost.
New and Changed Information for Data Migration Assistant
The following sections explain the new and changed information for Data Migration Assistant:
New and Changed Information for Data Migration Assistant 6.1(3a)
No new or changed information exists for Data Migration Assistant 6.1(3a).
New and Changed Information for Data Migration Assistant 6.1(3)
The following sections contain information that is new or changed for Data Migration Assistant 6.1(3):
Data Migration Assistant Enhancements
Cisco Unified Communications Manager Release 6.1(3) includes the following Data Migration Assistant (DMA) enhancements. For more details, refer to the documents Data Migration Assistant User Guide 6.1(3) and Upgrading to Cisco Unified Communications Manager Release 6.1(3) from Cisco Unified Communications Manager 4.x Releases:
•The platformConfig.xml file that is generated by DMA supports upgrades for the first node (publisher database server) as well as for the subsequent nodes (subscribers). DMA provides a window where you can make detailed configuration specifications. Enter data at the DMA window Export > Answer File Generator.
•DMA provides a window where users can customize the behavior of DMA by specifying which types of logs to include in the output file. Enter data at the DMA window Export > Custom Options.
•DMA explicitly lists the pre-DMA export tasks. DMA provides both information and the automation of pre-export tasks, when possible, to ensure that the user knows what tasks to complete before DMA is run. Enter data at the DMA window Export > Pre-Export Tasks.
•DMA supports the generation of a license file upon successful DMA validation. The user can upload this license file to Cisco.com to get the actual license file ready for use. Go to the DMA window Export > Storage Location and specify a local directory destination for the license file licupgrade.lic. Specify the destination in the "Path Name" text box of the window "Destination Option for License File" field.
For More Information
•Data Migration Assistant User Guide Release 6.1(3)
Effects on CAR Data When You Upgrade Cisco Unified Communications Manager by Using Data Migration Assistant
If you do not need to carry over your CAR data to Cisco Unified Communications Manager 6.1(3), Cisco recommends that you purge the CAR data before you run the Data Migration Assistant (DMA). Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file.
Note Make sure that you purge any CAR records that are older than 180 days.
The Cisco Unified Communications Manager installation program limits the time in which CAR records migrate from the DMA TAR file to the CAR database on the upgraded system. The time limit that is allotted for the CAR component specifies 60 minutes. So, to facilitate migration of more data within the stipulated time, CAR uses the following logic:
•Data migration starts with the migration of billing records from the tbl_billing_data CSV file into the tbl_billing_data table of the CAR database. Data migration starts from the latest record and proceeds toward the oldest record in the CSV file. The billing data migration stops when no more billing records remain to be migrated or until the 60-minute time limit is reached, whichever occurs first.
•After the billing data migration, if time remains in the preallotted 60 minutes, CAR proceeds with migration of error records from the tbl_billing_error CSV file into the tbl_billing_error table of the CAR database. Data migration starts from the latest record and proceeds toward the oldest record in the CSV file. For each error record that is migrated, CAR migrates the data that corresponds to the error_record_id that exists in the tbl_error_id_map CSV file into the tbl_error_id_map table of the CAR database. This action ensures that error record migration stays consistent with data in the tbl_error_id_map. The migration process continues until no more data remains to migrate or until the 60-minute time limit gets reached, whichever occurs first.
•Whenever the time limit gets reached, CAR data migration stops, and the tbl_system_preferences of the CAR database get updated to reflect the data that is present in the upgraded system database.
Note If you upgrade from Cisco Unified Communications Manager 4.x, Cisco Unified Communications Manager saves the content of the Cisco Unified Communications Manager 4.x CAR database to CSV files. The Cisco Unified Communications Manager 4.x CAR database includes part of the CDR information. The Cisco Unified Communications Manager 4.x CDR database stores the complete information about CDRs. This database does not migrate. The Data Migration Tool uses the CAR database CSV files to migrate the CAR database. The system stores the CSV files in the /common/download/windows/car directory. The system stores the pregenerated reports in the /common/download/windows/pregenerated database. Because no corresponding CDR database exists in Cisco Unified Communications Manager 5.x and later releases, the complete CDR data does not migrate to the Cisco Unified Communications Manager 5.x or 6.x system. The Cisco Unified Communications Manager 5.x and 6.x CAR database schema gets extended to contain complete CDR information, but only for the new CDRs that the Cisco Unified Communications Manager 5.x and 6.x systems generate.
For More Information
•Data Migration Assistant User Guide Release 6.1(3)
Ensure CAR Administrator Privileges Are Restored After Upgrade
When you use DMA to upgrade Cisco Unified Communications Manager, CAR users no longer have CAR administrator privileges after the upgrade and become standard end users. You must reset the CAR administrator privileges after the upgrade. Refer to the "Configuring CAR Administrators, Managers, and Users" section in the CDR Analysis and Reporting Administration Guide for more information on how to configure CAR administrators.
For More Information
•Data Migration Assistant User Guide Release 6.1(3)
This section contains information about the caveats that this release of DMA resolves and information about how to create your own list of resolved and open caveats.
You can find the latest resolved caveat information for Data Migration Assistant by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip You need an account with Cisco.com to use the Bug Toolkit to find open and resolved caveats of any severity for any release.
To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•All severity level 1 or 2 bugs.
•Significant severity level 3 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Step 1 Acccess the Bug Toolkit, http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 If you are looking for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field and click Go.
Tip Click Help on the Bug Toolkit window for information about how to search for bugs, create saved searches, create bug groups, and so on.
Table 1 describes possible unexpected behaviors in Data Migration Assistant.
Tip For more information about an individual defect, click the associated Identifier in Table 1 to access the online record for that defect, including workarounds.
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1; however, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
Note Because defect status continually changes, be aware that Table 1 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the UsingBug Toolkit.
Tip Bug Toolkit requires that you have an account with Cisco.com. By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)