Failed to Execute a Backup Task

A manual or scheduled backup task fails.

Possible causes are listed here in order of their probability.

If the fault persists after you have ruled out one cause, move on to the next one.

Figure 1 Troubleshooting

**Table 1** Troubleshooting
Possible Cause	Solution
The vault capacity has been used up.	For detailed handling measures, see The Vault Capacity Has Been Used Up.
The vault is frozen because your account is in arrears.	Top up your account.
Other operations are being performed on the resource to be backed up.	For detailed handling measures, see Other Operations Are Being Performed on the Resource to Be Backed Up.
The system is busy.	Back up the data in off-peak hours or submit a service ticket.

Backup stops once the usage of the vault exceeds the upper limit. Take the following measures when the storage capacity of your vault is not enough:

Log in to CBR Console, locate the target vault, and delete unwanted backups by following instructions in Deleting a Backup.
If you want to retain the generated backups, expand the vault capacity. For details, see Expanding Vault Capacity.
If a backup policy has been applied to the vault, disable the backup policy or remove the policy from the vault. To disable the policy, see Disabling a Backup Policy. To remove the policy, see Removing a Policy from a Vault. Then, automatic backup is disabled, and the storage capacity of the vault will not change. You can also modify the backup policy or dissociate resources from the vault.

Automatic backup may fail when other operations, such as backup and restoration, are being performed on the target resource.

Log in to CBR Console and check whether the status of the target resource is Available or Running.
Figure 2 Checking the resource status
If yes, perform the backup again. If no, wait until the status of the target resource becomes Available or Running.