This article explains the following points in detail:
What are restore checks
Druva provides restore checks to proactively check the consistency of backed up data or snapshots on a regular basis. This service is implemented in the Druva Cloud. Restore checks are performed periodically on the latest available snapshot for every backup set. If any inconsistencies are found, Druva tries to fix the issues.
When does restore check run
Restore checks are triggered along with the weekly compaction cycle and share the same schedule. If inconsistencies are found for any snapshots, that backup set becomes eligible again for a restore check in the subsequent cycle, which is triggered with every weekly compaction.
Criteria for restore checks
Each backup set undergoes restore checks periodically.
If restore checks for a backup set succeed, the backup set becomes eligible for restore checks again in the next cycle.
If restore checks for a backup set do not succeed or any inconsistencies are found in the snapshot, Druva fixes these inconsistencies.
Restore checks for a newly added backup set are triggered by default in the next scheduled cycle. However, if the first backup of that backup set has not completed, the backup set is skipped and picked up again in the very next cycle.