IBM Storage Copy Data Management (CDM)

Overview

IBM Storage Defender Copy Data Management (CDM) provides automated, policy-driven management of application-aware snapshots and replication across diverse storage environments. CDM enables data consumers to access required copies when and where they are needed while preventing proliferation of unnecessary or unused copies on valuable storage resources.

CDM orchestrates application-consistent backups across multiple platforms—including VMware, Oracle, Microsoft SQL Server, EPIC, SAP HANA, and various file systems—by leveraging storage-assisted snapshots.

Policy-Based Replication (PBR)

Overview

Policy-Based Replication (PBR) is a feature of IBM FlashSystem that facilitates replication from a source system to a target FlashSystem using policy-driven automation. PBR enhances disaster recovery (DR) capabilities by simplifying configuration and management through the use of policies and volume groups. Compared to traditional Remote Copy methods, PBR provides:

• Higher replication throughput

• Reduced latency

• Lower administrative overhead for configuration, lifecycle management, and monitoring

Until CDM version 2.2.26, backups could only be taken on the primary site of the storage network. Beginning with CDM version 2.2.27, CDM supports snapshot creation on FlashSystems configured as PBR replication targets. Snapshots created at the DR target site are crash-consistent and not application-consistent.

Policy-Based High Availability (PBHA)

Overview

IBM FlashSystem Policy-Based High Availability (PBHA) provides continuous and resilient access to data across two or more FlashSystems. PBHA uses replication policies to ensure data is automatically synchronized between systems, enabling applications to continue operating without interruption in the event of a site-level or system failure.

Configuring PBR Backups in IBM CDM

CDM supports backup operations on target FlashSystems configured for PBR. To configure PBR backups:

1. Create an SLA Policy:
   In the CDM interface, create a new Service Level Agreement (SLA) policy by selecting “Add Policy Based Replication (PBR)”.

2. Configure Additional Parameters:
   The SLA may include settings such as retention rules, safeguarded copies, and other replication-related parameters.

3. Attach the SLA to a Backup Job:
   Assign the SLA to a backup job to enable snapshot creation on the PBR target site.

When the backup job executes, CDM takes a snapshot of the replicated volume on the target FlashSystem.

Configuring PBHA 2-Site Backups in IBM CDM

PBHA backups follow a similar configuration workflow to PBR backups:

1. Create an SLA Policy:
   Select “Add Policy Based HA (PBHA)” when creating a new SLA policy.

2. Configure Additional Parameters:
   The SLA may include settings such as retention rules, safeguarded copies, and other replication-related parameters.

3. Attach the SLA to a Backup Job:
   Assign the SLA to enable snapshot operations across both FlashSystems participating in PBHA.

When a PBHA backup job runs, CDM creates snapshots that are available on both FlashSystems, ensuring high availability and resilience.

Configuring PBHA 3-Site Backups in IBM CDM

PBHA 3-site backups follow a similar configuration workflow to PBHA 2-site backups:

1. Create an SLA Policy:
   Select “Add Policy Based HA (PBHA)” when creating a new SLA policy.

2. Click 3-site checkbox:Click on the checkbox for "PBHA 3 Site"
3. Configure Additional Parameters:
   The SLA may include settings such as retention rules, safeguarded copies, and other replication-related parameters.

4. Attach the SLA to a Backup Job:
   Assign the SLA to enable snapshot operations across both FlashSystems participating in PBHA as well as on DR site FlashSystem

When a PBHA 3-Site backup job runs, CDM creates snapshots that are available on both FlashSystems, ensuring high availability and resilience. It will also create a snapshot on the DR site which can be used in case of application crash.

Restoring from PBR, PBHA Backups

To restore a backup from PBR, PBHA backup copies, user can select corresponding backup copy to restore from:

1. Navigate to Jobs, Click New and then Restore
2. Select source:Select the source(DB/FS/VM etc) which you want to restore
3. Navigate to "Copy":
   The copy section will show all the available backup copies to restore from along with the location of the copy. Refer to the screenshot given as example. User can select a copy available on HA systems or copy available on DR site. The site can be identified from column "Local". 
4. Select Destination:
   Select the destination to which you wish to restore to and save the job.

Once the job is created user can run the job to start restore.

Important points to note:

• Backup copies available on HA systems are Application Consistent.
• Backup copies available on DR site are Crash Consistent