{{ $t('productDocDetail.updateTime') }}: 2025-12-18

Introduction

You can configure DR policies, including backup schedule, transmission frequency, and other settings, for VMs of web systems, app systems, and database systems with different RPO requirements to safeguard data based on different protection levels.

Precautions

1. Do not use file datastores to store IO activity logs of CDP.

2. Store IO activity logs and DR data on the secondary site in the same datastore.
3. The silent backup function supports only the following Windows versions.

4. If a DR policy has silent backup enabled, if the VMs do not support silent backup or silent backup fails, a non-silent backup is created. When the system creates a non-silent backup, the operation is recorded in the operation logs.
5. Silent backup supports NTFS file system consistency and app consistency if the apps support silent backup.
6. To use the silent backup function as expected, make sure that the following Windows system services on which the function relies are normal:

a. The COM+ System Application service is started, and its startup type is Manual.

b. The COM+ Event System service is started, and its startup type is Automatic.

c. The Volume Shadow Copy service is not running, and its startup type is Manual.

Prerequisites

1. The backup repositories of the primary and secondary sites are planned and configured.

2. DR sites and links are configured.
3. SCP V6.9.0 and later support silent backup. Before you enable the quiesce guest file system function, make sure that vmTools is installed on the VMs and the VMs are in the running state.

Procedure

1. Go to Resources > Disaster Recovery > Disaster Recovery > DR Policy and click New.

2. Configure a DR policy:

①Enter a name for the DR policy.

②Select the applicable scope of the policy.

③Select the primary site.

④Select the secondary site.

⑤Select the protected VMs.

⑥Set the RPO. An RPO defines the acceptable amount of data loss when an application goes down. Important data usually requires a shorter RPO to back up and sync data more frequently. However, this increases the loads on the production environment and network.

⑦Configure the remote backup repository. In most cases, the backup repository of the secondary site is selected.

⑧Configure local backup. The local backup interval must be shorter than the RPO. When the RPO is no longer than 1 hour, you can select only CDP for local backup.

⑨Configure the backup repository of the primary site.

⑩When CDP is selected for local backup, you need to specify the datastore used to store IO activity logs. It is recommended to select a non-production datastore. You can select a virtual datastore. Enable or disable the quiesce guest file system function based on your business requirement.

3. Click Advanced on the right of Disaster Recovery. Then, you can specify whether to compress data before transmission, select the RP retention method, and set the alert threshold.

4. Create different DR policies for OA systems, apps, and databases to meet different RPOs. After DR policies are created, you can select a DR policy and click Execute to perform first-time data backup and DR data transmission. You can also use the replica seed function to export the full data of VMs on the primary site and import the data to the secondary site to complete first-time data backup and DR data transmission. After you complete the configuration, click the green button to enable or disable the DR policy.
5. In the Advanced pop-up window, you can configure different DR limits for different resource pools. You can specify the maximum number of concurrent backup transmission tasks for transmitting DR data from the primary site to the secondary site, the maximum number of concurrent backup tasks for backing up VMs on the site, and the maximum number of concurrent backup merging tasks that can be triggered on multiple VMs.