Why is this marked as red (issue) in the admincinsole if the backup did run and completed successfully? (now it’s MAr 14, 5PM)
Best answer by Bart
View originalWhy status red
Userlevel 6
+13
Userlevel 7
+19
- Commvault Certified Expert
- 1049 replies
-
14 March 2021
Hi
What is the feature release version you are running on? Reason for asking is that this particular functionality is being improved/enhanced as we speak. If you hover over the red text then it should display the root cause. Are you using FS agent level backup? These two are currently still connected so if there is an issue with FS it could become visible in Virtualization as well.
Userlevel 6
+13
11.22.13 .
The examples above are simple VM backups. So no agent.
Userlevel 6
+13
If I click on it (not hover, that doesn’t show anything), I see:
Job ID...0...doesn’t make sense, but last successful backup is OK.
So it seems to be yet another bug.
Userlevel 7
+23
- Vaulter
- 4998 replies
-
15 March 2021
Hey
I have reached out to some resources internally, though any context you can provide will help.
Userlevel 6
+13
within Admin center → Protect → virtualization:
In 11.21 this was working correctly as far as I remember
Userlevel 7
+23
- Vaulter
- 4998 replies
-
15 March 2021
Thanks,
Userlevel 7
+19
- Commvault Certified Expert
- 1049 replies
-
15 March 2021
Userlevel 6
+13
Thanks,
Yes and no.
We have agents with plans , and we have agents without plans, both giving the same problem.
the last backup field, as mentioned previously , also proves the backup did run:
Userlevel 6
+13
they are really all wrong, and because of that, I’m 100% sure it was working fine with 11.21, and not with 11.22
Userlevel 6
+13
also, one which DOES fail, doesn’t have that red status:
=> failing since Feb 9
=> Last backup is in black instead of “red”...
Userlevel 7
+19
- Commvault Certified Expert
- 1049 replies
-
15 March 2021
Not sure if you already opened a ticket, but I think it is time to contact support!
Userlevel 6
+13
Not sure if you already opened a ticket, but I think it is time to contact support!
It’s commvault, so we opened hundreds of tickets already 
Userlevel 7
+23
- Vaulter
- 4998 replies
-
15 March 2021
Edit: I found your case, so I’ll keep an eye on it as well, though feel free to update the thread before me!
+1
I see this frequently in my environment if we have a subclient configured that doesn’t result in any VM’s being backed up. The snap job will show successful and the backup copy will show failed to start because there was nothing to copy.
For example: If I have a subclient configured to back up a certain datastore, but all of the VM’s on that datastore are excluded for whatever reason. The job still runs every day and shows successful, but nothing gets backed up, and the backup copy job shows “Failed to Start”.
Userlevel 7
+19
- Commvault Certified Expert
- 1049 replies
-
15 March 2021
I have already made complains that setting this on global level really doesn't make sense. Especially when you take into account public cloud. Example would be Amazon EC2 IntelliSnap in where the snapshots are offloaded by Amazon from the primary storage to S3 and where snapshots do not have a tight/direct relationship anymore with the source. There are many environments and cases in where this satisfies the requirements so in these situation you want to tick the checkbox. Now what if your CommCell spans Amazon and Azure, Amazon and VMware and what if you are a MSP? In all these cases you want to be able to set it on a plan level.
But maybe this setting helps solving your challenge ;-)
Userlevel 6
+13
Development said that this issue should be resolved in FR/SP23.
Userlevel 7
+19
- Commvault Certified Expert
- 1049 replies
-
16 March 2021
So that it mean that they will not create a backport of the fix to previous releases? Because it will take time for FR23 to mature and become GA and also you will most likely get something else for it in return.
Userlevel 7
+23
- Vaulter
- 4998 replies
-
16 March 2021
Thanks,
Appreciate you updating us all!
Userlevel 6
+13
So that it mean that they will not create a backport of the fix to previous releases? Because it will take time for FR23 to mature and become GA and also you will most likely get something else for it in return.
They are checking for a backport. Will let you kno.
Userlevel 6
+13
It’s resolved with diag 2302 for FR22, and should be part of FR23 already. After installing the fix, you won’t see the difference immediately, but you will see it after a while. (next backup most probably).
Case closed.
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.