HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

547 of 739
Application failback and restoration
If you have not done so already, launch the Storage Mirroring Recover Application
Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring
Recover Application Manager.
1. Before you failback, you may need to rebuild your source server. If necessary, refer
to instructions on rebuilding an Exchange or SQL source server.
2. There are two options for how to perform failback:
● If you selected DNS failover, you can use the Application Manager to
automate failback and restoration.
● If you selected Identity failover, you will need to use the manual processes
described in Identity failback, and restoration.
3. After you have failed back to the source, you can re-enable protection for your
application workload.
Note:
● When failing back, you may be prompted to supply the credentials of the
user in the Double-Take Admin group. You will need to enter local system
credentials in order to proceed with failback.
● The Failback button may not become active right away after completing a
failover. This is resolved by restarting the Application Manager.
● If you close the Application Manager while failing back to the original
Exchange production server, you may have to manually run the post_
restore.bat file (located in the source’s Storge Mirroring directory). This
.bat file starts the Exchange services and updates any public folders
originally hosted by the source.
● If you have deselected any Exchange mail stores prior to failover, an error
message will appear during failback stating that there were potential
errors (i.e., unpaired mailstores). This message can be ignored since the
mailstores were not failed over in the first place.
● If you create a new mailstore on the target while the source is failed over,
upon failback an error will appear stating that there is an unpaired
mailstore. The Application Manager will not automatically move the new
mailstore and users back to the source.
● During failback, mail sent to public folders may be routed to the target
server after Exchange is shut down, which will result in that mail being
stuck in the queue. Care should be taken to ensure that mail is not sent to
public folders until the failback process is complete.
● If the source is an Exchange 2007 CCR, LCR, or SCC cluster, after