Restore Corrupted File Backup
Situation
In case some part of file-level backup is accidentally deleted or lost from the backup storage, you can try to restore the intact part of such backup dataset.
Solutions
Solution 1
In case you received the following error codes: 2026, 2029, 2030, 2035, in some cases 1021.
- Perform the repository synchronization or consistency check, as prompted, and then start the restore again.
- For 1021 (inconsistent backup), to correct run the Full backup.
Solution 2
In case you received the following error codes: 2513, 2514.
- As prompted, click Enable 'Ignore Missing Data' option....
Support of this feature depends on backup storage provider and backup plan format.
| Cloud Storage | New Backup Format + Ignore Missing Data | Legacy Backups + Ignore Missing Data |
|---|---|---|
| BackBlaze B2 | ✔️ | ❌ |
| Microsoft Azure | ✔️ | ❌ |
| OpenStack | N/A | ❌ |
| AWS S3 | ✔️ | ✔️ |
| ✔️ | ✔️ | |
| Wasabi | ✔️ | ✔️ |
| Minio | ✔️ | ✔️ |
| S3 Compatible | ✔️ | ✔️ |
| File System | ✔️ | ✔️ |
Now you should be ready to retry the restore procedure.
Once the restore task is complete and the following warnings are reported: 2515, 2534. Now all the files that cannot be restored due to damaged backup chain integrity should be listed and accounted for on the Backup History grid, which is available:
In the Backup Agent on History tab.
In Management Console (Reporting > Backup History, on file view tab of side panel for the completed restore task).
In case there are no backup data that can be restored, you receive the following error codes: 2010, 2035.