[솔루션] Commvault Disaster Recovery (Replication)

Reference : https://documentation.commvault.com/11.24/essential/113647_disaster_recovery_and_replication.html

 

 

Overview

Commvault Disaster Recovery brings simplified, flexible, and scalable disaster recovery to your organization, providing you with DR automation, replication, and cost-optimized cloud data mobility.
With support for multiple data types – including applications, containers, virtual machines and hypervisors – along with multi-cloud integration, one-click failover, multi-tenancy support, live replication, and intuitive reporting, Commvault allows you to protect and recover your entire data environment, wherever it resides.
By enabling you to reuse your protected data through copy data management, Commvault provides a cost-effective means to extract more business value from your data, for such things as DevOps, testing, and analytics, helping to reduce storage costs and improve business outcomes.

 

 

How DR Works

The DR solution is based on replication.
When you create a replication group, the software automatically creates all the components—such as plans, groups, and schedules—that are required to maintain and run replication jobs for the workloads that you specify.

Replication jobs are controlled by replication groups that you can configure to update either periodically or continuously.

• The periodic replication method involves taking and cleaning up snapshots frequently on the source VM and requires less bandwidth.
  
  
• The continuous replication method continuously streams updates from source to destination VMs so that the destination VM is always current.
  You can use the continuous replication method with VMware-to-VMware replication groups.

Virtual Machine Replication

Choose the best disaster recovery configuration for your environment from a variety of technologies:

• Back up and replicate
• Snapshot replication
• Continuous replication using VMware VAIO

Database Replication

Recover from a disaster more quickly by using your backups to copy data to a secondary site.

File System Replication

Perform periodic replication from backups when they run or configure continuous replication for quicker disaster recovery:

• Back up and replicate
• Block-level replication

Replication Monitor

Use the central Replication Monitor to view the sync status of any replication pair for VMs, databases, and file systems and perform any of the available replication operations:

• Planned failover
• Unplanned failover
• Test failover
• Failback
• Others

 

---

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.

 

 

---

Cross-Platform Feature Support for Replication

 

Source and Destination Support

The following table shows supported cross-platform source and destination sites.

Feature Support

The following table shows cross-platform supported features for Command Center and CommCell Console.

 

 

---

Component Requirements for Primary and Secondary Sites

 

The primary and secondary sites for replication must have the required VMware environment, and must include Commvault components to manage operations and data movement.
The requirements are slightly different for on-premises deployments and VMware Cloud on AWS.

For an on-premises deployment, you can create a hypervisor configuration using the vCenter or a standalone ESX host.
For a destination site that is a VMware Cloud on AWS deployment, you can only use the VMware vCenter as the destination hypervisor.

If the destination site is a VMware Cloud on AWS deployment, the access node must be a virtual machine in the VMware Cloud.

 

The following table shows the components that must be present on the primary and destination sites:

 

 

---

Architecture

The Commvault Disaster Recovery solution uses hypervisor and Commvault components on the primary site and on the secondary (destination) site.

The Commvault deployment can reside on separate infrastructure or can be co-located with the primary site.
If the Commvault deployment is co-located with the primary site, configure CommCell Disaster Recovery to ensure that the Commvault deployment remains accessible if the primary site is unavailable.

 

The following diagram displays the DR solution architecture.

 

The following components are required on the primary and secondary sites:

• A hypervisor configuration.
  
  
• At least one access node with the Virtual Server package installed, to control replication operations.
  The access node connects to the hypervisor. The access node reads VM data from the source hypervisor and transfers it to the MediaAgent.
  
  
• At least one MediaAgent to manage data movement.
  The MediaAgent performs data deduplication, compression, encryption, and other tasks. The MediaAgent transfers data over a network (WAN) or SAN to the destination hypervisor, and writes data to the destination site.
  Data is read by an access node at the destination site to create the replicated VM.

 

The Commvault deployment can be a single server or multiple servers that include the following components:

• A CommServe host that runs the Commvault software and hosts the CommServe database
• A Web Server
• The Command Center, which provides operational control for the Disaster Recovery solution
• Temporary cache storage that stages virtual machine data for replication