If onlyIncremental Backup is set, then a Full Backup will occur only in 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' !
A Snapshot is only occurring when scheduling 'Full'.
In the example above:
A Full Backup is scheduled every day at 02:00 AM - and in addition to that -
An Incremental Backup is scheduled every 6 hours
Backup Task - Destination
Select backup destinations and enter your credentials for each
Note: More than one can be selected
Local - Set a folder of your choice (any directory that can be accessed from your machine)
Destinations - 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)
View of the Backup Task responsible nodes
In addition to the scheduled time defined, you can backup your data now.
The scheduled backup will still be triggered as defined.
Click to refresh this panel viewed details
Backup Task - When Cluster or Node are Down
When the cluster is down (and there is no leader):
Creating a new Ongoing Task is a Cluster-Wide operation,
thus, a new Ongoing Backup Task cannot be scheduled.
If a Backup Task was already defined and active when the cluster went down,
then the Backup Task will still continue to execute on its defined schedule (on its responsible node).
But, it will fail to be reported to the cluster and may be run again after the cluster has recovered.
When the responsible node is down
If the responsible node for the Backup Task is down during the scheduled time,
then another node from the Database Group will take ownership of the task so that there are no gaps in your backups.
Backup Task -vs- Replication Task
RavenDB's External Replication provides you with an off-site live replica/copy of the data.
('live' meaning that any changes in the database will be reflected in the replica once they occur).
This is quite useful if you need to shift operations to a secondary data center.
But a replica isn't a backup... It doesn't present good solutions to many backup scenarios.
For example, it doesn't protect you from an accidental collection delete,
or tell you the state of the system at, say, 9:03 AM last Friday.
A backup keeps an exact state of the database at a specific point in time and can be restored