Scenarios¶
CSBS supports one-off backup and periodic backup. A one-off backup job is manually created by users and takes effect for only one time. Periodic backup jobs are automatically driven by a user-defined backup policy.
Table 1 describes the two backup options.
Item | One-Off Backup | Periodic Backup |
|---|---|---|
Backup policy | None | Required |
Number of backup operations | Only one, manual | Periodic operations driven by the backup policy |
Backup name | User-defined backup name, which defaults to manualbk_xxxx | System-assigned backup name, which defaults to autobk_xxxx |
Backup method | Full backup at the first time and incremental backup subsequently, by default. CSBS allows you to use any backup (no matter it is a full or incremental one) to restore the full data of a server. | Full backup at the first time and incremental backup subsequently, by default. CSBS allows you to use any backup (no matter it is a full or incremental one) to restore the full data of a server. |
Application scenario | Executed before patching or upgrading the OS or upgrading an application on an ECS. A one-off backup can be used to restore an ECS to the original state in case the patching or upgrading fails. Executed before patching or upgrading the OS or upgrading an application on a server. A one-off backup can be used to restore a server to the original state in case the patching or upgrading fails. | Executed for routine maintenance of an ECS. The latest backup can be used to restore an ECS in case an unexpected failure or data loss occurs. |
You can also use the two backup options together if needed. For example, associate all ECSs with a backup policy to execute periodic backup of all ECSs, and manually perform one-off backups for the most important ECSs to further ensure those ECSs' data security, as shown in Figure 1.
Figure 1 Intermixed use of the two backup options¶