mirror of
https://github.com/restic/restic.git
synced 2024-12-23 08:16:36 +00:00
Added documentation about what happens if you run out of space
during a backup, based on conversation on the forum: https://forum.restic.net/t/limited-backup-destination-space/733/6
This commit is contained in:
parent
e4c0d77bdd
commit
888f52afd1
1 changed files with 14 additions and 0 deletions
|
@ -299,3 +299,17 @@ information. Just specify the tags for a snapshot one by one with ``--tag``:
|
|||
The tags can later be used to keep (or forget) snapshots with the ``forget``
|
||||
command. The command ``tag`` can be used to modify tags on an existing
|
||||
snapshot.
|
||||
|
||||
Space requirements
|
||||
******************
|
||||
|
||||
Restic currently assumes that your backup repository has sufficient space
|
||||
for the backup operation you are about to perform. This is a realistic
|
||||
assumption for many cloud providers, but may not be true when backing up
|
||||
to local disks.
|
||||
|
||||
Should you run out of space during the middle of a backup, there will be
|
||||
some additional data in the repository, but the snapshop will never be
|
||||
created as it only would be written at the very (successful) end of
|
||||
the backup operation. Previous snapshots will still be there and will still
|
||||
work.
|
||||
|
|
Loading…
Reference in a new issue