Using ContinuousDataReplicator with Microsoft SQL Server

The following section provides the steps required to use CDR for data replication and recovery of Microsoft SQL Server data based on a single source and single destination. If your environment uses a different scenario, adjust your steps accordingly.

Before You Begin

• A full understanding of the following subjects will prove helpful:
  • Overview - ContinuousDataReplicator
  • Data Replication
  • Application Integration
  • Recovery Points
  • Recover Replicated Data

Data Replication and Consistent Recovery Points for Microsoft SQL Server

Required Capability: Capabilities and Permitted Actions

To use CDR to replicate Microsoft SQL Server data and create Consistent Recovery Points:

1. Select two computers on which to install CDR, one designated as the source computer, and one designated as the destination computer.
   • Verify that they both meet the System Requirements.
   • Install the ContinuousDataReplicator software for Windows on both computers.
2. For VSS, you may want to use separate volume for shadow storage.
3. Configure CDR to Replicate Application Data.
4. Create a Replication Set.
5. Configure Consistent Recovery Points for the SQL Server data; see Configure CDR Recovery Points.
6. Add a Replication Pair.
7. Start Data Replication Activity.
8. Create a Consistent Recovery Point Using CDR.

Additional Recommendations

• On both the source and destination computers, it is recommended that you Configure Throttling for CDR Replication Activities.
• It is recommended that you Configure Alerts. For more information, see Alerts.

  It is also recommended that you also see Space Check for the Quick Recovery and ContinuousDataReplicator Agents and configure the Disk Space Low alert to provide warning that the source computer is running out of disk space, which will ultimately cause replication activity to be System Aborted.

• Optionally, you can Configure CDR for Backups of Recovery Points.

  To perform backups of Recovery Points, you must also install the Windows File System iDataAgent on both the source and destination computers.

• Monitor Data Replication Activities.
• View the Recovery Point Creation History.
• Run and review the CDR Replication Job Summary Report.

Copyback of Microsoft SQL Server Data

SQL data is restored at the database level. While you can restore SQL data from a Recovery Point, a backup of a Recovery Point, or the Live Copy, these methods will not ensure consistency of the application data; only a restore from a Consistent Recovery Point, or a backup of one, will ensure consistency of application data. Copyback is recommended as the primary method of moving the replicated data back to the production SQL Server, in addition to restoring a backup of a Consistent Recovery Point where that is appropriate. To ensure application integrity, you must use Add App to create your Replication Pairs. (Refer to Add or Edit a Replication Pair and Application Integration.) Add App discovers the location of, not only user-defined databases (.mdf, .ndf, .ldf) but also any system databases on the client, which you can select for data replication.

For step-by-step instructions, see Copy Back SQL Data from a Consistent Recovery Point.

Additional Recommendations

• View the Recovery Point Copyback History.
• Run and review the CDR Copyback Job Summary Report.