Posted on 2011-05-01
I'm testing a DR scenario but have run into a problem (note this is a lab environment)
Two nodes (Node1/Node2) running an Exchange 2007 CCR Cluster named CCRMBX.
There are two DR servers, DR1 and DR2. Both are configured as SCR targets for CCRMBX - the reason being, when I failed over, I wanted to have DR1 and DR2 running as quickly as possible as a CCR cluster, otherwise I'd need to fail over to CMS to DR1 and then reseed which could take a while.
I ran the following commands on DR1 (but for all SG's)
Restore-StorageGroupCopy "CCRMBX\SG1" -standbymachine DR
Couple of questions on this -
i. I'm still not entirely sure what the above command does, does it break SCR in preparation for DR1 hosting the SG's?
ii. I'm simulating a staged failover, should I need to dismount the databases first or will the -force switch do it? In which case, when I run the -force switch, I am prompted with a message stating that I need to dismount the DB first anyway. Interestingly, this is for SG2 - SG4 only, not SG1 for which the command ran ok.
iiii. I manually dismounted anyway, then ran the following command
setup.com /recovercms /cmsname:CCRMBX /cmsipaddress:192.168.1.20
I then recv a message stating that that DR2 is configured as an SCR target and I'd need to disable-storagegroupcopy. Does this mean that having two SCR targets for CCRMBX1 to avoid the reseed to start CCR on the DR nodes is not advisable?
iv. Since the setup.com /recovercms failed with the above error, how can I 'undo' the Restore-StorageGroupCopy command and set everything the way it was?