X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=vzdump.adoc;h=193e1cfe23d8dfbbd9ac5f9b41524dd460be5eeb;hp=03d6caa60310a10b25b696774573d0bf75473a6f;hb=5ec2497fc1fbc22ce8385a67a0924ffcd0ad1fe0;hpb=922569a5bcc78ffdb69e8ca27a8ddb8cad61c393 diff --git a/vzdump.adoc b/vzdump.adoc index 03d6caa..193e1cf 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -111,7 +111,7 @@ started (resumed) again. This results in minimal downtime, but needs additional space to hold the container copy. + When the container is on a local file system and the target storage of -the backup is an NFS server, you should set `--tmpdir` to reside on a +the backup is an NFS/CIFS server, you should set `--tmpdir` to reside on a local file system too, as this will result in a many fold performance improvement. Use of a local `tmpdir` is also required if you want to backup a local container using ACLs in suspend mode if the backup @@ -170,7 +170,7 @@ the target storage. This can negatively effect other virtual guest as access to storage can get congested. To avoid this you can set bandwidth limits for a backup job. {pve} -implements to kinds of limits for restoring and archive: +implements two kinds of limits for restoring and archive: * per-restore limit: denotes the maximal amount of bandwidth for reading from a backup archive @@ -185,14 +185,14 @@ you have `Data.Allocate' permissions on the affected storage. You can use the `--bwlimit ` option from the restore CLI commands to set up a restore job specific bandwidth limit. Kibit/s is used as unit -for the limit, this means passing '10240` will limit the read speed of the +for the limit, this means passing `10240' will limit the read speed of the backup to 10 MiB/s, ensuring that the rest of the possible storage bandwidth -is available for the already running virtual guests, and does not impacts -their operations. +is available for the already running virtual guests, and thus the backup +does not impact their operations. NOTE: You can use `0` for the `bwlimit` parameter to disable all limits for a specific restore job. This can be helpful if you need to restore a very -important virtual guest as fast as possible. (Need `Data.Allocate' +important virtual guest as fast as possible. (Needs `Data.Allocate' permissions on storage) Most times your storage's generally available bandwidth stays the same over