How to Fix: VM cannot be backed up …file groups reported during OnIdentify
A peculiar kind of error occurs whenever a merge operation is taking place and at the same time a VM backup is started:
VM <GUID> cannot be backed up, error -2147212301 (VSS WRITER ERROR RETRYABLE), The virtual machine '<VM Name>' cannot be backed up because either the file groups reported during OnIdentify has changed, or the supported backup type (hot backup or saved state backup) reported during OnIdentify has changed. Try not to perform any configuration changes to the virtual machine between OnIdentify and OnPrepareBackup. (Virtual machine ID <GUID>)
The reason for the error is Hyper-V can’t handle the backup request while a checkpoint is being merged to a running VM.
You’ll need to wait until the merge is completed and then run the backup again.
The merge operation status shows up in the Hyper-V Manager “Status” column next to the VM name to the right.
In addition, Hyper-V logs all these operations in the Event Viewer, look into the logs by navigating through the tree on the left:
Applications and Services Logs -> Microsoft -> Windows -> Hyper-V XXXXXXX
See bottom half of this article: //backupchain.com/hyper-v-backup/Troubleshooting-First-Steps.html
Have you tried BackupChain Hyper-V Backup yet? It’s the all-in-one backup solution for Windows Servers made specifically for IT Professionals. A fully functional trial is available here.
Backup Software Overview
Server Backup SoftwareDownload BackupChain
Cloud Backup
Backup VMware Workstation
Backup FTP
Backup VirtualBox
Backup File Server
Hyper-V Backup
Backup Hyper-VPopular
- Hyper-V Links, Guides, Tutorials & Comparisons
- Veeam Alternative
- How to Back up Cluster Shared Volumes
- DriveMaker: Map FTP, SFTP, S3 Site to a Drive Letter (Freeware)
Resources
- Free Hyper-V Server
- Remote Desktop Services Blog
- SCDPM Blog
- SCOM Blog
- V4 Articles
- Knowledge Base
- FAQ
- Sitemap
- Backup Education
- Archive 2024
- Archive 2022
- Archive 2021
- Archive 2020
- Archive 2018
- Archive 2017
- Archive 2016
- Archive 2015
- Archive 2014
- Archive 2013
- Hyper-V Scripts in PowerShell
- FastNeuron
- BackupChain (Greek)
- BackupChain (Deutsch)
- BackupChain (Spanish)
- BackupChain (French)
- BackupChain (Dutch)
- BackupChain (Italian)
Backup Software List
BackupChain
Veeam
Unitrends
Symantec Backup Exec
BackupAssist
Acronis
Zetta
Altaro
Windows Server Backup
Microsoft DPM
Ahsay
CommVault
IBM
Other Backup How-To Guides
- How to Shut Down a Hyper-V Virtual Machine
- Fix for Error 0x80780049, Backup ID 517
- How to Convert from Dynamic VHD/VHDX Disk Format to / from Fixed in Hyper-V
- Before You Use Carbonite, Mozy, CrashPlan, Rackspace, Softlayer
- Hyper-V Manager: Scheduled Snapshot and Checkpoint Creation
- Copy a File From the Host to a VM Using a Powershell Script
- How to Fix VolSnap Error ..a critical control file could not be opened
- How to fix: VSS snapshot creation failed with result: 80070002 on TrueCrypt Volumes
- How to fix: could not create backup checkpoint for virtual machine
- How to Fix: MSMQ Writer (MSMQ) failed
- Reboot a virtual machine in Hyper-V from the command line
- KB 2885541 Packet sniffing tool does not sniff all network traffic through port mirroring on Windows 2012 Server VMs
- The Ultimate Hyper-V PowerShell Commands Cheat Sheet
- How to Create and Delete Hyper-V Checkpoints / Snapshots
- Windows Server 2025 Direct ISO Download Link
- Backup Strategies for Large VMs with and without Deduplication
- Move Hyper-V VM from Windows 8 to Server 2012 and Vice Versa
- How to Convert VHD Files to VHDX Disks in Hyper-V
- Is My Hard Drive Failing? Signs of Hard Drive Failure
- Fix for Hyper-V Backup Error 0x80780049 (ID 517)