Provides an explicit backup schedule for a single database to follow.
This overrides any agent schedule that would otherwise be active.
A database backup schedule should be used when a database has different automatic backup requirements from the agent's schedule.
Set a schedule¶
Navigate to your dashboard and click 'Databases' on the agent managing the database you wish to backup. Click the 'Add schedule / Edit schedule' button against the database.
Set the options described below and click 'Save Schedule'.
This is how often the backup runs. You can choose to run backups every x days or every x weeks on the days you want.
For example (assuming today is the Monday the 2nd):
- You chose every 2 days:
backups would be triggered on the 2nd, 4th, 6th, 8th etc.
- You chose every 2 weeks on Mondays and Tuesdays:
backups would be triggered on the 2nd, 3rd, 16th, 17th, 30th, 31st etc.
This takes effect on days when backups are triggered and defines when / how often backups occur during the day.
You can choose to run a backup once at a specific time of day, or every x hours or minutes between the hours of your choosing.
For example (let's assume today is a day which triggers backups):
- You choose Once at 01:00:
A single backup is taken at 01:00 in the agent's timezone.
- You choose Every 12 hours starting at 02:00 and ending at 14:00:
Backups are taken at 02:00 and 14:00
The number of days a backup is stored for before being deleted.
A shorter period could be used if you take regular backups, or your should retain them longer if you intend to take backups infrequently.
This is calculated from the time the backup was scheduled to run. For example, if the backup took 1 hour to complete and the backup retention was set for 7 days, the backup would be deleted 6 days and 23 hours after the backup completed.
Reducing the retention period effects completed backups. For example, if you reduce your retention period from 7 to 5 days and you had a backup which was 6 days old, it would be removed the next time backups are pruned.