Skip to content

Commit feab511

Browse files
committed
updates
1 parent 542786f commit feab511

2 files changed

Lines changed: 23 additions & 11 deletions

File tree

support/windows-server/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2726,6 +2726,8 @@ items:
27262726
href: ./virtualization/back-up-restore-hyper-v-vm-bmr-data-backup.md
27272727
- name: Back up virtual machines from parent partition
27282728
href: ./virtualization/back-up-hyper-v-vm-from-parent-partition.md
2729+
- name: Troubleshoot Hyper-V virtual machine backup, checkpoint, and storage failures
2730+
href: ./virtualization/hyper-v-virtual-machine-backup-checkpoint-storage.md
27292731
- name: Configuration of virtual machine settings
27302732
items:
27312733
- name: Copy and paste don't work when you connect to Hyper-V virtual machine

support/windows-server/virtualization/hyper-v-virtual-machine-backup-checkpoint-storage.md

Lines changed: 21 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,19 @@ ms.custom:
1414

1515
This article provides a comprehensive guide to troubleshooting common issues encountered with Hyper-V virtual machine (VM) backup, checkpoint management, and storage failures in Windows Server environments (Windows Server 2016, Windows Server 2019, and Windows Server 2022). These issues often arise during backup or restore operations, checkpoint creation or merging, VM startup, and storage connectivity. They can impact both production and disaster recovery workflows in standalone Hyper-V hosts, clustered setups, and environments integrated with third-party backup tools. Timely identification and resolution are critical to maintaining VM availability, data integrity, and backup reliability.
1616

17-
You might encounter the following symptoms in affected environments:
17+
You might experience:
18+
19+
- Inability to perform backups or restores, leading to potential data loss.
20+
- Unexpected VM downtime or loss of access.
21+
- Orphaned disk files causing storage exhaustion.
22+
- Persistent warning or error states in management consoles.
23+
24+
In addition, you might encounter the following symptoms in affected environments:
25+
26+
- [Backup and restore failures](#backup-and-restore-failures)
27+
- [Checkpoint and snapshot issues](#checkpoint-and-snapshot-issues)
28+
- [VM startup or migration failures](#vm-startup-or-migration-failures)
29+
- [Storage and file system errors](#storage-and-file-system-errors)
1830

1931
## Backup and restore failures
2032

@@ -58,14 +70,15 @@ You might encounter the following symptoms in affected environments:
5870
- > Cannot connect to virtual machine configuration storage
5971
- > The virtual machine is not in a valid state to perform the operation.
6072
61-
## User experience
73+
The root causes of these issues can be grouped into the following categories with corresponding resolutions provided:
6274

63-
- Inability to perform backups or restores, leading to potential data loss.
64-
- Unexpected VM downtime or loss of access.
65-
- Orphaned disk files causing storage exhaustion.
66-
- Persistent warning or error states in management consoles.
75+
- [Checkpoint and VSS-related issues](#checkpoint-and-vss-related-issues)
76+
- [File system and storage problems](#file-system-and-storage-problems)
77+
- [Permissions and policy misconfiguration](#permissions-and-policy-misconfiguration)
78+
- [Cluster and configuration issues](#cluster-and-configuration-issues)
6779

68-
The root causes of these issues can be grouped into the following categories, with corresponding resolutions provided.
80+
> [!NOTE]
81+
> Always back up critical VMs before performing file merges, deletions, or major configuration changes. For further assistance, consult Microsoft Support or your backup vendor.
6982
7083
## Checkpoint and VSS-related issues
7184

@@ -186,7 +199,7 @@ The root causes of these issues can be grouped into the following categories, wi
186199
In Hyper-V Manager, use **Import Virtual Machine** and locate the exported/imported files.
187200
3. Update VM configuration version:
188201
189-
In Hyper-V Manager, right-click the VM, and select **Upgrade Configuration Version**. Or use the folowing PowerShell cmdlet:
202+
In Hyper-V Manager, right-click the VM, and select **Upgrade Configuration Version**. Or use the following PowerShell cmdlet:
190203
191204
```powershell
192205
Update-VMVersion
@@ -225,6 +238,3 @@ To assist with troubleshooting, collect the following items:
225238
- [Backing up and restoring virtual machines](/windows/win32/hyperv_v2/backing-up-and-restoring-virtual-machines)
226239
- [Antivirus exclusions for Hyper-V](antivirus-exclusions-for-hyper-v-hosts.md)
227240
- [PowerShell Hyper-V cmdlets](/powershell/module/hyper-v/)
228-
229-
> [!NOTE]
230-
> Always back up critical VMs before performing file merges, deletions, or major configuration changes. For further assistance, consult Microsoft Support or your backup vendor.

0 commit comments

Comments
 (0)