Creating Mirrors
Solution Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-10
Remote Mirroring of an Oracle Database Using Data Replicator Software
For more information on how to create volumes, refer to the SANtricity Storage Manager
online help.
Creating Mirrors
Through SANshare Storage Partitioning, set up mirror relationships between the primary
site and the secondary site. Select the type of replication to be used, and configure any
consistency groups that might be required. Establish the mirrors, and allow the mirrors to
synchronize.
For more information on how to create mirrors, refer to the SANtricity Storage Manager
Remote Volume Mirroring Feature Guide.
Verifying the Installation
Some aspects of the installation verification are apparent. The SANtricity Storage
Manager shows you if the RVM Solution is working. Use the following process to verify
the installation.
1
After the volumes have been established, simulate a WAN link failure, and document
the results. This documentation will be used later during the customer knowledge
transfer.
2
Restore the link. Depending on the configuration, re-establish the mirrors, or allow for
automatic re-establishment.
3
Re-create the snapshots on the remote storage system.
4
Unmount (export) the volumes from the remote host if they are already known or
mounted.
Example for AIX:
# umount <mount point>
# varyoffvg <volume group>
# exportvg <volume group>
5
Copy the volume copies again from the Copy Manager interface.
6
After the volume copies have completed, disable the snapshots of the mirrored
volumes. Import the volumes back into the remote host OS.
7
After the volumes are mounted, make sure that the data on the volumes matches the
data up to the point in time where the snapshots were created. You can try to start the
remote database and see if the data files are available, but you might receive errors or
warnings that the data is not in a consistent state. This error occurs because you did
not suspend the database during the snapshot process. However, database suspension
does take place during the erm.ksh script execution.
