Skip to main content
commvault.com commvault.com
Question

IntelliSnap backup fails on Hyper-V after upgrade from 2016 to 2019

  • August 15, 2025
  • 3 replies
  • 36 views
I
Byte
Forum|alt.badge.img+10

Hi.

A Hyper-V cluster was upgraded from 2016 to 2019 by removing a single host at a time, then reinstalling the server with Windows Server 2019, and joining it to the cluster again. This process was followed with all hosts, one at a time. When all hosts were reinstalled with 2019 and rejoined to the cluster the functional level of the cluster was upgraded to 2019.

 

Job error:

Device not found : [getVolumeInfo failed: Unable to get the volume/device information corresponding to mount point []. Error:[Failed to get extents for GUID:[\\?\Volume{fee5e662-9548-44e6-817a-8927aac20033}] Error:[The device is not connected. ]] (MM.60604)]<br/>Source: prihpv03ap, Process: vsbkp

 

I used Powershell to verify that the GUID above still matches the disk presented on the host and the Mount Path C:\ClusterStorage\XXXXX.

When I present a new SAN disk to the cluster and configure it as a CSV the IntelliSnap backup completes successfully.

Is there some sort of disk identifier that remains on the disk that prevents it from being identified correctly?

 

Thanks.

Ignes

3 replies

J
Vaulter
Forum|alt.badge.img+8
  • Jace RossVaulter
  • Vaulter
  • August 18, 2025

Hi Ignes,

At face value it would appear that it’s implying the GUID isn’t accessible at that time.

Can you confirm a few things for me?
1) can you create a test VM group with a single VM from the failing CSV and see if that works?
2) Confirm, is this happening during snap backup?
3) When you ran the PS commands for the references volume GUID was it run on prihpv03ap?
4) Your Hyper-V client is configured using the cluster name (so it will utilize all member servers)?

 

Cheers,

Jace Ross, Senior Technical SME
I
Byte
Forum|alt.badge.img+10
  • Iggy
  • Author
  • Byte
  • August 18, 2025

Hi Jace,

Find my feedback below:

  1. Still fails with a single VM
  2. The snap backup job fails. If I revert to streaming backup it completes.
  3. The PS commands were executed on all Hyper-V hosts.
  4. All Hyper-V hosts are configured to be used.

Let me know if you require additional information.

 

Regards,

Ignes

 

J
Vaulter
Forum|alt.badge.img+8
  • Jace RossVaulter
  • Vaulter
  • August 18, 2025

With all of the above it looks like everything should be configured correctly.
At this stage I would recommend contacting Commvault support to investigate your snap logging to see why this is being reported as there’s some disconnect between the expected storage and what should be protected.

Jace Ross, Senior Technical SME
Terms & ConditionsCookie settingsAccessibility statement