Setting Up a Remote Copy Volume Group for Instances
1.Identify the virtual volumes that contain all database(s) and log files to be copied.
2.Create one primary Remote Copy volume group for this instance.
3.Add all virtual volumes that belong to this instance (all database and log files) to the primary Remote Copy volume group, and add the associated secondary virtual volumes to the secondary volume group on the Remote Copy backup server.
CAUTION: The relationship between instances and Remote Copy volume groups is 1:1.
•You must add files from only one instance to a primary Remote Copy volume group.
•You must add files from only one instance to one primary volume group.
◦Do not disperse files from one instance over multiple primary Remote Copy volume groups.
◦Do not add files from multiple instances to the same Remote Copy volume group.
If you do not ensure your system meets these requirements, you run the risk of data corruption and loss.
4.Synchronize the Remote Copy primary and secondary volume groups.
Recovering a SQL Database from a Remote Copy Backup Server
If a SQL database crashes at the site that holds the primary servers, you can recover the data from the Remote Copy backup server at the remote site as long as it is set up in an identical manner to the original production server.
NOTE: If you are performing a promote restore for volumes in a Synchronous Long Distance Remote Copy relationship, you must manually stop Remote Copy before initiating the volume promote restore.
1.On the backup server, use Recovery Manager to mount the virtual copy to the production server.
2.Log onto the production server and stop the SQL instance and its dependent services.
3.From the mounted virtual copy, manually copy all necessary database and log files to the corresponding database location.
4.Restart the SQL instance and its dependent services.
5.Log back onto the backup server and unmount the virtual copy.
Recovering a SQL Database from a Remote Copy Backup Server 75