Step by Step Directions for Techs
I don’t have to deal with this often, but it does pop up. What to do when replication fails? Here are some steps, but be certain to run them from the standby server.
First, determine if it failed by running this command in the shell.
Get-StorageGroupCopyStatus -Server [primary exchange server] -StandbyMachine [standby exchange server]
This will give you the status of all the databases. If they are suspended, you might be able to start it up again.
Resume-StorageGroupCopy -Server [primary exchange server]\[storage group name] -StandbyMachine [standby exchange server]
If it isn’t something that easy, we will need to suspend the database replication and then reseed it (be very certain to run these from the standby server).
Suspend-StorageGroupCopy -Identity [primary exchange server]\[storage group name] -StandbyMachine [standby exchange server]
(running Get-StorageGroupCopyStatus will show it is suspended)
Update-StorageGroupCopy -Identity [primary exchange server]\[storage group name] -StandbyMachine [standby exchange server] -DeleteExistingFiles
(this takes a bit before it finishes and keeps control of the window. If you have multiple databases, be prepared to wait).
There is a problem with Windows 2008 / Windows 2008 R2 that comes up when you try to browse locally. This seems to happen for me most frequently in lab environments. For example, I recently put together a proof of concept for ADFS to service a web farm / web server. When testing ADFS using hosts files and browsing to the ADFS site locally, I will get authentication errors. The solution is to disable the loopback check.
To do that: