> Essential > Disaster Recovery and Replication

Replication of Virtual Machines

Using Virtualization, you can configure virtual machines (VMs) or instances for replication to one or more secondary sites and configure replication groups for Commvault Disaster Recovery. Replication uses backups of primary VMs to create destination VMs and keeps destination VMs updated using continued incremental backups. Replication was formerly referred to as Live Sync.

The Commvault software includes multiple replication solutions. Choose the solution that most closely fits your needs based on your environment.

Solution

Technology used

Environment

Periodic (Classic)

Backup-based replication using recovery groups

  • You need to both back up and replicate data

  • Long-term data retention required

Periodic

Replication with replication groups

Replicate data using no intermediate storage

Continuous

VMware VAIO

  • RPO of less than 15 minutes required

  • VMware to VMware only

Recovery Options

The table below explains how to choose a DR site for Auto Recovery.

DR site Recovery options
Cloud Hot site recovery: A normal AUX copy process transfers data from the primary storage to a secondary storage copy near the DR site. As each backup arrives, the system creates and updates virtual DR disks, ensuring they remain synchronized with production. During failover, new VMs are spun up in the cloud, and these pre-created DR disks are attached, enabling rapid recovery.

Warm site recovery: A normal AUX copy process transfers data from the primary storage to a secondary storage copy near the DR site, but no DR disks or VMs are pre-created. When failover is initiated, DR disks and VMs are created using the latest data. This approach reduces operational cost but increases the recovery time objective.
On-premises Hot site recovery: A normal AUX copy process transfers data from the primary storage to a secondary storage copy near the DR site. As each backup arrives, the system creates and updates virtual DR disks and VMs, ensuring they remain synchronized with production. VMs are provisioned but remain idle. During failover, these VMs are turned on, enabling rapid recovery.

Warm site recovery: A normal AUX copy process transfers data from the primary storage to a secondary storage copy near the DR site, but no DR disks or VMs are pre-created. When failover is initiated, DR disks and VMs are created using the latest data. This approach reduces operational cost but increases the recovery time objective.

Loading...