Support for Remote Copy Modes and Policies
Recovery Manager supports Remote Copy in synchronous and asynchronous periodic mode.
•If you are using synchronous Remote Copy, the policies on the production system (the Remote Copy primary system) and the Remote Copy backup system must match. If the policies do not match, Recovery Manager cannot create virtual copies on a synchronous Remote Copy system.
However, if you manually specify an expiration value, a retention value, or both when you create a virtual copy, Recovery Manager creates the virtual copy on a synchronous Remote Copy system even if the policies on the Remote Copy primary and backup servers do not match.
NOTE: For more information on specifying values at the time you create virtual copies, see the description of the RMSql create command in “Using the Recovery Manager CLI” (page 42).
•If you are using asynchronous periodic Remote Copy, you can create Recovery Manager virtual copies even if policies on the servers do not match. If policies do not match, the virtual copies use the policies on the Remote Copy backup server.
•If you are running Remote Copy in a Synchronous Long Distance configuration, the virtual copies on the synchronous and asynchronous periodic Remote Copy backup servers do not have the exact same timestamp.
Support for GeoCluster for Microsoft Windows
Recovery Manager for SQL supports the use of both Remote Copy and HP 3PAR GeoCluster Software for Microsoft Windows:
•When synchronous mode Remote Copy is used with Recovery Manager for SQL and GeoCluster, you can use Recovery Manager to create virtual copies on both the production system (the Remote Copy primary system) and the Remote Copy backup system.
•When Synchronous Long Distance Remote Copy is used with Recovery Manager for SQL and GeoCluster, you can use Recovery Manager to create virtual copies on all three systems: the production system (the Remote Copy primary system), the synchronous mode Remote Copy backup system, and the asynchronous periodic mode Remote Copy backup system.
Setting Up Remote Copy Volume Groups
Setting Up a Remote Copy Volume Group for Databases
1.Identify the virtual volumes that contain the database and log files to be copied.
2.Create one (and only one) primary Remote Copy volume group per database.
NOTE: Recovery Manager supports multiple databases in one Remote Copy volume group if all the databases in the group belong to the same instance.
3.Add the virtual volumes belonging to the 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: Do not disperse files from one database over multiple primary Remote Copy volume groups. Recovery Manager does not support database and log files from one database existing in any location other than the one primary Remote Copy volume group created for that database.
4.Synchronize the Remote Copy primary and secondary volume groups.
74 Remote Copy for Recovery Manager