I am working on a project that involves an upgrade for a Call Manager server version 4.1.3 to CUCM 7.1.3a.
I ran the Data Migration Assistant, but unfortunately, since I didn't had the proper information at the time, I got the DMA File for version 7.1.2.
My question is: Is there any possible way to somehow "translate" the DMA file I got on version 7.1.2 to 7.1.3a???, if not, what other option do I have besides running the DMA tool on the old server again (this server is in production, so it is kind of complicated to restart it after the DMA tool installation)???.
Because the DMA process is so key to the overall migration, I
would start over with the DMA 7.1(3) version. The pain of
scheduling another "maintenance window" to re-run DMA may
be well worth it vs the pain of an unsuccessful upgrade. You may want
to open a TAC case to verifiy the data integrity if you don't start over.
The release notes for DMA do indicate these notes related to the
"Major" CUCM version requirement;
Use this document if you are running supported versions of Cisco Unified CallManager and are ready to upgrade to Cisco Unified Communications Manager 7.1(1x). The DMA version number that you use must match the major version of Cisco Unified Communications Manager. [For example, if you were upgrading to Cisco Unified Communications Manager 7.0(1a), you could use DMA Release 7.0(1) or DMA Release 7.0(1a).]
Tip If you have installed an (a), (b), (c), (and so on), version of Cisco Unified Communications Manager, you only need to match the DMA major version number. For example, if you had Cisco Unified Communications Manager Release 6.1(1b), you could use DMA Release 6.1(1a).
So it depends on what is considered a "Major" version here.
The other things to consider here, are the Bug caveats fixed in DMA 7.1(3);
Caveats That Are Resolved in Data Migration Assistant 7.1(3)
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 "Using Bug Toolkit" section
If you do decide to remove the DMA 7.1(2) version, here are the steps;
You must remove DMA and the applications that are installed with it before installing another DMA version. See the following sections for instructions:
•"Stopping DMA" section
•"Uninstalling DMA" task
Note To uninstall previous versions of DMA, refer to uninstall instructions in the guide for that release. This section applies only to uninstalling DMA 7.1(2). Stopping DMA
Ensure that DMA is not running on your system. DMA, a server application that is controlled through a browser interface, can continue to run after you close the browser. To verify that you have stopped DMA, perform the following procedure:
Step 2 When prompted, log in as the Windows Administrator.
The Security Alert window displays. To continue running DMA, you must click Yes.
The Data Migration Assistant Home window displays.
Step 3 If you are running DMA on a secure server, the Warning - Security window displays. It asks whether you want to accept a certificate from the secure server to exchange encrypted information.
To continue running DMA, you must click either Yes or Always. If you click Always, this window will not display again when you access this server.
The Data Migration Assistant Home window displays.
Step 4 From the Data Migration Assistant menu bar, choose Export > Export Data.
The Export Data window displays.
Step 5 Click the View Status link.
Step 6 Review the status to determine whether the last execution completed.
If you are not sure whether the DMA process completed, you can cancel the DMA operation by choosing Start > Programs > Cisco DMA > Cancel Export. The system could require several minutes to cancel the export process.
Step 7 Continue the DMA removal, as described in the "Uninstalling DMA" section. Uninstalling DMA
Note To uninstall previous versions of DMA, refer to uninstall instructions in the guide for that release. This section applies only to uninstalling DMA 7.1(2).
Step 2 From the Add/Remove Programs Window, choose Cisco Data Migration Assistant.
Step 3 Click Remove.
Step 4 Choose Yes to uninstall.
Step 5 Make sure that a restart of the server is possible and choose Yes to restart the server.
Note If you use Virtual Network Computing (VNC) to access your server, you may want to remotely restart the server by choosing No and restarting the server by using the VNC facility that sends Ctrl-Alt-Delete to the server.
sorry rob! I tried to click 5 starts, but it somehow hit 4 stars... my bad!
But Rob is correct... you will need to re-install the correct DMA version on your 4.x publisher,reboot, and then run DMA again. You can not use DMA 7.12 for a 7.13 install. The databases are slightly different.
Probably need to schedule another window, uninstall 7.12, then reboot. Install 7.13 DMA, reboot. Then finally run the DMA for 7.13.
Your other option here is to boot off a 7.1 disc and use your current DMA TAR file. Then afterwards, upgrade to 7.13x. You can use *PRE* 7.13 boot disc and then apply the 7.12 release as you load the publisher.
If it was me, id probably do the DMA again. Its not that bad. I run it remotely for my clients at night. Pop the TV on, and watch the pretty progress bars and screen refreshes
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...