Use the backup vm command to start a full backup of a virtual machine.
Use the backup vm command to back up VMware virtual machines.
One or more virtual machines are processed using the Tivoli® Storage Manager data mover node. Data mover node is the name that is given to a configuration where the backup-archive client runs on a vStorage backup server and is configured to protect the virtual machines in a Virtual Center or ESX/ESXi server. You must configure the VMware virtual machine before you use this command. For information about configuring the VMware virtual machine, see Preparing the environment for full backups of VMware virtual machines.
A full VM backup stores a backup copy of all virtual disk images and configuration information for a virtual machine. Full VM backups enable a complete restore of a virtual machine, but they take more time and more server space than a file-level or incremental backup.
File-level VM backups can individually restore virtual machine files, but it does not have an easy full VM machine recovery procedure. You might want to use a combination of file level VM backups with periodic full VM backups for optimal results. You must be licensed to use Tivoli Storage Manager for Virtual Environments to use the periodic full backup strategy. For information about the periodic full backup strategy, see Periodic full backup strategy.
If you set vmenabletemplatebackups option to yes, a Backup VM operation includes the template VMs, but only if the vStorage backup server is connected to a vCenter Server, and not to an ESX or ESXi host.
Virtual machines that are deployed in vApps are included in Backup VM operations. There are no client options needed to protect the vApp VMs.
A Full VM backup uses VMware Changed Block Tracking (CBT) to create content-aware (used-block only) backups. Tivoli Storage Manager enables changed block tracking (CBT) on an ESX or ESXi server when a backup begins. VMware CBT requires an ESX 4.1 (or later) host, with virtual hardware 7 (or later). You cannot perform incremental or full VM content-aware backups on virtual machines that do not support CBT.
See Compression, encryption, and adaptive subfile backup processing for more information.
For information about the incremental-forever backup strategy, see Incremental-forever backup strategy.
This command is valid on supported Windows clients that are installed on a vStorage backup server that protects VMware virtual machines.
This command is valid only on supported Linux clients that are installed on a vStorage backup server that protects VMware virtual machines.
>>-Backup VM--+------------+------------------------------------> | .-,------. | | V | | '---vmname-+-' >--+-------------------------------------------------+--------->< '-:vmdk=-- --disk_label-- -- -PREView-- --options-'
backup vm vm1 -preview
Full BACKUP VM of virtual machines 'VM1'
vmName:vm1
VMDK[1]Label: Hard disk 1
VMDK[1]Name: [ds5k_svt_1] tsmcetlnx14/tsmcetlnx14.vmdk
VMDK[1]Status: Included
VMDK[2]Label: Hard disk 2
VMDK[2]Name: [ds5k_svt_1] tsmcetlnx14/tsmcetlnx14_1.vmdk
VMDK[2]Status: Excluded - user,Independent,pRDM
Return code | Description |
---|---|
0 | A command to back up one or more virtual machines completed successfully. |
8 | A command to back up multiple virtual machines succeeded for only some of the virtual machines that were targeted by the command. Examine the log file to determine the processing status for each of the targeted virtual machines. |
12 | A return code of 12 can indicate that either
of the following error conditions occurred:
|
dsmc backup vm vm1 -vmbackuptype=file
dsmc backup vm vm1 -vmbackuptype=file -vmchost=virtctr
dsmc backup vm vm3,vm4 -vmbackuptype=fullvm -mode=ifincremmental
dsmc backup vm vm1 -vmbackuptype=fullvm -mode=iffull
dsmc backup vm "vm1:vmdk=Hard Disk 1" -vmbackuptype=fullvm -mode=iffull
dcmc backup vm "vm1:-vmdk=Hard Disk 1:-vmdk=Hard Disk 4"
-vmbackuptype=fullvm -mode=iffull
dsmc backup vm "vm1:vmdk=Hard Disk 2:vmdk=Hard Disk 3",
vm2 -vmbackuptype=fullvm -mode=iffull
dsmc backup vm –vmmaxparallel=5 –vmlimitperhost=2 –vmlimitperdatastore=0
Use the Backup VM command to backup Hyper-V virtual machines. You can back up Hyper-V guests that exist on a local disk, a SAN-attached disk, a cluster shared volume, or guests that exist on a remote file server share. Remote file server shares must be on a Windows Server 2012 (or newer) system.
For information about the incremental-forever backup strategy, see Incremental-forever backup strategy.
This command is valid on supported Windows clients that are installed on a Hyper-V host server.
>>-Backup VM--+-----------------+-------------------------------> | .-,------. | | V | | +---vmname-+------+ +-vmlist=--vmname-+ '-vmlist=?--------' >--+---------------------------+--+-------------------------+---> '- -VMBACKUPType=HYPERVFULL-' '- -VMBACKUPUPDATEGUID-- -' >--+-----------------------+----------------------------------->< '- -PREview-- --options-'
If you do not specify a virtual machine name, and if you specify -mode=ifincremental or -mode=iffull, the domain.vmfull option is used to determine which virtual machines to include in the backup operation.
If you do not specify a virtual machine name, and if you specify -mode=full, the vmlist option is used to determine which virtual machines to include in the backup operation.
This option updates the globally unique identifier (GUID) for the virtual machine that you are backing up. This parameter is intended for use only in the following scenario:
tsm> backup vm -vmbackuptype=hypervfull -mode=ifincr -preview
Backup VM command started. Total number of virtual machines to process: 6
1. VM Name: VM2
Domain Keyword: all-vm
Mode: Incremental Forever - Incremental
Target Node Name: SPC
Data Mover Node Name: SPC
Cluster Resource: no
Disk[1]
Name: \\beta\d$\Hyper-V\VM2\VM2.vhdx
Capacity: 40.00 GB
Size: 9.13 GB
Full Backup: included
Incremental Backup: excluded
Disk Type: VHDX
Number of Subdisk: 1
Use both the -preview option and the -detail option on the command to
display information about subdisks that are included when the backup
is run. A subdisk is the AVHDX file that is created when a snapshot
is taken of a VHDX file. This example output is abbreviated to show
only information about one virtual machine and one disk. tsm> backup vm -vmbackuptype=hypervfull -mode=ifincr -preview -detail
Backup VM command started. Total number of virtual machines to process: 6
1. VM Name: VM2
Domain Keyword: all-vm
Mode: Incremental Forever - Incremental
Target Node Name: SPC
Data Mover Node Name: SPC
Cluster Resource: no
Disk[1]
Name: \\beta\d$\Hyper-V\VM2\VM2.vhdx
Capacity: 40.00 GB
Size: 9.13 GB
Full Backup: included
Incremental Backup: excluded
Disk Type: VHDX
Number of Subdisk: 1
Subdisk[1]
Name: \\beta\d$\Hyper-V\VM2\VM2_88ABC7B4-E59F-87B9-20D064E549C4.avhdx
Capacity: 40.00 GB
Size: 4.00 MB
Full Backup: included
Incremental Backup: included
Disk Type: AVHDX
Return code | Description |
---|---|
0 | A command to back up one or more virtual machines completed successfully. |
8 | A command to back up multiple virtual machines succeeded for only some of the virtual machines that were targeted by the command. Examine the log file to determine the processing status for each of the targeted virtual machines. |
12 | A return code of 12 can indicate that either
of the following error conditions occurred:
|
dsmc backup vm VM1 -vmbackuptype=hypervfull -mode=full
dsmc backup vm VM1 -vmbackuptype=hypervfull -mode=ifincremental
dsmc backup vm -vmbackuptype=hypervfull -mode=ifincremental
dsmc backup vm -vmbackuptype=hypervfull -mode=full -vmlist=vm1,vm5
dsmc backup vm -mode=full -vmlist=?
backuptype hypervfull
vmlist vm1,vm2,vm5