Help understanding the CDP Job RPO SLA reporting in VBR

[kevin.boddy]

Hi,

I have a CDP job with 5x VMs configured.
When the CDP job is enabled, you see the 5x VMs under the Running status and double-clicking each one you can see their RPO SLA status is 100%.
Under the CDP Job view you can also see the RPO SLA status is 100% for the entire job.

What I have seen is that if one of the VMs stops working, for whatever reason, that VM will not show under the Running status.
The other 4x VMs will showing under Running, and you can see their RPO SLA as 100%.
If you go to the CDP Job view, the job RPO SLA is still reported as 100%.

Why is the logic for the CDP Job view RPO SLA to only count the RPO SLAs of the Running VMs?
Would it not be more logical to show the RPO SLA for the CDP Job based on all the VMs configured within the job?
Therefore, if only 4 out of 5 VMs is actually Running, the CDP Job view would only show an RPO SLA of 80% maximum.

Thanks
Kevin

[veremin]

Actually, what you're describing doesn't seem like expected behavior for us — in general, if a machine stops replicating, it will reduce its SLA to zero, plus it will affect the SLA of the entire policy.

Therefore, we would recommend that you open a ticket with our support team and provide the ticket number here so that we can take a look at what went wrong in your case.

Thanks!

[kevin.boddy]

Thanks. I've logged a case #07630755. Let's see what they find.

[veremin]

Thank you, we will also review your case and join the investigation if our assistance is needed.