ApsaraDB RDS for SQL Server supports the snapshot backup feature. The snapshot backup method is faster and support larger amount of data than the physical backup method.
ApsaraDB RDS for SQL Server supports snapshot backup and physical backup. The data from physical backup files can be restored at a speed of up to 20 MB per second. Each physical backup supports up to 4 TB of data. If you want to restore a large amount of data, the restoration process may require a long period of time.
The snapshot backup feature is developed based on Volume Shadow Copy Service, which is provided by Microsoft. This feature allows you to periodically back up data snapshots on cloud disks and use the snapshots to quickly restore data to a point in time. For more information, see Volume Shadow Copy Service. The snapshot backup feature provides the following benefits:
Each snapshot backup supports up to 16 TB of data.
Snapshot backups provide faster restoration than physical backups. This significantly reduces the recovery time objective (RTO) and improves the fault tolerance of your database service.
Snapshot backups do not consume CPU or memory resources. Snapshot backups consume fewer I/O resources than physical backups. When snapshot backups are being created, the performance of your RDS instance is not significantly affected. For more information, see Troubleshoot high I/O issues on an ApsaraDB RDS for SQL Server instance and Troubleshoot the issues that cause high CPU utilization of an ApsaraDB RDS for SQL Server instance.
Comparison between snapshot backup and physical backup
Log backup frequency
Physical backups support the following log backup frequencies:
The log backup frequency is fixed as Every 30 Minutes.
The restoration is fast. The restoration speed varies based on the specifications of your RDS instance.
The restoration is extremely fast. The restoration speed is not affected by the amount of data. The speed of restoring data from a snapshot backup is higher than the speed of restoring data from a physical backup.
The log backup files that are used are generated between the point in time at which the most recent snapshot backup file is generated and the point in time to which you want to restore data.
Amount of data supported
Up to 4 TB of data is supported.
Up to 16 TB of data is supported.
Impact on instance performance
A large number of resources are consumed. This significantly affects the performance of your RDS instance. We recommend that you perform a physical backup during off-peak hours.
Only a small number of I/O resources are consumed. This does not significantly affect the performance of your RDS instance. You can perform a snapshot backup at any time.
Physical backup files can be downloaded.
Snapshot backup files cannot be downloaded.
The RDS instance meets the following requirements:
The RDS instance uses enhanced SSDs (ESSDs).
The RDS instance was created after January 01, 2021.
If the RDS instance runs RDS Basic Edition or RDS High-availability Edition, make sure that the cross-region backup feature is disabled. If the cross-region backup feature is enabled, you must disable it before you enable the snapshot backup feature. For more information, see Enable cross-region backups for a single RDS instance in the ApsaraDB RDS console.
The AliyunServiceRoleForDBS service-linked role is created by using your Alibaba Cloud account when you use the backup feature of ApsaraDB RDS for the first time. For more information, see How do I create a service-linked role for DBS?
If your RDS instance runs RDS Basic Edition or RDS High-availability Edition, the snapshot backup feature does not support cross-region backups. For more information, see Enable the cross-region backup feature for an ApsaraDB RDS for SQL Server instance.
Snapshot backup files cannot be downloaded.
Snapshots are created based on cloud disks instead of backup files. As a result, the snapshot backup feature does not support incremental backups.Note
Snapshots use the incremental snapshot chain mechanism. This mechanism retains the status of snapshot at each point in time. As a result, a snapshot backup only backs up the incremental and updated data on cloud disks.
Each RDS instance is allocated a free quota for backup storage. If the backup storage of your RDS instance does not exceed the free quota, you are not charged for backup storage. If the backup storage exceeds the free quota, you are charged for the excess storage that you use. For more information about the free quota and billing rules, see Billable items and pricing for the backup storage of an ApsaraDB RDS for SQL Server instance.
By default, an RDS instance uses the physical backup method. You can manually change the backup method to snapshot backup.
- Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the left-side navigation pane, click Backup and Restoration.
On the Backup Strategy tab of the Backup and Restoration page, click Edit in the Data Backup Settings section.
In the dialog box that appears, set the Backup Method parameter to Snapshot Backup and click Save.Note
After you change the backup method to Snapshot Backup, physical backups are not regularly performed. However, you can still perform a physical backup when you manually back up your RDS instance. For more information, see Back up an ApsaraDB RDS for SQL Server instance.Physical Backup
After you change the backup method to Snapshot Backup, the log backup frequency is fixed as Every 30 Minutes.
Creates a data backup for an instance.
Queries the data backups of an instance.
Queries the backup settings of an instance.
Modifies the backup settings of an instance.
Queries the backup tasks of an instance.
Queries the binary log files of an instance.