Veeam Hyper-V: Local Volume Free Space

Summary

This monitor tracks threshold breaches for the following metric:

• Hyper-V Local Volume \ % Free Space - percentage of free space on the Hyper-V Local Volume.

Warning and Error thresholds are available for the metric.

Causes

Review the alert description for specific guidance relevant to this alert. General troubleshooting information is given below.

Resolutions

Ops Mgr 2012 and 2016 customers can use the in-context dashboards, available in the Navigation section of the Tasks pane, to drill down into historical performance data and current alerts. These dashboards will show relevant metrics for this object and for contained objects, and further dashboards will become available by selecting within the dashboard. Drill-down from dashboard to dashboard to arrive at the detailed metrics that can assist in finding root-cause.

In particular the 'Local Volume Space Usage Analysis' dashboard will indicate which VMs may have grown rapidly, causing the free space issue.

The recommended minimum free space on volumes containing Hyper-V virtual machine VHD and/or VHDX files:

• 15% free space, if the partition size is less than 1TB

• 10% free space, if the partition size is between 1TB and 5TB

• 5% free space, if the partition size is greater than 5TB

If the disk usage has breached these thresholds then immediate action should be taken to free space, or disk corruption issues can occur.

Use the Alerts View to see all current open issues for this object. Use the Events View to review any error and warning events for this object. Open a Performance View to see the performance metrics for this object and all contained objects. Open a Diagram View to analyze the relationships of this object to other components.

Potential Issues

There follows a list of problems that can affect virtual machines when the Disk is full/approaching full:

• Virtual machine startup failure: Hyper-V host may be unable to create auxiliary files necessary to run a VM.

• Migration failures.

• Checkpoint creation/commit: checkpoints can quickly consume available disk space. If the disk is full, then checkpoint creation, commit, or continued growth may fail causing VM corruption.

• Poor performance: general performance issues can be seen on a disk that is full or approaching full, as many filesystem commands perform poorly when space is limited.

• Unpredictability: various unpredictable issues of stability, performance and file corruption can occur when a datastore is full.

If a Local Volume is full, the following remedial actions can be taken:

• Increase capacity: if the underlying storage system allows, the volume size can be increased.

• Move virtual machines to other storage: you can free space by relocating VMs to alternative storage.

• Add additional disks: You can add additional volumes to hold VMs.

• Remove old Checkpoints: commit and/or delete VM checkpoints to free space. This should of course be reviewed with the VM owner to assess the requirement for the checkpoints history.

• Clean up Local Volume: files not related directly to host/VM operations may be stored on the volume (for example, CD or DVD ISO images). Such files can be safely moved to another location to free space for host/VM files.

External

See the Help Center for more information including reference lists of all Rules and Monitors and User Guide for the Veeam Hyper-V MP.

See the Microsoft Online Documentation for more information on Microsoft Hyper-V.