Hello,
We have ran into a very strange issue. After we upgraded to FR26 our Windows team has been complaining that the Hyper-V nodes are going into non-responsive state during the backups and in some cases they have to force a reboot to bring those nodes and VMs back online. They have provided below data to support their side of the argument:
- The issue is only observed during the backup window.
- While the backups progress, multiple disk/vhdx related error/warning messages are being logged:
- Disk 208 has the same disk identifiers as one or more disks connected to the system.
-
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the GxCVD(Instance001) service. All Commvault services report this.
-
The disk signature of disk 208 is equal to the disk signature of disk 5.
-
DISKPART shows multiple entries like:
Disk 5 Invalid 200 GB 0 B *
-
This was not observed prior to the upgrade we performed.
We have opened a Commvault incident for this. Does anyone here have any clue what might be going on here?
Thank you
Regards
Abdul