Virtual Image Protection
- 16 Feb 2021
- DarkLight
Virtual Image Protection
- Updated on 16 Feb 2021
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Commvault VMware Protection (VMDK)
Overview:
Image level (VMDK) back up the guest server at the hypervisor storage level and do not require any modules to be installed.
Requirements:
A supported version of VMware Tools must be on each virtual machine; unsupported versions must be upgraded.
http://documentation.commvault.com/hds/v11/article?p=system_requirements/vs_vmware.htm [external link to Commvault website]
Virtual image Protection is offered for VMs hosted in Expedient's vColo or pvColo environments
Defaults:
VMDK backups will include the following by default.
- Virtual Machines (Windows and Linux)
- VMDK Files
- GPT or Dynamic disk volumes
- If you subscribe to Expedient's Virtual Colocation (vColo) service it is important to understand that you must have adequate free space to support the snapshots that will need to be created during the backup process. This is usually greater than or equal to 10% free space required.
Requested Information in Workbook: Servers names at the VMware level.
Special Considerations:
- By default, Expedient disables Guest Quiescing due to compatibility issues, meaning all image-based backups are only crash consistent.
- Virtual Machines that are extremely busy and/or have a high file change rate may experience I/O issues while snapshots are being taken of the machine.
- Virtual RDMs/Independent disks are not supported by Expedient at this time.
Was this article helpful?