Hyper-V: Virtual machines should be backed up at least once every week
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
One or more virtual machines have not been backed up in the past week.
Impact
Significant data loss might occur if the virtual machine encounters a problem and a recent backup does not exist. This impacts the following virtual machines: <list of virtual machines>
Resolution
Schedule a backup of the virtual machines to run at least once a week. You can ignore this rule if this virtual machine is a replica and its primary virtual machine is being backed up, or if this is the primary virtual machine and its replica is being backed up.
Additional references