jorgene wrote:Tried a reboot on the Cluster node that holds the running VM's. Still same problem and Warning errors?
What should i do about this, there is no logic in this.
collinp wrote:I just resolved my CBT issues recently. It turns out that we had some vm's that had 'pending' year old chained VMM checkpoints associated with them. The checkpoints were deleted from VMM by the VM administrators but the vm's were never powered off for a long enough period to let the checkpoints merge properly. If you do a find file *.avhd on c:\clusterstorage\ on a hyper-v host you can see if you still have pending snapshots around. I shutdown the 20 or so vm's one at a time and watched from Hyper-v manager and it took 3 hours for all of checkpoints to merge before I could power the vm's back on. Once I cleaned up all the vmm checkpoints, Veeam CBT began working for everything.
jorgene wrote:Issue resolved after tons of log files sent to support.
According to support this issue will be resolved in future releases.
My solution to this error was to stop and start VeeamFCT service on all Hyper-V nodes that was connected to the CSV that hold VM's that generated warning messages.
Note: rebooting the nodes didn't relove this error, just the stop and start of the VeeamFCT service when nodes are online.
I will try this again as i will soon migrate/Create more VM's to the cluster.
sc stop veeamfct
sc start veeamfct
Users browsing this forum: No registered users and 1 guest