Back up data

Backup types

Backup type	Description
Level-1 backup (data backup)	Level-1 backups are created based on Redirect-on-Write (ROW) snapshots. These snapshots are stored on a cluster that supports distributed storage. The system does not replicate data when it saves a data block to a snapshot. When a data block is modified, the system saves one of the previous versions of the data block to a snapshot and creates a new data block that is redirected by the original data block. Therefore, you can create backups within a few seconds regardless of the size of your database storage. Compared with level-2 backups, it takes less time to create and restore level-1 backups. However, level-1 backups take up more storage space. PolarDB clusters are backed up and restored by using multi-threaded parallel processing. This improves efficiency. A level-1 backup (snapshot) can be restored or cloned at a rate of 1 TB every 40 minutes. Level-1 backups can be retained for 7 to 14 days. By default, the level-2 backup feature is enabled to ensure the data security. The following figure shows the total physical storage of level-1 backups. Warning To disable the backup feature, submit a ticket. After you disable this feature, you must bear the risks that may arise. For example, data loss may occur due to user errors.
Level-2 backup (data backup)	Level-2 backups are level-1 backups that are compressed and then stored in on-premises storage media. Level-2 backups are slower to restore than level-1 backups. However, the costs incurred for level-2 backups are lower than that of level-1 backups. Level-2 backups can be retained for 30 to 7,300 days. You can also enable the Retained Before Cluster Is Deleted feature. By default, the level-2 backup feature is disabled If you enable this feature, expired level-1 backups are transferred to on-premises storage media and stored as level-2 backups. The level-1 backups are transferred to level-2 backups at a rate of approximately 150 MB/s. Note If a level-1 backup expires before the task of transferring the previous level-1 backup to a level-2 backup is completed, the level-1 backup is deleted and is not transferred to a level-2 backup. For example, the system creates level-1 backups at 01:00 (UTC+8) every day for PolarDB clusters, and retains the level-1 backups for 24 hours. The system creates Level-1 Backup A at 01:00 (UTC+8) on January 1, and creates Level-1 Backup B at 01:00 (UTC+8) on January 2. Level-1 Backup A expires at 01:00 (UTC+8) on January 2 and starts to be transferred to a level-2 backup. However, Level-1 Backup A stores a large amount of data, and the transfer task is not completed by 01:00 (UTC+8) on January 3. Therefore, after Level-1 Backup B expires at 01:00 (UTC+8) on January 3, Level-1 Backup B is deleted and is not transferred to a level-2 backup.
Log backup	The log backup feature creates backups by updating redo logs to Object Storage Service (OSS) in parallel. Based on a full backup (snapshot) and redo logs, you can perform point-in-time recovery (PITR) for a PolarDB cluster. Log backups can avoid data loss caused by user errors. Log backups can be retained for 7 to 7,300 days. You can also enable the Retained Before Cluster Is Deleted feature to store data permanently. Note If you want to restore data to a specific time point, you must include the time required to replay the redo log files. It takes about 20 to 70 seconds to replay 1 GB of redo log data. The total restoration time is the sum of the time required to restore data based on backup sets and the time required to replay the redo log files.

Pricing

The backup and restore features of PolarBD are free of charge. Only storage fees are charged. Fees are calculated based on the storage consumed by backups (data and logs) and the retention period of these backups.

Billing methods

Backup methods

Configure automatic backup

1. Log on PolarDB console.
2. On the top of the page, select the region where the target cluster is located.
3. Find the target cluster and click the cluster ID to go to the Overview page.
4. In the left-side navigation pane, choose Settings and Management > Backup and Restore.
5. Click Backup Settings.
   
6. In the dialog box that appears, configure the following parameters.
   

   Parameter	Description
   Backup Method	The default value Snapshot Backup is used and cannot be changed.
   Backup Cycle	Specifies the backup cycle. Note To prevent data loss, automatic backup must be performed at least twice a week.
   Start Time	Specifies the start time for automatic backup.
   Level-1 Backups Retained For	Specifies the retention period for level-1 backups. Note Level-1 backups can be retained for 7 to 14 days.
   Level-2 Backup	Enables or disables the level-2 backup feature. Note By default, level-2 backup is disabled.
   Level-2 Backups Retained For	Specifies the retention period for level-2 backups. Note Level-2 backups can be retained for 30 to 7,300 days. To retain level-2 backups permanently, select Retained Before Cluster Is Deleted. The retention period parameter becomes unavailable after you select this option.
   Log Backups Retained For	Specifies the retention period for log backups. Note Log backups can be retained for 7 to 7,300 days. To retain log backups permanently, select Retained Before Cluster Is Deleted. The retention period parameter becomes unavailable after you select this option.
   When Cluster Is Deleted	Specifies the backup retention policy that applies when you delete a cluster. Retain All Backups Permanently: retains all backups after you delete a cluster. Retain Last Automatic Backup Permanently: retains the latest backup after you delete a cluster. Delete All Backups Immediately: does not retain any backup after you delete a cluster. Note If you select the Retain All Backups Permanently or Retain Last Automatic Backup Permanently policy, the system runs an automatic backup task to store all data when you delete a cluster. After you delete a cluster, level-1 backups are automatically transferred to level-2 backups. You can go to the Cluster Recycle page to view stored backups. For more information, see Cluster recycle bin.

7. After you configure backup settings, click OK.

Manually create a backup

1. Log on PolarDB console.
2. On the top of the page, select the region where the target cluster is located.
3. Find the target cluster and click the cluster ID to go to the Overview page.
4. In the left-side navigation pane, choose Settings and Management > Backup and Restore.
5. On the Backups tab, click Create Backup.
   
6. In the Create Backup dialog box, click OK.
   Note You can create up to three backups for a cluster.

Restore data

For more information, see Restore data.

FAQ

• Is the total physical storage space of level-1 backups equal to the size of all the snapshot backups?
  No, the total physical storage space of level-1 backups is not equal to the size of all the snapshot backups. The total physical storage space of level-1 backups is displayed in the ① section, as shown in the following figure.
• Why is the total physical storage space of level-1 backups smaller than the size of a single backup?

  The storage space of level-1 backups in PolarDB is measured by using two methods: logical storage space of each backup and physical storage space of all the backups. PolarDB uses snapshot chains to store level-1 backups. The same data blocks are replicated only once. Therefore, the physical storage space of all the level-1 backups is smaller than the logical storage space of all the level-1 backups. In some cases, the physical storage space of all the level-1 backups is even smaller than the logical storage space of a single backup.

• How are you billed for backups in PolarDB ?

  You are billed for the storage space of level-1 backups, level-2 backups, and log backups. By default, the level-1 backup and log backup features are enabled and the level-2 backup feature is disabled. Alibaba Cloud offers some storage space for free to store backup files.

• What is the billing method of level-1 backups?

  Storage fee per hour = (Total physical storage space of level-1 backups - Database storage usage × 50%) × Unit price per hour. For example, the total physical storage space of level-1 backups of a PolarDB database is 700 GB and the database storage usage is 1,000 GB. Then, the storage fee per hour is calculated based on the following formula: (700 GB - 500 GB) × USD 0.000464/GB = USD 0.0928.

• Can I use a storage package to deduct the storage fees of backup data?

  No, a storage package can be used to deduct only the storage fees of business data instead of backup data.

API reference