1

Hi,

We have a host which has Windows Server 2012 R2 and Hyper V service installed on it. We have 2 VMs configured on the host. We have Altaro VM backup running at 19:00 and Windows backup running at 22:00.

Before each backup we get an event ID 157 (Disk X has been surprise removed). The problem is that after the Windows backup the D drive on both VMs are lost and a restart is required to solve this problem. When we log on to the host machines the hard disk on both servers is still attached but with a bunch of numbers added at the end of the original name. When the servers are restarted Hyper V reports that a merge is in progress and the hard disk then points to the original disk.

Has anyone encountered this problem?

Thanks

3 Spice ups
2

Yes and it was happening because the IP address on our servers where changing. Are the servers set with a static IP?

3

Yes servers are both static. Forgot to mention that the Windows backup is running on the host.
Also both hard disks are on the same IDE controller 0 for both VMs. This evening I will be adding a ISCI controller and moving the D drive to the new controller. Hopefully this resolved the issue.

4

Had that problem when I had both windows backup and Backup Exec running on the same machine. I think the method of backup for one involved a shadow copy of the hard drive which then showed up as another drive that needed backing up to the other backup program, which then was confused when the backup stopped using it and disappeared.

Something like that anyways.

Its stopped happening since I removed windows backup jobs from severs running Backup Exec. I now satisfy my desire for excessive redundancy by running multiple backup jobs to multiple direct-attached, LAN and remote VPNed target locations, but all using just the one product.

5

This happens because of windows backup attribute and CBT attribute are clashing. Better to use only one Backup Mechanism

6

Is the 157 event showing up inside the guest VM or on the host itself?

157 events inside the guest VM are quite normal actually, and can be fixed with a Microsoft rollup which you can read about here: Hyper-V and "Event ID: 157 - Disk x has been surprise removed" | Microsoft Learn

Does this behaviour still occur when running one of the two backup solutions, not both?

7

It seems like the controller was the problem. We moved the secondary disk to a SCSI controller from an IDE controller. We just left the boot disk on the IDE controller and it has been working since then.