vzdump/storage: mention protected backups limit and give an example

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2022-03-29 14:53:18 +02:00 committed by Fabian Grünbichler
parent 5c85b0a168
commit 2db55d5d11
2 changed files with 8 additions and 2 deletions

View File

@ -56,11 +56,12 @@ dir: backup
path /mnt/backup path /mnt/backup
content backup content backup
prune-backups keep-last=7 prune-backups keep-last=7
max-protected-backups 3
---- ----
The above configuration defines a storage pool called `backup`. That pool can be The above configuration defines a storage pool called `backup`. That pool can be
used to store up to 7 backups (`keep-last=7`) per VM. The real path for the used to store up to 7 regular backups (`keep-last=7`) and 3 protected backups
backup files is `/mnt/backup/dump/...`. per VM. The real path for the backup files is `/mnt/backup/dump/...`.
File naming conventions File naming conventions

View File

@ -301,6 +301,11 @@ For filesystem-based storages, the protection is implemented via a sentinel file
`<backup-name>.protected`. For Proxmox Backup Server, it is handled on the `<backup-name>.protected`. For Proxmox Backup Server, it is handled on the
server side (available since Proxmox Backup Server version 2.1). server side (available since Proxmox Backup Server version 2.1).
Use the storage option `max-protected-backups` to control how many protected
backups per guest are allowed on the storage. Use `-1` for unlimited. The
default is unlimited for users with `Datastore.Allocate` privilege and `5` for
other users.
[[vzdump_restore]] [[vzdump_restore]]
Restore Restore
------- -------