I have a TAC case open about this but I figured I could double my chances of finding a resolution by bringing it up here.
The issue I am having is that DiRT Restore locks up and makes no more progress once it begins the directory synchronization step. A quick look in task manager shows DiRT as *Not Responding*. I have left it running as is without touching the server over the weekend, thinking something might be happening in the background, but upon arriving in the morning at the beginning of the week DiRT restore is in the same condition it was in when I left. Also a check of the DiRT Recovery Restore log file shows that it just stops, and records no errors.
A little background info for what we're trying to do:
We have a total of 8 Unity 4.0(3) servers in production, 4 primary and 4 secondary. Each pair of Unity servers has an off-box message store(exchange 2000). Everything running on a Windows 2000 OS. Currently the 4 pairs of servers are located in 3 sites, 2 of the pairs being in the larger site. The 3 sites are each on their own voicemail-only domain.
We are looking to upgrade to 8 Unity 5.0(1) servers, 4 primary and 4 secondary, with off-box exchange 2003 message stores. Everything running on Windows 2003 OS. Same setup as before, just newer versions of everything running on new hardware. One major difference will be that all 3 sites will be sharing the same voicemail-only domain.
In order to achieve this upgrade I have built 8 brand new Unity 5.0(1) servers, and their associated exchange 2003 message stores, on Windows 2003 OS, in our lab. I have also built 4 temporary Unity 4.0(3) servers running on Windows 2000 OS (because it won't let me install Unity 4.0(3) on windows 2003).
The overall objective is to DiRT backup each of the 4 live systems including messages, then DiRT restore the config and messages to the temporary Unity 4.0(3) servers. Once the restore has run and any errors have been accounted for, we will upgrade the box to Unity 5.0(1). When the upgrade is complete we will run a new DiRT backup not including messages(they will already have been restored to the proper message store) and DiRT restore this to the freshly built Unity 5.0(1) server running Windows 2003. Once that's done we'll implement failover between each pair of servers.
Now we have have been able to do this successfully for both of the smaller sites that only have a single pair of Unity servers. We have restored them to the temporary server, upgraded Unity on that server, then backed up and restored to the permanent Unity 5.0(1) server. No major errors, everything works great. For reference they have between 400-700 subscriber accounts.
Where we run into the problem is when trying to DiRT restore either of the 2 larger systems, each of which has around 3,000 subscriber accounts. I'll include the DbWalker logs from each existing server, as well as the DiRT backup logs, and the restore logs that just freeze, for anyone that wants to take a look at them.
So I guess my question is, has anyone run into DiRT Restore just locking up like that? If so were you able to discover the cause and work around it?
Also, from reading the help file my understanding is that COBRAS can only be used to backup/restore Unity 4.0(5) and up. Am I incorrect? Can I try using it instead of DiRT to backup my Unity 4.0(3) systems?
