Veeam threat center rpo anomalies

[matteu]

Hello,

I would like to understand why I have VM in the "RPO anomalies" widget on the Veeam threat center because I have backup of them.
I can see several VM in this dashboard. Some have no backup -> dashboard is ok for them.
Some have backup less than 24hours but this dashboard says Never success.

I use TAG as backup method.

Maybe I don't understand something ?

[jorgedlcruz]

Hello Matteu,
Meanwhile I check it with QA, would you mind opening a support case, please?

Thank you!

[matteu]

Case n°07057021

[matteu]

working in progress, I just send database to the support for investigation and I'm waiting the answer !

[jorgedlcruz]

Hello matteu,
Keep working with support. I am aware that we have a hotfix for VMs that exists duplicated in Veeam ONE, for example if you delete and readd the vCenter to VBR, or similar cases.

Perhaps they are related to your case.

Will contact support and they will come back to you.

[matteu]

I have the issue in my lab and a customer also have this issue.
I guess it will be the same fix but let see when I will have an answer

[Dynamic]

Hi matteu,
do you have an update on this? We are running on three different customer environments in the same issue.
Already opened a case - for one customer it's #07366664

All backups are running fine, also replicas. But the RPO Anomalies widget lists last success something around several weeksy/months old, for all backups.
Our workloads are all selected by vSphere tags.

Could be a coincidence, but it's maybe since the update to 12.1.2

[matteu]

They gave me a big sql query to execute

[Dynamic]

Hi matteu,
we received a hotfix today, which should also changed the bu7ild nr. to 12.1.0.3585. I will apply this maybe tomorrow at the customer side.
Best Markus

[matteu]

But yes, I saw this issue on some customer too...
It s not really Nice when you want to give a course to them on the product and you just have to say them sorry but here there is a bug on veeam side sometimes and you need to open a support ticket ^^.
The issue is not "new" but I hope veeam one will have less issue on new version

[Dynamic]

hi matteu and all,
the first provided patch/fix didn’t resolve the customers issue. We have now received a second one.
Due to vacation on customers and also my side, we have to postpone this. I will keep you informed.
Best, Markus

[jorgedlcruz]

Keep us posted, please. We are aiming to have the most possible stable product, but some fixes and bugs can always be discovered on all software out there. Hope the new hotfix helps on your case, Markus, let us know.

[Dynamic]

hi Jorge, i will do
The customer is still on vacation, hence the case has been postponed. It is now assigned to Bogdan, who is awaiting our feedback.
Best, Markus

[Dynamic]

short update: meanwhile the customer had the option to execute the script - but it didn't resolve the issue.
We have now received another query from support, this should restart the collector.

i can see a lot of "delete from [collector].[task] where [uid] in" in this query.
Will keep you informed, as soon the customer or i could run this task against the db.

[Dynamic]

Hi Jorge,
after applying the new query it's getting better. Now we only see anomalies from missing Agent Jobs.

Kamila from support mentioned:
*As far as I know, VMs which are being backed up by Agents, might not have the "correct"/actual protection date in Veeam ONE and this is expected behaviour.*

Unfortunately we have to backup some of these VMs by an agent (for example SQL Cluster). The customer is asking for supporting this in the near future

[jorgedlcruz]

Hello,
Thank you, feedback is noted to consider a workload protected, no matter if agent, backup, snapshot, or even file level job.

It will take some time and some rework of logic, but it makes total sense yes.

Thank you so much, glad to hear now looks a bit better.