Return
-
Title
Backups Fail with Error, "Element not found" for Hyper-V VMs -
Description
After installing the Agent service on a Hyper-V host and protecting Hyper-V guests agentlessly, all guest fail to transfer with the follow error message:
Replay.Core.Implementation.Transfer.TransferJob (Transfer ID '2a83f847-6af7-4cb0-8f1f-04a6a540aa71' of volumes [\HyperVVolume\49409B91-42EC-49E4-953E-CA19755F88C6--6135008909153161705,\HyperVVolume\49409B91-42EC-49E4-953E-CA19755F88C6-3692206745,\HyperVVolume\49409B91-42EC-49E4-953E-CA19755F88C6-736362849530939259] from 'AgentName' Job Id = 2a83f847-6af7-4cb0-8f1f-04a6a540aa71:TransferJob)The transfer failed due to an exceptionWCFClientBase.ClientServerErrorException depth 0: Call to service method https://HyperVHost:8006/apprecovery/api/agent/hypervFileProtection/pauseProtection POST failed: File protection failed. Looks like the file with id: DriverFileId: 20, VolumeSerialNumber: 16481149639505876808, FileIdHighPart: 2251799813687511, FileIdLowPart: 0 is not protected. (0x80131500) ---> System.InvalidOperationException depth 1: File protection failed. Looks like the file with id: DriverFileId: 20, VolumeSerialNumber: 16481149639505876808, FileIdHighPart: 2251799813687511, FileIdLowPart: 0 is not protected. (0x80131509) ---> System.ComponentModel.Win32Exception depth 2: Element not found. (0x80004005) -
Cause
After Agent installation, the Hyper-V host was never rebooted. -
Resolution
Although machines can still be protected after the Agent installation, this doesn't mean a backup will be successful. Agent installations require reboots before backups can be successful. To resolve this error message, schedule time to reboot the Hyper-V host.