Stopping a Backup

Scenarios

You can stop a backup that is being created and then delete it.

Constraints

• You can stop an automated full backup or manual full backup that is being created.
• After a backup is stopped, it will not be billed and can be deleted.
• A backup that is being copied cannot be stopped.
• This function can only be used when there is much data to be backed up and creating the backup takes too long.
• This function stops the backup command. If the backup command has already finished when the stop request is delivered, but the backup task flow is still ongoing due to subsequent actions, the backup task flow status will not be affected by the stop request.
• You are advised not to stop the first automated full backup after an instance is changed or restored. Forcibly stopping that backup may cause incremental and differential backups between the current time and the next automated full backup to fail, and point-in-time recovery (PITR) may be unavailable. Do not stop that backup unless absolutely necessary.

Stopping a Full Backup

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.
4. In the navigation pane on the left, choose Backups & Restorations.
5. On the Full Backups tab page, click Stop Full Backup.
6. In the displayed dialog box, click Auto Enter to enter YES, and click OK.
   Figure 1 Stopping a Backup