I'm using CDP since 2 years and have always used the same schedule:
Now since a week or so, I received some strange error messages and realized, that it would also run during nights and doesn't stop at 8 pm as it did in the past. My first idea was that the time on the hosts was completely wrong, but it turned out that the time was fine.
When I try to failover the cdp replicas, I'm able to use the slider for the hours in the night which confirms that replication is taking place at night. Before I create a ticket I would like to know if this scheduler is the only way to set the start and stop for the CDP jobs or if other parameters like short-term retention would affect the scheduler. Thanks!
That sounds unexpected.
I just tested in my lab (v12.1) and CDP worked fine within the specified time period. I don't see any CDP restore point after the allowed time period.
Can you please open a ticket so we can troubleshoot the issue?
According to the R&D team, there are no known issues related to CDP policy and its backup window settings. So, kindly, proceed with a support ticket creation. Thanks!
for whatever reason, this case is going very very slow. Obviously there is some kind of bug as I've provided the logs and now the case got escalated. Hope that a solution will be found soon
I apologize for the delay. Sometimes it takes a little bit longer to find the root cause.
From the case notes I can see unexpected delays of the case from both sites.
Let's hope we can now work more timely on the case with the new escalation engineer.
