Resources For IT Professionals
Page Details
Options

Revision #2

Wiki  >  TechNet Articles  >  Hyper-V: Recovery snapshots should be removed after failover  >  Revision #2
Hyper-V: Recovery snapshots should be removed after failover
You are currently reviewing an older revision of this page.
Go to current version

Table of Contents



This article is intended to provide more information about a specific issue that can be identified by running a Best Practices Analyzer scan for Hyper-V. It also can be used without running a scan, as general troubleshooting and best practice information to help you configure your server appropriately. If you have troubleshooting steps or information that would improve this article, please add it. For instructions on how to edit a TechNet Wiki article, see Wiki: How to Use the Editor.

For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.

Operating System

Windows Server 2012

Product/Feature

Hyper-V

Severity

Category

Note: The following sections provide details about the specific issue. Italics indicates UI text that appears in the Best Practices Analyzer tool for the specific issue.

Issue

A failed over virtual machine has one or more recovery snapshots.

Impact

Available space may run out on the physical disk that stores the snapshot files. If this occurs, no additional disk operations can be performed on the physical storage. Any virtual machine that relies on the physical storage could be affected. This impacts the following virtual machines: <list of virtual machines>

Resolution

For each failed over virtual machine, use the Complete-VMFailover cmdlet in Windows PowerShell to remove the recovery snapshots and indicate failover completion.

Additional references