Reference
Why was my validation evidence run skipped?
Skipped is deliberate: evidence gives way to real work and follows its configured cadence.
ReadyCurrentasuredensevalidationevidence
The Short Answer
Evidence collection is best-effort by design. A run is skipped - not failed - when the VM is busy with conflicting operations, when it is not yet due under the every-N-backups cadence or minimum spacing, or when concurrency limits defer it.
A skip never fails the backup itself, and the next due backup gets another evidence opportunity.
What Controls The Cadence
- Run evidence immediately in the backup pipeline, or defer it to background dispatch.
- Run every N backups, with minimum spacing between runs and optional staggering across VMs.
- A concurrency limit caps simultaneous evidence VMs; each run has an execution timeout.
Related Docs
Recovery Validation And EvidenceThe AsureDense suite: checksum validation, boot and mount evidence after backup, interactive boot sessions, and operator attestations.Recovery PointsHow Sendense represents available points in time for restore, browsing, and recovery workflows.Performance SettingsHow to size SHA concurrency with profiles or custom limits, tune the Backup Data Engine, backup admission, boot-evidence capacity, and replication safety timers.