Periodic Backup Tasks View
Periodic Backups View
Create a periodic backup task
To schedule automatic, recurrent backups.
View Details of periodic backup tasks
- Backup Now (e.g. before software updates) can be triggered in the 'View Details' interface.
- Edit this database backup task. To edit server/node-wide backup tasks, see button #5.
- Delete this periodic backup task.
- Go to server-wide backups view to back up all databases on the server.
Database Group Topology
This shows all active server-wide and database specific periodic backups.
Creating Periodic Backups
Defining Periodic Backups
Task Name (Optional)
- Choose a name of your choice
- If no name is given then RavenDB server will create one for you based on the defined destination
Backup Task Type:
- Backed Up Data: The database data in a JSON format, including documents, indexes (definitions only) & identities
(same as exported database format)
- Size of backup data: Smaller
- Backup Speed: Faster
- Restoring: Slower, Indexes have to be rebuilt from their definitions
- Backed Up Data: The raw database data including the indexes (definitions and data)
- Size of backup data: Larger
- Backup Speed: Slower
- Restoring: Faster, Indexes do not have to be rebuilt
Preferred Node (Optional)
- Select a preferred mentor node from the Database Group to be the responsible node for this Backup Task
- If no node is selected, then the cluster will assign a responsible node (see Members Duties)
Select the content to back up. Note: Both incremental and full backups can be scheduled at the same time.
Scheduling Two Backups
Full Backup will back up all the database data every time the task is scheduled to work.
A Snapshot can only occur when scheduling 'Full'.
Incremental Backup will only back up the delta (changes made) of the data since the last backup that has occurred.
- If only Incremental Backup is set, then a Full Backup will occur only the first time that the task is triggered,
followed by Incremental Backups according to the scheduled time.
The Full Backup that is done the first time will be either a 'Backup' or a 'Snapshot', depending on the type selected.
- Data that is backed up in Incremental Backup is always of type 'Backup' - even if the Backup Task Type is 'Snapshot'.
'Backup' types save index definitions, but not the fully built indexes.
Schedule the Backup Tasks to occur at regular intervals (daily, monthly, hourly, every minute) at specific times.
Save on data transfer with frequent "incremental" backups and recover lost data with infrequent "full" backups
To save on data transfer costs you can schedule frequent 'incremental' backups, (which save any changes made since the previous backup).
To ensure that you can recover lost data, schedule infrequent 'full' backups.
Infrequent backups can be useful if a mistake was made and you need access to data from a few days ago.
If downtime while recovering databases is a concern, you can also set up an external replica and manually fail over to it while you recover the data onto the original cluster.
To save storage space, you can set obsolete scheduled backup files to delete automatically after the time period that you define.
Old backups are deleted after the defined time period during the next scheduled backup.
Backup Retention Policy
Enable / disable the retention policy. If disabled, the backups are stored indefinitely, which may use a lot of storage.
We recommend enabling so that deletion of obsolete backups can be scheduled.
- Select the retention period.
Some organizations require backups to be stored for as long as 7 years. If this is the case, consider the issue when scheduling and setting the retention policy.
Backups can be encrypted. Make sure that you save the encryption key well.
Backup Encryption Options
- Toggle Encrypt to encrypt the backup files.
Choose the current encryption key or create a new one for this backup task.
- Use the current encryption key. You don't need to set and save a new key with this option.
- Create a new encryption key for backups. You can only do this on 'Backup' type backups.
Create New Encryption Key for Backup
- The new encryption key. Click the 'refresh' arrow to randomly create a different key.
- Options to save the key.
- Check the box to acknowledge that you've saved the key.
Select backup destinations and enter your credentials for each.
Make sure to save the destinations and credentials information so that your team will be able to restore the database if needed.
Local machine storage
- Set a folder of your choice (any directory that can be accessed from your machine)
Cloud storage options
More than one destination can be selected at the same time. The backup process will first write the backup to the local path (or to a temporary path if the local path is not specified).
Once that's done, the backup owner will start uploading the backup to all remote destinations in parallel.
If any of the remote destinations fail, the entire backup will be considered to have failed.
For a resilient data protection strategy
that protects your databases from natural disasters and theft, we recommend scheduling concurrent backups on a local machine and on the cloud.
This strategy is known as the 3-2-1 Backup Rule.
Periodic Backup Details
Periodic Backup Details
Backup Task Details:
- Task Status
Active / Not Active / Not on Node
List of all backup destinations defined
- Last Full Backup
The last time a Full Backup was done
(Snapshot / Backup type - depending on task definition)
- Last Incremental Backup
The last time an Incremental Backup was done
- Next Estimated Backup
Time for next backup
(Full Backup / Incremental Backup / Snapshot - depending on task definition)
- Retention Policy
Backups older than this period will be deleted during next backup.
In addition to the scheduled time defined, you can backup your data now.
This is useful before software updates or any other action where data may be lost.
The scheduled backup will still be triggered as defined.
Click to refresh this panel viewed details