X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=vzdump.adoc;h=404ad09ce81bf02f5da443caf2dceee8d1271f48;hb=0a1739bd15ba88b0a384366994f1b8afe5073676;hp=fb1ac3d0c3c9853a51aa0ce9ffb9e0ebed3b01a2;hpb=a35aad4add155497568b0742d9ebc3851de64d81;p=pve-docs.git diff --git a/vzdump.adoc b/vzdump.adoc index fb1ac3d..404ad09 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -78,17 +78,17 @@ consistency, the use of the `snapshot` mode is recommended instead. `snapshot` mode:: This mode provides the lowest operation downtime, at the cost of a -small inconstancy risk. It works by performing a Proxmox VE live +small inconsistency risk. It works by performing a {pve} live backup, in which data blocks are copied while the VM is running. If the guest agent is enabled (`agent: 1`) and running, it calls `guest-fsfreeze-freeze` and `guest-fsfreeze-thaw` to improve consistency. -A technical overview of the Proxmox VE live backup for QemuServer can +A technical overview of the {pve} live backup for QemuServer can be found online https://git.proxmox.com/?p=pve-qemu.git;a=blob_plain;f=backup.txt[here]. -NOTE: Proxmox VE live backup provides snapshot-like semantics on any +NOTE: {pve} live backup provides snapshot-like semantics on any storage type. It does not require that the underlying storage supports snapshots. Also please note that since the backups are done via a background Qemu process, a stopped VM will appear as running for a @@ -166,7 +166,7 @@ Bandwidth Limit Restoring one or more big backups may need a lot of resources, especially storage bandwidth for both reading from the backup storage and writing to -the target storage. This can negatively effect other virtual guest as access +the target storage. This can negatively affect other virtual guests as access to storage can get congested. To avoid this you can set bandwidth limits for a backup job. {pve} @@ -200,7 +200,7 @@ time, thus we implemented the possibility to set a default bandwidth limit per configured storage, this can be done with: ---- -# pvesm set STORAGEID --bwlimit KIBs +# pvesm set STORAGEID --bwlimit restore=KIBs ----