backup: clarify that CLI means FS-level and highlight retention-note

plus some other related, small additions/changes

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/vzdump.adoc b/vzdump.adoc
index f766d36515dcd3410b2175e776c68990be3971a0..b9dca2acf8e2e59c55ce560706a5deda27fe105e 100644 (file)
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -289,13 +289,17 @@ Backup Protection
 -----------------
 
 You can mark a backup as `protected` to prevent its removal. Attempting to
-remove a protected backup via {pve}'s UI or API will fail. However, manual
-removal of a backup file via CLI is still possible. Protected backups are
-ignored by pruning and do not count towards the retention settings.
+remove a protected backup via {pve}'s UI, CLI or API will fail. However, this
+is enforced by {pve} and not the file-system, that means that a manual removal
+of a backup file itself is still possible for anyone with write access to the
+underlying backup storage.
+
+NOTE: Protected backups are ignored by pruning and do not count towards the
+retention settings.
 
 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.
+server side (available since Proxmox Backup Server version 2.1).
 
 [[vzdump_restore]]
 Restore