I am almost done rebuilding my VM environment and I will test again and post any errors. Below are the steps I wil be following to fail back to the production data center.
All clients are currently connected to and running off the SCR server.
Process to failback to production.
Power on the two CCR nodes in the production datacenter
Dismount the databases and delete all log and edb files but not the Storage Groups or Databases
Remove CMS using the command setup.com /ClearLocalCMS /CMSName:exchcluster
Enable Storage Group copy from the SCR back to the production server
Note, this is where problems first seem to appear. After enabling the Storage Group copy, a check of the status shows the copy is disabled instead of initializing. If I leave it long enough, it eventually goes to a Healthy state withou doing anything but its strange.
To switch back over to production,
Dismount the databases on the SCR server
To activate the copy on the production server, run the Restore Storage Group command.
This is where the error occurs. The -force parameter is not being used.
After examining the database using eseutil /mh, it shows a Dirty Shutdown state
Running eseutil to repair it works but the state remains Dirty Shutdown.
If you see anything wrong with the process, let me know before I actually implement it. Otherwise, I will proceed and post any errors.
Thanks
