Using this Protected Item type will incur a per-guest Booster charge.
This feature requires Comet Backup 23.9.7 or later.
This Protected Item backs up VMware vSphere virtual machines by connecting directly to either a vCenter server or an ESXi host. Guest virtual machines do not have to be offline for the backup to happen.
For each virtual machine selected for backup, Comet takes a snapshot of the VM, then streams all necessary files (including the
vmdk disks, and other files) into the Chunking engine, optionally using Changed Block Tracking (CBT) for improved performance. Comet then frees the VM snapshot on the host. The machine running Comet Backup does not require any temporary disk space.
Large disk image files are streamed from the datastore to Comet. A large amount of traffic takes place over the internal network. For the best performance, Comet Backup should be installed as a VM on the same ESXi cluster and/or specific host that it is backing up.
You can choose how many VMs Comet backs up at a time. Backing up multiple VMs at a time may increase performance.
Changed Block Tracking can be used to read only blocks that have changed since the last successful backup. Additionally, unallocated disk areas are skipped (Standard and CBT) to further improve the backup performance.
If Changed Block Tracking is used, Comet accesses the VMware datastore using the NBDSSL protocol with
fastlz compression mode for improved performance.
- Desktop Client
- Only available for Windows x86_64 clients
- Running on the same network with the target ESXi/vCenter
- vSphere 6.7 (ESXi or vCenter) or later.
- Enable methods
- Disable methods
- Allocate space
- Browse datastore
- Low level file operations (ESXi: FileManagement)
- Virtual machine
- Allow read-only disk-access
- Allow virtual machine download
- Snapshot management (ESXi: State)
- Create snapshot
- Remove snapshot
Protected Item configuration (desktop client)
Select VMware vSphere on the protected item list.
vSphere APIunder Connection and click
Configure...to enter user credentials.
Test Connectionto check the connectivity of the client to the host.
Click on the plus sign on the right to start selecting virtual machines. All virtual machines can be backed up by selecting the top level
VMware vSphere. Individual virtual machine selection is also possible as well.
Select the backup type to use for all selected virtual machine. See options for more details on the possible modes.
Comet connects to the vSphere server using the vSphere's SOAP API (VADP). Comet transfers files from the datastore NBDSSL protocol.
|Server||The vCenter/ESXi host. Also accepts |
|Thumbprint (Optional)||If supplied, this will be the SSL certificate hash used to compare against the received server certificate for extra security.|
|Allow invalid SSL certificate||Ignore SSL certificate validation errors|
|Username/Password||vCenter/ESXi credentials for authentication|
Latest VM state (Changed Block Tracking)
- Recommended for best performance.
- Back up only changed disk sectors since the last successful backup (this option can be selected even for the first backup job).
Latest VM state (Standard)
- Back up current state of all disks and VM configuration. Past snapshots will be flattened, resulting in a single disk with the most recent state.
Virtual Machine List (web)
When configuring VMware vSphere protected item using the web UI, there are some manual options which can be configured for a more customized selection.
- Include All Virtual Machines: Backup all virtual machines on found on host. Selecting the top level item in the picker will select all and apply this filter. This is useful for dynamically include new virtual machines to the backup without having to reconfigure the protected item.
- Include specified Virtual Machine: Only virtual machines with matching name will be backed up.
- Exclude specified Virtual Machine: Virtual machines with matching name will be skipped.
- If manually specifying a virtual machine, a couple of formats are accepted
[datacenter-name] vm-nameto back up a specific VM on a datacenter
vm-nameto target all matching virtual machines across all datacenters
For Changed Block Tracking and Standard mode
- Performance is optimized by seeking over unallocated disk sectors.
- Data transfer occurs over the NBDSSL protocol.
- Separate snapshot files are not included in the backup. Current VM state is flattened in a single disk image.
- Disks with independent disk mode is not supported and will be skipped during the backup process.
Comet Backup can restore the
vmdk, and other files to the local disk. You must then copy them to the ESXi datastore, and import the VM from the ESXi/vCenter interface.
UPCOMING: Future versions of Comet may support restoring directly to the datastore.
If backup is made while a VM is running off a snapshot, the resulting disk will be a flattened version of the snapshot branches. Do the following to reimport this virtual machine.
- Update VMX config with
scsi0:N.fileName = <file>
- (Optional): Reclaim disk space (
vmkfstools -K <vmdk>) to reset unallocated spaces for improved backup performance.
If CBT was enabled. It is recommended to disable/restart CBT before the first boot.
Granular restore of single files and folders is available for NTFS partitions.
Enabling CBT inside VMware vSphere
CBT is an optional feature for virtual machines and disks inside VMware vSphere. To use CBT mode in Comet, you should first enable CBT for VMs and their disks inside VMware vSphere.
- Stop the running VM.
- In the VMware vSphere web interface, click the "Edit" button.
- In the "Edit Settings" dialog, select the "VM Options" tab.
- Find the "General" section -> find the "Configuration Parameters" section -> click "Edit configuration".
TRUEto enable CBT or
FALSEto disable CBT.
FALSEfor each attached disk.
- If you are disabling CBT, use the datastore browser to delete any
*-CTK.VMDKfiles inside the VM's directory.
- Start the VM again.
Common Log Messages
No parent snapshot found. Fallback to full backup
- A valid reference backup job is not found for CBT. This usually happens during first backup in a storage vault or if a previous backup failed. This will result with the current job running a full backup instead of CBT. Then next CBT backup after this should be successful without this message.
VM <name> contains <N> snapshots(s). Snapshots will be flattened during backup
- If a virtual machine is running off a snapshot, the final virtual disk image will be a consolidation of the current snapshot up to the root. The snapshot tree is not preserved.
Unable to run CBT: disk size changed <old> -> <new>
- Virtual disk size has changed since the last backup. This requires a full backup on the disk.
Unable to run CBT: inconsistent change id <old> -> <new>
- Change ID information has changed since the last succesful backup. This requires a full backup on disk.
Unsupported disk mode <mode>
- Independent disk modes (persistent and non-persistent) is not supported. This disk mode does not support snapshots which is a required part of the backup process.
Unsupported disk backing
- Disk was created using an unsupported format. This disk will be skipped.
Error downloading file: download(<file URL>): 401 Unauthorized
- Credentials used does not have the Datastore role(s) set.
CBT is not enabled on <vm name>
- CBT is configured on protected item but is disabled on the target virtual machine.