Guidelines for using IBM DB2 Universal Database (UDB) with HP StorageWorks Storage Mirroring (T2558-96335, June 2009)

The target server is now standing in for the source DB
Restore your data
If your source experiences a failure, such as a power, network, or disk failure, your target machine
will stand in for the source while you resolve the source machine issues. During the source machine
downtime, data is updated on the target machine. When your source machine is ready to come back
online, the data is no longer current and must be updated with the new data on the target machine.
1. Verify that your source machine is not connected to the network. If it is, disconnect it.
2. Resolve the source machine problem that caused the failure.
NOTE:
If you must rebuild your hard drive, continue with step 3.
If you do not need to rebuild your hard drive, verify that the Storage Mirroring connection on
the source has been disconnected (right-click the connection in the Storage Mirroring Management
Console and select Disconnect) and then continue with step 4.
3. If you must rebuild your hard drive, complete the following. If you do not need to rebuild your
hard drive, skip this step and continue with step 4.
a. Install Windows. Since your source machine is not connected to the network, go ahead and
use the sources original name and IP address.
b. Install Storage Mirroring using the installation defaults.
c. Install DB2 using the same drive and directory settings recorded in Install software on the
source, page 13
4. Verify that DB2 is not running on the source. The DB2 services must not be running at this time.
Depending on the type of failure, your services may be set to manual startup but could still be
running. Stop any DB2 services that are running.
5. On the target, select Start, Programs, Storage Mirroring, Failover Control Center.
6. Select the target machine that is currently standing in for the failed source.
7. Select the failed source and click Failback. The pre-fail back script entered during the failover
configuration stops the DB2 services on the target so that no additional changes can be made.
Sample Implementation18