Discussions specific to the VMware vSphere hypervisor
Post Reply
Seif
Lurker
Posts: 2
Liked: never
Joined: Sep 19, 2018 3:12 pm
Full Name: Seifallah DALI
Contact:

Failed to get information about vhd disk. Error Code:'32774

Post by Seif »

Hello,

I have a VM running in a cluster Hyper-V. I have Veeam B&R 9.5 and the bakup is constantly failed with this error:
(Error code: '32774'. Failed to get information about vhd disk 'C:\ClusterStorage\CSV02\TE-SRV-SFB02\TE-SRV-SFB02.vhdx'. Failed to get shared disks extents Failed to enumerate VM disks. Failed to get information about VM '4d480a4b-4717-4dfd-9152-3122913163da')

The backup for the other VM was successfully done.

Regards.

wishr
Veeam Software
Posts: 1747
Liked: 195 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to get information about vhd disk. Error Code:'32774

Post by wishr »

Hi Seif,

Welcome to Veeam community forums and thank you for the question.

Please note, that according to Veeam forum rules, you should include support case ID when posting about any technical issue, as requested when you click the "New topic" button. Please post your support case ID once you get one in the original post in this thread, we'll keep an eye on it.

Thanks,
Fedor

Seif
Lurker
Posts: 2
Liked: never
Joined: Sep 19, 2018 3:12 pm
Full Name: Seifallah DALI
Contact:

[Case ID 03202533] Failed to get information about vhd disk. Error Code:'32774

Post by Seif »

Hi Fedor,

thank you for your thinning, I just put the ID [03202533] in the subject box

Best regards,

doublejay
Novice
Posts: 5
Liked: never
Joined: Aug 09, 2019 12:58 pm
Contact:

Re: Failed to get information about vhd disk. Error Code:'32774

Post by doublejay »

Hello,

how was this case solved?

Cheers,
JJ

wishr
Veeam Software
Posts: 1747
Liked: 195 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to get information about vhd disk. Error Code:'32774

Post by wishr » 1 person likes this post

Hi Jan,

According to the support ticket notes, there was an issue related to Hyper-V and it faded away after maintenance on the hypervisor side.

Thanks

Post Reply

Who is online

Users browsing this forum: No registered users and 28 guests