proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-05 11:47:43 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Replace VM occurences with 'guest' or 'container' when appropriate

Browse Source 
also replace Qemu/KVM with QemuServer as it is the detailed term
used in the vzdump man page
This commit is contained in:
Emmanuel Kasper 2016-04-13 10:58:35 +02:00 committed by Dietmar Maurer
parent 0006064d98
commit c31f32a9c1
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
vzdump.adoc
View File

@ -25,16 +25,16 @@ Backup and Restore
include::attributes.txt[] include::attributes.txt[]
endif::manvolnum[] endif::manvolnum[]
'vzdump' is a utility to make consistent snapshots of running virtual 'vzdump' is a utility to make consistent snapshots of running guest
machines (VMs). It basically creates an archive of the VM private systems. It basically creates an archive of the guest private
area, which also includes the VM configuration files. 'vzdump' area, which also includes the guest configuration files. 'vzdump'
currently supports LXC containers and QemuServer VMs. currently supports LXC containers and QemuServer VMs.
There are several ways to provide consistency (option `mode`): There are several ways to provide consistency (option `mode`):
`stop` mode:: `stop` mode::
Stop the VM during backup. This results in a very long downtime. Stop the guest during backup. This results in a very long downtime.
`suspend` mode:: `suspend` mode::
@ -140,7 +140,7 @@ Configuration files are also stored inside the backup archive
Examples Examples
-------- --------
Simply dump VM 777 - no snapshot, just archive the VM private area and Simply dump guest 777 - no snapshot, just archive the guest private area and
configuration files to the default dump directory (usually configuration files to the default dump directory (usually
'/var/liv//vz/dump/'). '/var/liv//vz/dump/').
@ -150,7 +150,7 @@ Use rsync and suspend/resume to create a snapshot (minimal downtime).
# vzdump 777 --mode suspend # vzdump 777 --mode suspend
Backup all VMs and send notification mails to root and admin. Backup all guest systems and send notification mails to root and admin.
# vzdump --all --mode suspend --mailto root --mailto admin # vzdump --all --mode suspend --mailto root --mailto admin
@ -158,19 +158,19 @@ Use snapshot mode (no downtime).
# vzdump 777 --dumpdir /mnt/backup --mode snapshot # vzdump 777 --dumpdir /mnt/backup --mode snapshot
Backup more than one VM (selectively) Backup more than one guest (selectively)
# vzdump 101 102 103 --mailto root # vzdump 101 102 103 --mailto root
Backup all VMs excluding VM 101 and 102 Backup all guests excluding 101 and 102
# vzdump --mode suspend --exclude 101,102 # vzdump --mode suspend --exclude 101,102
Restore a container to a new VM 600 Restore a container to a new CT 600
# pct restore 600 /mnt/backup/vzdump-lxc-777.tar # pct restore 600 /mnt/backup/vzdump-lxc-777.tar
Restore a Qemu/KVM machine to VM 601 Restore a QemuServer VM to VM 601
# qmrestore /mnt/backup/vzdump-qemu-888.vma 601 # qmrestore /mnt/backup/vzdump-qemu-888.vma 601