Creating a Replication Policy

Constraints

• You can set replication policies for server backup vaults and SFS Turbo backup vaults.
• A user can create a maximum of 32 replication policies in each region.
• If the automatic replication based on the replication policy fails, the replication task status is set to Failed. The replication task is automatically retried, and the task status is set to Running.

Procedure

1. Log in to the management console. Click in the upper left corner and select a region.
2. Click and choose Storage > Cloud Backup and Recovery.
3. Choose Policies in the navigation pane and click the Replication Policies tab. In the upper right corner, click Create Policy. Select Replication policy.
   Figure 1 Creating a replication policy

   

4. Set the replication policy parameters. Table 1 describes the parameters.

   Table 1 Replication policy parameters

   Parameter	Description	Example Value
   Type	Select a policy type. In this section, we select the replication policy.	Replication policy
   Name	Replication policy name. You can enter a custom name or use the default name policy_xxxx. The name can contain 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.	replication_policy
   Status	Whether to enable the replication policy. By default, this function is enabled. CBR replicates backups and deletes expired replicas only after a replication policy is enabled and applied to vaults.	Enabled
   Cross-Account Replication	Whether to enable cross-account replication. When cross-account replication is enabled, the source vault can be replicated to a target vault under another account, either in the same region or across regions. If this function is enabled, it cannot be disabled, and the destination replication vault identifier cannot be modified. You can modify other parameters. You can replicate backups to vaults of the same type that have cross-account replication enabled. For details, see Creating a Replication Vault with the Destination Account.	-
   Accounts In the Same Organization	This parameter is displayed only when cross-account replication is enabled. Determines whether the two accounts are in the same organization. You can enable cross-account replication for accounts that are in an organization or not in an organization. For details, see Inviting an Account to Join Your Organization. Enable this function if you need to replicate backups across accounts in the same organization. If this function is not enabled, you need to enter the name of the agency granted by the target account to the current account for replication.	-
   Destination Replication Vault Identifier	This parameter is displayed only when cross-account replication is enabled. Enter the ID of the cross-account replication vault of the same type in the destination region. All backups can be copied to the vault in the destination region. Replication traffic fees are generated for the source region. Replicated backups take up the same space as source backups. The target account needs to provide the vault ID to the account that initiates the replication. You can click the target vault in the vault list to go to the vault details page. The vault ID is displayed in the Basic Information area.	cross_account_copy:cbr:backup:<regionid>:<accountid>:<projectid>:vault:<vaultid>
   Agency Name	This parameter is displayed only when cross-account replication is enabled. Name of the agency granted by the target account to the current account for replication. If the source and destination accounts belong to different organizations, enter the name of the agency granted by the destination account to the current account.	AgencyName
   Replication Frequency	Select a replication frequency. By default, the replication task is executed automatically every Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday. Weekly Specifies on which days of each week the replication task will be executed. You can select multiple days. Day-based Specifies the interval (every 1 to 30 days) for executing the replication task. If you select day-based replication, the first replication is scheduled to be executed on the day when the replication policy is created. If the replication policy is created after the replication time, the first replication will be executed in the next replication period.	Every day
   Execution Time	Execution time of the replication policy in a day. The default replication time is 22:00. Replication tasks can be scheduled at the beginning of each hour, and you can select multiple hours. You can select multiple times, either on or off the hour, for replication. For times not on the hour, you can specify minutes from 0 to 59. For example, you can select a time that is not on the hour, such as 00:10 and 01:10. It is recommended that replication be performed during off-peak hours or when no services are running.	00:00, 02:00
   Target Cloud	This parameter is displayed only when cross-cloud replication is enabled. Select the target cloud to which the backup data is to be replicated. Only the clouds that support replication are displayed.	-
   Destination Region	Select the region to which the backup data is to be replicated. Only the regions that support replication will be displayed. For details about the regions that support cross-region replication, see Table 1. During cross-region replication: If the selected region contains only one project, you can directly select the region name. If the selected region has multiple projects, the default project of the region is preselected, but you can still select another project if needed.	AP-Bangkok
   Cross-Cloud Replication Credential Name	This parameter is displayed only when cross-cloud replication is enabled. Select the cross-cloud replication credential created for the target cloud. If no cross-cloud replication credential has been created, create one by referring to Creating Cross-Cloud Replication Credentials.	-
   Retention Rule	The rule that specifies how backup replicas will be retained in the destination region. By default, backup replicas are retained for one month. Backup quantity You can set the maximum number of backup replicas to retain for each resource. The value ranges from 2 to 99,999. You can also set long-term retention rules with advanced options. Long-term retention rules and quantity-based retention rules will be both applied. Day-based: 0–100 Weekly: 0–100 Monthly: 0–100 Yearly: 0–100 A resource may be replicated multiple times in a day. If day-based replication is configured, only the most recent backup replica of that day is retained. If you set Day-based to 5, the most recent backup replica of each of the last five days that have backup replicas generated will be retained and the earliest backup replicas will be deleted automatically. When multiple backup schedules (daily, weekly, monthly, yearly) are enabled, the system retains the combined union of all backups. For example, if Day-based is set to 5 and Weekly to 1, five backup replicas will be retained. The long-term retention rule and the quantity-based retention rule both apply. Time period Backups can be retained for one month, three months, six months, one year, or a user-defined period between 2 and 99,999 days. Permanent NOTE: The system automatically deletes the earliest and expired backup replicas every other day. This prevents exceeding the maximum number of backup replicas to retain or retaining any backup replica longer than the maximum retention period. CBR may experience delays in deleting expired backup replicas, but these delays are usually less than 24 hours. The retention rules apply only to auto-generated backup replicas; manual ones must be deleted manually. After a backup replica is used to create an image, the replica will not be deleted by the retention rule.	6 months

5. Click Create Now. After the replication policy is created, you can view it in the replication policy list.
6. Locate the desired vault and choose More > Apply Replication Policy to apply the replication policy to the vault. You can then view the applied replication policy on the vault details page.

   Data will be periodically replicated to the vault based on the policy.

Example

A user applies a replication policy to a vault in a given region at 11:00 a.m. on Thursday. According to this policy, backups will be replicated to the destination region at 02:00 a.m. every day, and only two backup replicas will be retained. According to this vault's backup policy, two backups are automatically generated at 00:00 every day. At 12:00 p.m. on Saturday, the replication vault will contain two backup replicas, which are replicated on Saturday. Backup replicas generated at 02:00 a.m. on Friday have been automatically deleted according to the replication policy.