we have a Microsoft Hyper-V Cluster with three Hyper-V nodes. Each node has a certain amount of VM's running.
The storage of the VM's is located on a NetApp Filer with iSCSI.
As backup type for the VM's, we have selected "Crash Consistent".
After the start of the backup schedule, all three nodes are starting to create snapshots of many VM's, which causes the VM's to go into suspend mode for snapshot creation.
Due to the simultaneous access to the NetApp Filer, the snapshot creation causes a timeout of the NetApp Filer.
Therefore, the Hyper-V Cluster thinks, that the storage is no more available and crashes. One node is trying to move the VM's to the other node and vice versa. Some VM's are shutdown. Some hang in snapshot creation. After the crash, the we have to clean the incomplete snapshot files, which is a pain.
Is there a solution to this? Maybe, there is an additional setting missing in the CommVault-Configuration. Or, we have to configure something on the NetApp-Filer?
We have three other Hyper-V Servers that host some VM's. But these are standalone with own storage and not in a cluster. The backup/snapshot of the VM's is working well on these.
Any help would be great. Thank you.