# Concepts

# Server

Check out our detailed Server section.

# Storage

Check out our detailed Storage section.

# Scheduling

Scheduling a backup allows you to define when the backup has to run:

Good to know

Backup scheduling is based on your time zone when using custom schedules (setup your time zone (opens new window)).

  • On demand: This won't schedule anything but will allow you to trigger the backup manually or using our API.
  • Daily: Every day at 0:00 AM
  • Weekly: Every Sunday at 0:00 AM
  • Monthly: Every first Sunday of the month at 0:00 AM
  • Custom: Use this option if you want to create your scheduling with more options or using plain CRON expression. Custom backup schedule Example of CRON schedule for "20:00 every Tuesday" = 0 22 * * 2

# Retention

The backup retention is the number of backups you want to keep available. This value will be a number, ranging from 0 (unlimited retention, meaning we never delete your backup files) to whatever retention number you might need.

# How does backup retention work?

Every time a backup runs, we check the number of backups you already have stored and if this number is higher than the retention value we delete the oldest backup files still stored.

# When should I use backup retention?

A good practice is to always define a retention value, in order to avoid using too much storage. The value will mainly depends on the context of the project you're backing up. When you created your backup, ask yourself the question "Till how long back in time do I need to be able to go if something goes wrong with my site/database"?

Good to know

Another great way to approach it is to define multiple backups for a given project, one with a 7 days retention scheduled on a daily base and a second one with a retention set to 12 scheduled on a monthly base. This will allow you to travel 12 months in the past with a low granularity (1 per month) and have a daily backup granularity for the last week.

# Notifications

We support email, Slack and Discord real-time notifications. You receive both, success and error notifications when you run backups on demand. For scheduled backups, you only receive notifications for backup failures after all retries are exhaused.

# Configure notification channels

By default you'll receive an email notification whenever a backup fails. You can disable this option from the advanced tab of your backup (https://my.simplebackups.com/backup/BACKUP_ID#advanced), a tick the "Mute backup notifications" checkbox in the "Email notifications" box.

You can enable backup error notifications to be sent to Slack and Discord on that page too.

# Configure notification email

Sometimes you may want to forward all backup notification emails to your developer to have him/her take action if backups fail.

In this case you can change the backup notification email in your SimpleBackups account by following these steps:

# Trigger backup remotely

Backup Trigger URL is a unique URL for every backup you have that can be used to run that backup immediately with without having to log in to SimpleBackups.

Example use cases:

  • Give your client or another developer a URL they can use to run that backup.
  • Run your backup on a custom interval, let's say every X minutes/hours.
  • Run your backup before you deploy a new version of your app.
  • Run your backup on-demand using a single URL when needed.

# How to use the Backup Trigger URL?

  • Create a backup on SimpleBackups.
  • View the newly created backup or an already existing backup (https://my.simplebackups.com/backup/BACKUP_ID#advanced).
  • Under the Backup Trigger URL you will find a URL that you can use in a cURL function, a Zapier integration, cron, deploy script, share it with a developer or use it to run your backup on-demand.

# Incremental backup

Incremental backups allow you to only back up the files that change. This allows you to save on storage space and make your file backups quicker to complete.

# SimpleStorage

→ Get to know "SimpleStorage.

Last Updated: 10/11/2021, 4:00:59 PM