ScaleGrid now allows you to set up automatic recurring backups for your MongoDB hosting standalone instances, replicas and shards. When you click the backup button in the main console, you’re presented with two options:
MongoDB on-demand backups can be used to backup your MongoDB clusters on-demand before an interesting event. For example, application upgrade, MongoDB version upgrade, etc.
MongoDB automated, recurring backups, on the other hand, are used to setup backups for your production clusters at regular, scheduled intervals.
For a general overview of MongoDB backup options, refer to our blog post – MongoDB backup options.
Automatic backups provide you with the following options:
This can be between 1 and 7 days.
Backup Time (UTC)
This is the time at which the backup is triggered. Please note that the time is in UTC.
Maximum Backups to Retain
This is the maximum number of scheduled backups that you want the system to retain. For example, if you backup once a week and would like to keep one months worth of backups, you would set this number to 4.
This is available only for replica sets and gives you the option of backing up from the primary or the secondaries. The advantage of backing up from the secondary is that it has no impact on the primary. This is especially important if you have a highly loaded primary.
You can easily restore any of your retained scheduled or on-demand backups at any time. In the restore UI, all automatic backups have a name with the format “Scheduled-<timeUTC>”. The “Taken On” property in the restore UI provides the exact time of the snapshot in your local time – this is the time we issued a snapshot command on the server. Select the backup you’d like to restore, and click restore to replace your existing data. As a good rule of thumb, make sure to create a backup of your current data before implementing a restore.
As always, if you have any questions or comments, send us an email at firstname.lastname@example.org.