Fix for Hyper-V Backup Error 0x80780049 (ID 517)
The error 0x80780049 (ID 517) reported by Windows Server Backup may be due to running a Windows Server 2012 (incl. R2) VM on a Server 2012 (R2) host.
A much better solution is to use BackupChain instead of Windows Server Backup, for many reasons, such as the additional feature set.
To fix your installation on Windows 8 or Windows Server 2012 install hotfix KB2918371:
https://support.microsoft.com/kb/2918371
On Windows 8.1 or Windows Server 2012 R2 install the hotfix KB2919355:
https://support.microsoft.com/kb/2919355
Steps to reproduce this behavior in Windows Server Backup: On a Windows Server 2012 Hyper-v server and a VM running Windows Server 2012
- Run Windows Server Backup on the host
- Select Backup Schedule
- click Custom on the Select Backup Configuration tab
- Select Add Items, select host component and the VM
- You then reboot the host.
The scheduled backup then fails with backup ID 517 and error 0x80780049.
Backup Software Overview
BackupChain 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
- Backup Sichern
- 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
- Hyper-V on RAID is Slow…Why?
- How to Fix: Folder name too long to delete
- Windows Server 2022 ISO Final Release Free Download
- How to Fix VolSnap Error ..a critical control file could not be opened
- Windows Server 2012 Failover Cluster Important Updates
- How to Convert from Dynamic VHD/VHDX Disk Format to / from Fixed in Hyper-V
- Backup too Slow: How to Speed Up Backups
- Hyper-V Integration Services Update: Why You Need to Keep Them Up-to-Date at all Times
- How to fix ‘Microsoft Hyper-V VSS Writer’ is in failed state, Writer Failure code: 0x800423f3
- Destination Path Too Long Fixed: Freeware Tool Deletes Long Path
- How to Install Hyper-V on Windows 8
- 2 Reasons Why Continuous Data Protection (CDP) Isn’t Always A Good Idea for Backups
- KB 2885541 Packet sniffing tool does not sniff all network traffic through port mirroring on Windows 2012 Server VMs
- Avoid Saved State Backup and Check Hyper-V Integration Service Versions Automatically
- How to Shut Down a Hyper-V Virtual Machine
- How to fix: could not create backup checkpoint for virtual machine
- VMware Workstation Speed-Up, How to Fix Slow Performance
- Free Disk2VHD Hyper-V VHDX Physical to Virtual Conversion P2V
- 0x8004230f VSS_E_UNEXPECTED_PROVIDER_ERROR VSS snapshot creation failed
- Fixed vs. Dynamic VHD and VHDX Performance