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

732 of 739
3. Repeat that process, modifying the other three files from earlier, but this time make
the modifications on the target copy of the file. Save the changes.
If desired, you can also test the target data as you did earlier. You can test user data
using the associated application, and you can save the changes if desired. If you want to
test application data, start the application services on the target, and test the application
data by using clients to connect to the application. Because the source is now failed
over, you will not need to worry about pausing the target or configuring clients to access
the application from the target. The clients will continue to access the source, which is
now being handled by the target machine.
10. Initiating failback
When failover occurs, a source machine has failed. The steps below must be used to
complete failback, which releases the source identity from the target.
1. If this were a real failure scenario and not an evaluation, you would first verify that
your source machine is not connected to the network. If it is, you would have to
disconnect it from the network.
2. Next you would resolve the source machine problem that caused the failure.
Warning: Do not connect the source machine to the network at this time.
3. In the Failover Control Center, select the target that is currently standing in for the
failed source.
4. Select the failed source and click Failback.