Werk #22468: Veeam CDP jobs: Show result of the last session and age of the last restore point
| Component | Checks & agents | ||
| Title | Veeam CDP jobs: Show result of the last session and age of the last restore point | ||
| Date | Oct 14, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The VEEAM CDP Job services reported Time since last CDP Run based on the
wrong value. The Windows agent plug-in sends the policy's next scheduled run
(NextRun), but the check treated it as the time of the last run. A CDP policy
replicates continuously, so NextRun only contains the time of the query: the
age shown was meaningless, and the service could go WARN with "The timestamp
of the file is in the future".
In addition, a failing CDP policy was shown as OK: on Veeam Backup &
Replication 13 the policy state is only InitialSync, Running or Disabled,
so the check never saw a failure. InitialSync was reported as UNKN.
What changed
The services now show:
- the policy state, with
InitialSyncbeingOK - the result of the last finished session of the policy (
WarningisWARN,FailedisCRIT). Veeam closes a CDP session about once a day and records in its result, for example, an exceeded RPO, failed long-term restore points or a powered-off source VM. - the time since the last long-term restore point. For a policy with several replicas, the oldest of their latest long-term restore points is used.
The time of the next run is no longer shown.
The ruleset Veeam: Time since last CDP run is renamed to Veeam: Time since
last CDP long-term restore point. Your existing rules are kept. Disabled
policies stay OK: they are not checked for their age, and the result of their
last session is only shown in the details.
The time since the last long-term restore point does not reflect the RPO: CDP replicates continuously, while long-term restore points are created on their own schedule, by default every 8 hours. Long-term restore points that Veeam created incomplete are counted as well. Review the default levels of 30/48 hours against the schedule of your policies.
Action required
Redeploy the Veeam agent plug-in (veeam_backup_status.ps1) on your Veeam
servers, e.g. by baking and updating the agents. Until then, the services only
show the policy state, and your levels are not applied.
Note that the updated agent plug-in requires a Checkmk server that includes this werk. Older servers will lose the VEEAM CDP Job services.