I want to replace the unity server hardware with another brand, so I can't do a mirror of the hard drives. I don't have a DAT drive in the server neither. What steps do I have to take to migrate unity from one server to another?
We're getting ready to do this ourselves. Is there any reason to need to worry about taking down relationshipd between the old unity server and the new one before doing this? Or is it okay if you just run the DIRT procedures, shut down the old one - install the new Unity server - run recovery - and archive the old server?
Also - Can't remember if I already asked this befor e- but we're planning to do this hardware replacemnt as part of a 3.1(5) to 4.0 upgrade - would it be better to upgrade to 4.0 on the currrent Unity and then run dirt and install the new server?
Or run dirt on the 3.15 box first, then bring the new box up to 3.15 and go to 4.0?
it's a good idea, although not necessary, to uninstall the old server first - you can just run DiRT restore on the new box without removing the old one though. It'll "stamp" all the objects in the directory to point to the new box so you can't just "hot swap" back to the old one or anything.
No real benefit to using DiRT on 3.15 vs 4.0(1) so you can do it in either order - just make sure in either case you run out to CiscoUnitytools.com and fetch the latest versions of DiRT backup and restore before rolling on it.
We'll go ahead and do it the right way and uninstall after grabbing the dirt image. Any need during the middle of that process to do any cleanup in AD or does DIRT restore handle any of that (aka any orphaned objects, etc) or does it pretty much re-utilize everything?
The only thing you need to do in AD is at the end of the Uninstall process - it puts up a dialog listing a few objects you need to go delete (i.e. the DLs, example admin and example subscriber for that box). Other than that you're good - DiRT will bind to the accounts in AD when you do the restore on the new box and it should be ready to roll.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...