← Back to Changelog

3rd May 2022

Scheduled backups, guides and enhancements

Today we are excited to release backup schedules. You can now create regular backups for your databases and addons, enhancing your production workloads on Northflank. Having regular backups is essential as it allows you to restore your addon in case of data loss, bad migrations or queries. Scheduled backups can be configured flexibly to ensure your individual backup requirements can be met.

Backup schedules on your addon allow up to three schedules. Configure the following parameters:

  • Backup type: snapshot (recommended) or dump (Backup Documentation)
  • Backup frequency: choose between hourly, daily or weekly backups and select the appropriate time of the day
  • Retention period: how long the backup will be stored until it's deleted

Notable features:

  • Configure multiple schedules, one per type (hourly, daily or weekly)
  • The total number of backups created for a schedule before any backups expire is limited to 500 backups
  • Backups created by a schedule can be manually changed to not expire. To retain the backup indefinitely, click on the backup and hit Retain backup forever using the save button
  • For backups that were created by a schedule, you can look up the schedule and the retention time on a per backup basis
  • If two or more schedules overlap, only one backup is created. The UI and API will show all associated schedules and the highest retention period is applied.


New Guides:

Other features & fixes:

  • Added new GitLab application handling for upcoming token rotation requirements
  • Added team invitation expiry and ability to regenerate an invitation
  • Added editing of Dockerfile during service creation
  • Improved performance of backup and VCS subscriptions
  • Improved UI handling of log search between two time ranges
  • Updated Flask template repository
  • Fixed project icon disappearing from documentation
  • Fixed build service handling in deployment component when no build is present
  • Fixed secret group creation when modifying alias keys in a particular order

Share this article with your network