Replication

ContinuousDataReplicator (CDR)

CDR replicates data from a source computer to a destination computer. This is done in near real-time by logging all file write activity to a replication log in the source computer, including new files and changes to existing files. These replication logs are transferred to the destination computer and replayed, ensuring that the destination remains a nearly real-time replica of the source.

For more information about data replication, see Overview - ContinuousDataReplicator.

Database Replication

Keep up-to-date copies of production databases on alternate servers, thus minimizing down time in cases where the production database server has failed. The advantages of Warm Database Restore over a traditional restore scenario is that the database is always kept in a near ready state. In the case of disaster, users do not need to wait for the time it would take to restore the database in its entirety. Only the latest backup may need to be applied to the target database before turning the application over to use it.

For more information, see Replication Using Warm Database Restore - SQL Agent or Replication Using Warm Database Restore - MySQL Agent.

Live Sync for VMware

Live Sync can be used to create and maintain warm recovery sites for virtual machines running critical business applications.

The Live Sync feature enables incremental replication from a backup of a virtual machine (source VM) to a synced copy of the virtual machine (destination VM).  The Live Sync operation opens the destination VM and applies changes from the source VM backups since the last sync point.

You can replicate virtual machines to vCenter or to vCloud. When replicating to vCloud, you can specify the organization, virtual data center (vDC), vApp name, and vApp owner.

The Live Sync feature can initiate replication automatically after backups or on a scheduled basis (for example, daily or once a week), without requiring any additional action from users. Using backup data for replications minimizes the impact on the production workload by avoiding the need to read the source VM again for replication. In addition, in cases where corruption on the source VM is replicated to the destination VM, users can still recover a point-in-time version of the source VM from older backups.

For more information, see Live Sync Replication.