• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Window's Server Backup, crashing HyperV vms

Joined
Oct 5, 2008
Messages
1,803 (0.29/day)
Location
ATL, GA
System Name My Rig
Processor AMD 3950X
Motherboard X570 TUFF GAMING PLUS
Cooling EKWB Custom Loop, Lian Li 011 G1 distroplate/DDC 3.1 combo
Memory 4x16GB Corsair DDR4-3466
Video Card(s) MSI Seahawk 2080 Ti EKWB block
Storage 2TB Auros NVMe Drive
Display(s) Asus P27UQ
Case Lian Li 011-Dynamic XL
Audio Device(s) JBL 30X
Power Supply Seasonic Titanium 1000W
Mouse Razer Lancehead
Keyboard Razer Widow Maker Keyboard
Software Window's 10 Pro
Hello,

We're backing up a couple of HyperV VM's to external disk, and periodically(about 50% of the time), the VM being backed up will crash during the snapshot process, backup of that component will fail. We're getting;

The disk signature of disk 2 is equal to the disk signature of disk 0
The disk signature of disk 3 is equal to the disk signature of disk 1

warnings in the logs
 
Did you enable full integration services on your VM's? Did you upgrade to the newest version of integrated services? (I still need to do that on my core)

What are the VM's? Are they windows-based? What is the CORE OS version?

I have seen those disk signature errors in logs before, but it hasn't usually been a problem. I do know that if you see that and a bunch of surprise removed entries it is because backup is isolating the data so that it can be backed up.

I've been running Windows Server Backup on my home server with approx 12 VM's for a while now without issue. Though my point of doing it was to expect issues because I've dealt with so many WSB issues in the field. You might check out Veeam Free for a good backup solution. Though when I tested it, it was MUCH slower to backup than WSB was.

Do these VM's have multiple VHD's connected?

Any other errors reported?
 
what is the actual error code? like @Kursah said do these machines have full and updated integration services? Sometimes if there is an update I need to reinstall integration services on the VM machine so that it works correctly.
 
Back
Top