3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
9.2 How it works
When users want to synchronize the data from the production site to secondary site, Recovery Manager for Microsoft SQL will leverage the VSS framework to freeze the I/O at the application level, and then allows the VSS provider to take a snapshot of the database and log volumes. Once the snapshot is taken, Remote Copy performs a synchronization on the data changes to the target volumes at the secondary site. After the synchronization is complete, the target server connected to the Inserv at the secondary site, creates a Virtual copy on the remote copy target volumes, and saves the information in its repository at the secondary site.
NOTE: The Target Server serves as the backup server at the secondary site. After synchronization has completed, a virtual copy will be created and managed by the Target Server at the secondary site.
NOTE: Virtual copy created on the primary site for Remote Copy purpose will be removed after synchronization has completed.
NOTE: In order for the Recovery Manager GUI to manage virtual copies from the remote target server, you need to register the SQL server using the exact server name and instance name. To perform restores at the remote target server, please refer to Recovering an SQL database from a Secondary Site on page 9.5.
9.2
How it works
