Commvault is trying to consolidate the same VM several times
Hello
Apparently, after successfully backing up some VMs (VMware), commvault is requesting disk consolidation several times in a row (without waiting the first request to finish).
This sometimes is causing the VM to be unresponsive. Commvault is being proactive but it is causing downtimes to the environment.
1 - can I disable this feature (commvault starting consolidation tasks for the VMs that needs consolidation)?
2 - can Commvault skip this VM? I read that commvault would skip VMs that needs disk consolidation. But I am not sure if this is really happening.
regards,
Pedro
Page 1 / 1
Hi @PedroRocha ,
We cannot skip this otherwise the next backup would fail.
So, that additional settings default is 3, which value to use?
I found another named bConsolidateVM and set it to false to stop this (environment is suffering a lot).
This whole story is very awkward. Commvault it causing a lot of downtimes in the environment due to this consolidation tasks in a row. It seems to be doing what it shouldn't.
I have an opened case 230614-623
take a look at this:
HI @PedroRocha ,
Well Commvault is only sending the API request, same for taking/removing Snapshots, so the real question is why this is taking so long for VMWare to consolidate the VM.
You can set it to 6 for now. However I would recommend you log a case with VMware so they can investigate. Of course you can log a case with us so we can work with VMware.
Best Regards,
Sebastien Merluzzi
cvlt dev is reviewing, I'll update it here
So you logged a case with Vmware also?
So you logged a case with Vmware also?
No yet. Consolidation is taking long because of factors like storage array performance and old snapshots (big deltas).
The big question is why commvault keeps sending consolidation tasks even when there is an active consolidation task in place. CVLT suspects VMware is not telling commvault to stop. I believe cvlt dev will verify and if needed we will involve VMware support.
Correct, a few things can cause this.
Same for taking/removing snapshots, if time is over then we try again.
Let’s see what Dev say then and if we have a way to stop it.
We are also facing same issues with multiple disk consolidation jobs being triggered by service account used by commvault, however, backup has been disabled ever since VM started report disk consolidation errors.
Please let me know if there is any solution or workaround.
Hi,
Dev is still working on it…
I set the bConsolidateVM additional setting to false so Commvault wouldn't start consolidation tasks at all.
VMware admin is doing it...
Hello,
We have the same issue in our environment. Also we have a ticket open.
Do you have NVMe Datastores presented on your VMWare ?
Hi,
Dev is still working on it…
I set the bConsolidateVM additional setting to false so Commvault wouldn't start consolidation tasks at all.
VMware admin is doing it...
Thank you, we just added same additional settings.
@PedroRocha what was the outcome of the ticket? we occasionally have the same issue and when we consolidate the ones who failed ourselves than it is done in a split second. Upon consolidation failure it seems it is indeed really impacting the availability of the VM.
@Onno van den Berg ,
Development has created a Hotfix.
MR87 has been released which includes the hotfix that was part of MR85.
@clariion Perfect, will ask colleague to provide hotfix to confirm this is installed as part as MR89.
Meanwhile, you can set bConsolidateVMadditional setting.
@PedroRocha Did installing MR85+ fix it?
@clariion Perfect, will ask colleague to provide hotfix to confirm this is installed as part as MR89.
Meanwhile, you can set bConsolidateVMadditional setting.
@PedroRocha Did installing MR85+ fix it?
Hello, haven't tested yet
@PedroRocha ok, or you can install 28.91 as @clariion confirmed After installing 11.28.91 all consolidation errors stopped.
@Sebastien Merluzzi unfortunately there is no way to relate forward port fixes in the maintenance releases of newer versions hence this fix is not mentioned in the release notes of the maintenance releases for FR30 and FR32. Can you please share the related fix numbers so we can pinpoint which maintenance releases should contain the fix. You mentioned the maintenance releases, however we ran into issues even after being on mentioned maintenance release, so or we hit another issue related to the same which was addressed by another fix.