Transferring Backups to a Specified OBS Bucket

Scenarios

You can transfer generated automated full backups, manual full backups, and incremental backups to specified OBS buckets.

Constraints

• Federated accounts cannot be used to transfer backups to OBS.
• Only physical backup files can be transferred to a specified OBS bucket.
• When being transferred to an OBS bucket, encrypted backups will be decrypted first.
• The maximum size of a single backup that can be transferred each time is 10 TB. If this limit is exceeded, the transfer task will fail.
• Ensure that the target OBS bucket is available and has enough space. Otherwise, the transfer task will fail.
• Expired or deleted backups will not be transferred. Set an appropriate backup retention period.
• Deleting the instance during a transfer will cause the transfer task to fail.
• Stopping or rebooting the instance, or changing its instance class during the transfer may cause the transfer task to fail.
• Permissions and system roles must be configured. For details, see Permissions.
• The transfer speed depends on the OBS upload rate, and the estimated time required may fluctuate.
• Backups transferred to OBS cannot be directly restored to RDS for SQL Server instances.

Billing

Transferring backups to OBS buckets will incur fees. For details, see OBS Pricing Details.

Procedure

1. Log in to the RDS console.
2. Click in the upper left corner and select a region.
3. On the Instances page, click the target instance name to go to the Summary page.
4. In the navigation pane, choose Backups & Restorations.
5. Select the backups to be transferred and click Transfer to OBS Bucket.
6. In the displayed dialog box, select an OBS bucket, specify a folder directory, and click OK.
   Figure 1 Transfer to OBS Bucket
   

7. After the task is submitted, return to the Instances page, choose Backups > Transfer Tasks, and check the execution result of the manual transfer task.
   Figure 2 Checking transfer tasks