mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-05-03 11:56:39 +00:00
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>
This commit is contained in:
parent
65c2112316
commit
6bc5d54db7
12
vzdump.adoc
12
vzdump.adoc
@ -289,13 +289,17 @@ Backup Protection
|
|||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
You can mark a backup as `protected` to prevent its removal. Attempting to
|
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
|
remove a protected backup via {pve}'s UI, CLI or API will fail. However, this
|
||||||
removal of a backup file via CLI is still possible. Protected backups are
|
is enforced by {pve} and not the file-system, that means that a manual removal
|
||||||
ignored by pruning and do not count towards the retention settings.
|
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
|
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.
|
server side (available since Proxmox Backup Server version 2.1).
|
||||||
|
|
||||||
[[vzdump_restore]]
|
[[vzdump_restore]]
|
||||||
Restore
|
Restore
|
||||||
|
Loading…
Reference in New Issue
Block a user