Unity 4.05 non failover migrating to new hardware and failover

Unanswered Question

I have a stand alone box no failover 4.05 vm only..

I have a new server I want to make primary and make the old box failover. I already have an Exchange 2003 box for the vm.

Plan:

-Upgrade current box to 4.2(1)

-The new hardware will be joined into their current domain as a 2003 os Unity vm only box and made primary.

-Run dirt on old box restore to new 4.2(1) box

- build the failover box and run failover sync...


I know there are alot more steps in between but my main question was..

When I build the new Primary box and I run through cuspa do i choose that this is going to be a primary box...and does that have any effect on when I restore from a non failover dirt.


I did accomplish this once but had some small issues like after they were all built the primary and failover box saw themselves as both primary until I ran the failover wizard.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Tommer Catlin Tue, 03/06/2007 - 15:54
User Badges:
  • Green, 3000 points or more

I would completely uninstall Failover and do the migration, then reinstall it on the new servers and setup/test. I have had bad luck with upgrading 4.05 to 4.2 with failover running.

Actions

This Discussion