{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.2
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","Backup Policy Configuration")}}

Backup Policy Configuration

{{ $t('productDocDetail.updateTime') }}: 2026-01-01

To ensure the best backup and recovery performance, as well as RPO and RTO, when there are many virtual machines to be backed up, the following suggestions are made:

1. It is recommended to deploy multiple XBSA Apps. If transmission encryption is enabled, the number of backup tasks of each XBSA App at the same time should be equal to the number of CPU cores reserved for backup by the NetBackup client; if transmission encryption is not enabled, the number of tasks that each XBSA App can handle is recommended to be calculated according to "network bandwidth / expected single cloud host backup rate". For example, for a NetBackup client connected to 10000Mbps, if a backup rate of 200Mb/s is expected, the XBSA App supports a maximum of 5 virtual machines to be backed up at the same time. The final backup rate is determined by a combination of factors such as agentless backup configuration, network transmission bandwidth, and storage IO performance.

2. It is recommended to create multiple backup strategies. Each backup strategy selects a certain number of cloud hosts (the number depends on the actual concurrent capability of the XBSA

App client) and associates them with different XBSA Apps, so that the cloud hosts are dispersed as much as possible on different XBSA Apps to improve backup and recovery performance.

3. Set a reasonable full backup frequency for the backup strategy. Under the premise of comprehensive storage space utilization, control the backup chain length within a reasonable range to ensure that as few backup points as possible are merged when restoring backup data. Whether the RTO is within expectations can be measured by the amount of data restored, the number of backup points, and the length of recovery.