Help CenterClumio Terraform ProviderClumio Python SDKClumio GO SDK
User Guide
BlogChangelogLogin

VMware Limitations

Suggest Edits

VMware Independent Disk Backup Limitations

Purpose

Clumio leverages VMware snapshots as part of the virtual machine backup workflow. VMware does not currently support snapshots of independent disks in a virtual machine, whether persistent or non-persistent.

This describes the current Clumio behavior for backup and restore of virtual machines with independent disks. 

Resolution

The following describes the expected behavior when a VM with independent disk(s) is protected by Clumio.

VM Backup:

  • Independent disks will not be backed up by Clumio.
  • Dependent (default) disks are backed up by Clumio.

VM Restore:

  • Only dependent disks will be restored.
  • If independent persistent disks are desired as part of the restore, customers are expected to manually create the independent persistent disk on the restored VM.

Windows ReFS Limitation

Purpose

This describes Clumio behavior for backup, restore, and file-level restore of virtual machines with ReFS drives.

Clumio performs backups at the virtual disk level and indexes the data at a individual drive, folder, or file-level in the guest file system. For Windows, ReFS is one of many guest file systems used. Clumio does not currently support Backup Indexing for ReFS-based drives.

Resolution

This is the expected behavior when a VM with independent disk(s) is protected by Clumio.

VM Backup:

  • Clumio VM Backups are taken at the VMware virtual disk level and do not exclude the ReFS drives, which are part of the Guest File System during backups.

VM Restore:

  • Full VM restore is not affected by the indexing limitation. If ReFS drives are part of the VM backup, you can expect all the drives, including ReFS, to be available as part of the restored VM.

Browse & Restore ( File / Folder level restore )

  • VM Backup Indexing is not supported for ReFS-based drives. In the Browse & Restore dialog the ReFS attributes are shown as "0 B(bytes)" and files inside the drives are not accessible for file-level restore. The workaround is to perform VM Restore.




Contact [email protected] in case of any clarifications or questions.

Updated 10 months ago