| Guidance | Action for Hyper-V | Action for VMware | |
|---|---|---|---|
| ☐ | Disable automatic VM snapshots/checkpoints. If snapshots are required, they should be taken while the application is idle. |
Navigate to and set Checkpoints to Disable |
Disable automated snapshot policies in vCenter Lifecycle Manager or any backup job targeting this VM. |
| ☐ | Application-consistent backups only; no snapshot or migration under write load | Do not run VSS or Hyper-V checkpoints against the live HDB volume during writes. Do not Live Migrate the VM under active write load. | Do not take quiesced snapshots, run VADP/CBT backup jobs, or perform Storage/vMotion of the HDB VM under active write load. |
| ☐ | Disable virtual disk cache mode. This ensures that FlushFileBuffers() calls from BDB reach stable storage. | Navigate to and set Cache Mode: to None. |
Navigate on the virtual machine to and select Independent – Persistent. Use this procedure to edit the VM's
.vmx file as follows:
|
| ☐ | Use fixed/thick-provisioned virtual disk | Convert dynamic VHDX (Virtual Hard Disk v2) to fixedvia PowerShell: Convert-VHD -Path "disk.vhdx" -DestinationPath "disk-fixed.vhdx"
-VHDType Fixed(See this document for more details.) |
Use Thick Provision Eager Zeroed VMDK. Thin-provisioned VMDKs introduce allocation overhead during write bursts. Convert via Storage vMotion or the procedure outlined here. |
| ☐ | Verify hypervisor tools/integration services are current | Run on host: Get-VMIntegrationService -VMName
<YourVM>(See this document for more details.) Update via Windows Update on the guest or reinstall the Hyper-V Integration Services package. |
Confirm VMwareTools status is Runningor Currentby navigating on the virtual machine to Summary. Update by navigating on the virtual machine to . |
| ☐ | Store virtual disk on local host storage, not network storage | Avoid placing VHDX files on Server Message Block (SMB) shares or Cluster Shared Volumes (CSV). Confirm VHDX path via . | Avoid NFS data stores for BDB VMDKs. Use local VMFS or iSCSI with synchronous write guarantees. NFS data stores with async mount options are not safe for BDB. |
| ☐ | Disable host-level write cache on physical disks (without a battery-backup unit—BBU) | On the Hyper-V host, confirm write-cache buffer flushing is NOT disabled unless a BBU is present via . | On the ESXi host, confirm the storage controller has a functioning BBU or
flash-backed write cache. Run the following command on the ESXi shell: esxcli
storage core device list and verify the controller cache status via vendor
management tools. (See this document for more details.) |