Error: XML Node BACKUP_LOCATIONS was not found

[DavidRobertson]

I'm really struggling with this one, Veeam Support have palmed off to Microsoft. Two Hyper V hosts built at the exact same time, shared SAS storage. One single VM fails when it's residing on HV2, move to HV1 and works fine. The error thrown is:

"Error: XML Node BACKUP_LOCATIONS was not found"

Task logs show:
#Logs removed by MOD

Turning application-aware processing on/off makes no difference. I've checked through the file locations etc, it's shared storage so nothing weird there. Hoping someone else has come across this before.

[Mildur]

Hello David

I removed the logs, because they shouldn't be posted here in the forum as explained by the rules.
Can you please post the case number?

I found a solution in a german forum. The Member exported the vm from the HyperV and reimported it.
Backup was successful after that.

Best regards,
Hannes

[DavidRobertson]

05431935

[Mildur]

Thanks.

I found a solution in a german forum. The Member exported the vm from the HyperV and reimported it.
Backup with Veeam was successful after that.

I see, our support engineer has recommended the same. Export the VM, import the VM.
Can you please try this step?

[Ci2Group]

Any fix that does not require downtime ?

[DavidRobertson]

I can't recall specifics but in the end a colleague sorted the Hyper V side with a rebuild of the host.

[Ci2Group]

so we are looking at rebuilding a host or exporting / importing the VM.

There is nothing that can be done to avoid down time?
I don't understand rebuilding the host. This is happening to us on a cluster and only having this issue on 1 VM. Other VMs on the host are backing up fine.

[nozmac]

Hi,

We experienced this issue recently and were able to resolve with the following steps.

1. Migrate all VMs currently on the affected node, to other nodes in the cluster.
2. Navigate to "\\<hyper-v-host-name>\c$\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache"

(NOTE: For each VM hosted on a Hyper-V node, there should be an .xml file and folder associated with each in the location specified above. If you have migrated all the VMs off this node, then the folder should be empty. If this is the case then the issue may not be resolved with these steps)

3. If there are files/folders at "\\<hyper-v-host-name>\c$\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache", then stop the Hyper-V Virtual Machine Management service on the node then rename the folder/files.
4. Start the Hyper-V Virtual Machine Management service.
5. Migrate a VM back to the affected node and re-try the backup.

Hope this helps other facing the same issue.