we are going to make major changes to our domain infrastructure and want to know if this the right procedure for moving Unity.
Let's call our current domain X which is where our Unity 2.4.6(161) server and the rest of our infrastructure is residing and working correctly. X is a child domain right now. We want to promote it to a parent. What the domain admins are going to do is Create a new domain Y, migrate all the existing servers etc to the new Domain Y, turn off domain X and then rename domain Y back to X. Assuming all that works, we know that Unity will not support a domain move like that.
We purchased two brand new Unity 3.1(6) servers and have been testing them in parallel with the 2.4 server in Domain X. What we plan to do is export all of the users from 2.4.6 and when all of the Domain stuff is completed, we will rebuild the new 3.1(6) servers from scratch in the new Domain X (which is now a parent but had the same name as before) then reimport the 2.4.6 users.
Has anyone done this before and can anyone offer suggestions as to whether it will work.
First thing, unless you're doing Windows2k3 domains, you can't rename domains.
If you're migrating to a new domain, the easiest thing to do is upgrade the 2.4.6 box to 3.1.6. Then take a dirt backup of the 3.1.6 system. Build the new domain, build the new 3.1.6 unity boxes in the new domain, and then do the dirt import.
I trust moving to different domains with DIRT more than I do the fulldb import/export for 2.4.6.
I was just looking at the Upgrading a Cisco Unity 2.x System to version 3.1 document and you can't upgrade directly to 3.1. According to the document, the procedure is to export the 2.4.6 database, uninstall 2.4.6, install 3.x, then reimport the database. Can the DiRT tool be used in place of the database export on 2.4.6?
No, DiRT only works with 3.1(2) and later.
The database was competely redone between 2.x and 3.x/4.x systems - to upgrade from 2.x you have to do the export/import using FullDBImport/Export if you want to save your data.
The install guides for 3.0/3.1/4.0(x) all cover how to upgrade from 2.x using FullDBImport/Export. You can do a direct import from 2.x to 4.0(2) and earlier - for 4.0(3) and later you'll have to do a "two hop" migration.
I've had a few customers use this to move from voice mail only to unified messaging. Of course, this was for users who didn't already have mailboxes in their corporate exchange servers.
Dirt doesn't replace the 2.4.6 fulldbimport/export. In fact, Dirt doesn't work with anything older than 3.1. Dirt is meant primarily as a disaster recovery tool that just so happens to be good for migrations like this (as long as the unity version is 3.1 or newer). Review the Dirt help file for the dirty lowdown.
Ok so we have to use the fulldbimport/export tool. Should the procedure of exporting the db, unistalling Unity in the current domain, then rebuilding the 3.x servers from scratch in the new domain and importing the db work?
I've never tried it like that. Again, I feel safer doing the fulldbimport/export while the box is in the same domain. Once I've upgraded and verified there aren't any problems (run dbwalker during this testing), I'd run DiRT backup. Then I'd uninstall unity (to clean up the old domain), remove the box from the old domain, move it to the new domain, reinstall Unity, and finally do the DiRT restore.