HP StorageWorks Storage Mirroring 5.0 application notes - High availability for Oracle 10g (T2558-88089, April 2008)

14
• Restore To—The name of the machine where the data will be restored. This is your temporary
source that has the unique IP address.
14. Identify the correct drive mappings for the data and any other restoration options necessary. For
detailed information on the restoration options, see the Storage Mirroring User’s Guide.
15. Verify that the selections you have made are correct and click Restore to begin the restoration. The
restoration procedure time will vary depending on the amount of data that you have to restore.
You can identify a restoration connection because it is enclosed in parenthesis ( ) and it has
_Restore appended to the end of the replication set name. The initial restoration is complete when
the Mirror Status is Idle. After the Mirror Status is Idle, the connection will continue replicating any
on-going data changes from the target to the source.
16. After the Mirror Status is Idle, schedule a time for failback. User downtime will begin once failback is
started, so select a time that will have minimal disruption on your users.
17. When you are ready, begin the failback process.
a. From the Failover Control Center, select the target that is currently standing in for the failed source.
b. Select the failed source and click Failback. The user downtime starts now. The pre-failback script
entered during the failover configuration stops the Oracle services on the target so that no
additional changes can be made.
c. When failback is complete, the post-failback script will be started. When the script is complete, you
will be prompted to determine if you want to continue monitoring the source server. DO NOT
choose Continue or Stop at this time.
18. Back in the Management Console, watch the restoration connection until activity has ended and
replication is in a Ready state. This will happen as the final data in queue, if any, is applied on the
source. The replication Ready state indicates replication is waiting for new incoming data changes.
There will not be any additional data changes because failback has released the source identity, so
users are no longer accessing their data.
19. Once replication is in a Ready state, disconnect the restoration connection from the target. This is the
connection enclosed in parenthesis () and it has _Restore appended to the end of the replication set
name.
20.Connect the source to the network.
a. On the source, change the IP address that you modified earlier back to its original address.
b. Enable any other NICs on the source.
c. Change the source name back to its original name and reboot, or restart the Workstation, Server,
and any other services you were prompted to stop.
21. Once the source is back online, users can reconnect to the source.
22.After the source is back online, select whether or not you want to continue monitoring this source
machine (Continue or Stop).
NOTE: The source must be online and Storage Mirroring must be running to ensure that the source
post-failback script can be started. If the source has not completed its boot process, the command to start
the script may be lost and the script will not be initiated.
23.After the restoration is complete, start the Oracle services on the source machine.
24.Reestablish the Storage Mirroring Oracle replication set connection.
At this time, your data is restored back to your source machine, the source machine is again the primary
Oracle server, and, if you selected to continue failover monitoring, the target is available to stand in for the
source in the event of a failure.