Troubleshooting disaster recovery

You can use the following guidelines to troubleshoot disaster recovery.

If any of the databases do not come back online after disaster recovery is performed due to missing logs, you might need to run a PIT restore from SnapManager for Exchange in the disaster recovery if the missing logs cannot be recovered.
Retrying the recovery part should also address overlapped IO in progress errors in CMS recovery.
If any error is encountered in any of the recovery tasks, after resolving the error the operation can be rerun. The tasks that are already complete can be excluded in the rerun, if needed.
For Microsoft 2008 systems, ensure that the machine accounts for the cluster is configured with full permissions on the Microsoft Exchange computer object.
As part of the recovery, the local DNS cache in the disaster recovery host will be flushed.
The local cache in the outlook clients might still have an old IP addresses for the Microsoft Exchange netname. ipconfig/flushdns can be pushed through a groupdate to flush the local DNS cache after a disaster recovery.