This article aims to provide further information about what happens when an Aura database instance is paused.
Note: A full backup (snapshot) is performed as part of the pause/resume process, so the larger an instance, the longer a pause/resume action may take.
1. Pause button is clicked
2. Status in Database tile updates to: Pausing
3. From the time you click the pause button, you will be charged the paused rate (20% of the normal running cost as explained in the Pause Modal), this will be in effect even while the status still displays: Pausing
4. Backup of instance is automatically initiated
5. Backup is completed
6. Status now changes to Paused in the console
- Enterprise and Pro Tier Aura instances will be automatically resumed after 30 days to ensure they don't miss critical updates.
- The creator of the instance will receive a notification about the resume action.
You have the option to pause the instance again.
- If you don't prefer this, you can download a dump of your instance and destroy the instance.
- You can re-upload the dump to a new instance when needed.
1. Resume button is clicked
2. Status changes to Resuming
3. From the time you click the resume button, you will be charged the full usual standard running costs once again (this is also explained in the Resume Modal)
4. Restore of full backup is initiated
5. Instance now shows as Running
If you experience any issues when performing these actions, please raise them with our support team.