beautypg.com

Application failback and restoration, Failing back an application workload – HP Storage Mirroring Software User Manual

Page 517

background image

Failback and restore

Page 516 of 677

Application failback and restoration

When protecting application workloads, your failback and restoration process will
depend on if you configured your application for identity or DNS failover.

l

Identity failover—If your application is configured for identity failover, you will
need to stop your application services and then you have the choice of restoring
and then failing back or failing back and then restoring. See

Failback and

restoration for applications configured for identity failover

.

l

DNS failover—If your application is configured for DNS failover, you will perform
your restoration and then failback. See

Restoring then failing back applications

configured for DNS failover

.

Exchange Note: If your source failure was such that you have to completely rebuild

your source before you can failback and restore, use the following
steps as a guideline for rebuilding the source server.

1. Install Windows, and any service packs, using the same name and

IP address configuration as the original source, and then join the
domain. See your Windows documentation for more information.

2. Login as a domain administrator or an equivalent account with full

Exchange Administrator rights.

3. Install Exchange using the /DisasterRecovery switch, making sure

that all of the components will be installed to the same location as
the original source and the Action is set to Disaster Recovery. In
addition, set the Microsoft Exchange Messaging and Collaboration
Services and Microsoft Exchange System Management Tools to
Disaster Recovery. You can disregard informational messages
related to recovering from tape backup. See your Exchange
documentation for more information.

4. Install any Exchange service packs or patches.

5. Install Storage Mirroring Recover.

6. Copy the files exchfailover.exe and post_restore_sourcename_

target_name.bat from the target to the new source, and then
continue with failback and restoration.

SQL Note:

If your source failure was such that you have to completely rebuild

your source before you can failback and restore, use the following