Skip to main content



How can we help you?


Druva Documentation

Restore Check FAQs

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

What is Restore check?

Restore Check is a feature which enables inSync to proactively check the consistency of backed up data or device snapshots on a regular basis. It was introduced in Druva inSync v5.3 on all the On-Premise editions. (Enterprise, Professional and Private Cloud). It’s a completely server side process and has no bearing on the client device.

Restore checks are performed on the latest available snapshot for every device. If any inconsistencies are found, restore check tries to fix the issues and also a “Restore Check Failed” alert is generated and sent out by the inSync server.                                                                                                                                                                                  

When does Restore Check run?

Restore checks are triggered along with the weekly compaction cycle and share the same schedule. It runs for each device at least once every 30 days.

In cases where inconsistencies are found for any device’s snapshots, that device becomes eligible again for restore check in the subsequent cycle which is triggered with every weekly compaction.                                              

Rules and criteria for Restore Checks:

  1. Each device undergoes restore check at least once every 30 days.
  2. Restore check is triggered with the weekly compaction cycle of their corresponding storages.
  3. If restore check for a device succeeds, then it will become eligible for restore check again only after 30 days.
  4. If restore check for a device does not succeed or any inconsistencies are found in the snapshot, then the device will undergo a restore check again in the very next weekly compaction cycle of its corresponding storage, provided the particular device has also completed another successful backup.
  5. Restore check for a newly added device will be triggered by default in the weekly cycle, however if the first backup of that device has not completed, then it will be skipped and picked up again in the very next cycle.
  6. A “Restore Check Failed” alert email is sent out from the server when it encounters a device for which restore check does not succeed.

NOTE: If a device does not succeed the restore check and another successful backup has not completed before the next weekly compaction cycle, then it will be skipped in the next cycle.               

What to do if you notice a “Restore Check Failed” alert?

Restore check might fail for certain devices. Please contact Support for assistance.

                                                                                                                                                                                Go to top

  • Was this article helpful?