Signed-off-by: Fabian Ebner <f.eb...@proxmox.com>
---
pve-storage-dir.adoc | 5 +++--
vzdump.adoc | 3 +++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc
index d1ca3eb..4116fe5 100644
--- a/pve-storage-dir.adoc
+++ b/pve-storage-dir.adoc
@@ -56,11 +56,12 @@ dir: backup
path /mnt/backup
content backup
prune-backups keep-last=7
+ max-protected-backups 3
----
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
-backup files is `/mnt/backup/dump/...`.
+used to store up to 7 regular backups (`keep-last=7`) and 3 protected backups
+per VM. The real path for the backup files is `/mnt/backup/dump/...`.
File naming conventions
diff --git a/vzdump.adoc b/vzdump.adoc
index b9dca2a..71221e7 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -301,6 +301,9 @@ For filesystem-based storages, the protection is
implemented via a sentinel file
`<backup-name>.protected`. For Proxmox Backup Server, it is handled on the
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.
+
[[vzdump_restore]]
Restore
-------
--
2.30.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
