Existing Job vs New Job

Discussions specific to Microsoft Hyper-V hypervisor

Existing Job vs New Job

Veeam Logoby svetecs » Fri Jan 19, 2018 1:23 am

I have a server sitting on a Hyper-V Cluster. I have a VeeaM job which points to the cluster to do it's backup. However, VeeaM constantly fails with:

Error: Job failed ('Failed to get the disk information. Failed to open attachment '\\fileserver\disk.vhdx'. Error: 'The process cannot access the file because it is being used by another process.'.'). Error code: '32774'. Failed to get information about vhd disk '\\fileserver\disk.vhdx'. Failed to get shared disks extents Failed to enumerate VM disks. Failed to get informa

Other VM's within the Cluster backup fine, regardless of if they're 2012, 2012 R2 or 2016.

So I create a new job, and directly backup the VM (selecting the actual VM, not via the Cluster object). This runs without error.

Within the cluster, there are around 5 VM's exhibiting this behaviour.

What do I need to do to get VeeaM to process these VM's correctly?

Posts: 1
Liked: never
Joined: Tue Jan 16, 2018 12:18 am
Full Name: Stan Svetec

Return to Microsoft Hyper-V

Who is online

Users browsing this forum: No registered users and 7 guests