This is an old revision of the document!
Data backup is essential to business or organization and having a data backup plan is only as good as the integrity of the backup data. To ensure that this objective is met, AhsayCBS backup server and AhsayOBM/AhsayACB client provides an improved Data Integrity Check (DIC) feature where the end user can easily verify the integrity of the data stored on the backup destination(s) (i.e. AhsayCBS, Cloud storage, or Local storage) to ensure that the backup data is recoverable.
In backing up large or even small file(s), data corruption may still occur during a backup job or even in a post-backup job. Some of the possible causes are:
Since data corruption is always a possibility, the solution is to identify and then remove corrupted files from the backup destination(s). Identifying and removing corrupted files from the backup destination(s) is mission critical as it measures the integrity of the backup data and its restorability.
The primary role of the Data Integrity Check is to identify and remove corrupted files from the backup destination(s). This will allow the next backup job to have an opportunity to back up these files again. However, corrupted files which are located in the retention area will not be backed up as the source file(s) no longer exists.
Data integrity check CANNOT fix or repair files that are already broken.
Data Integrity Check can be started using the following options:
There are two (2) data integrity check modes:
This is the default setting of the data integrity check. Running a data integrity check on this mode allows the AhsayOBM/AhsayACB client or AhsayCBS backup server to perform a comparison between the files and/or folders on the backup destination(s) and the list of the files and/or folders recorded in the current index file.
When should I run a Data Integrity Check in default mode?
* If you encounter index issues on your backup/restore job * If you know or suspect the backup set storage statistics are not updated or incorrect and cannot wait for the next weekly Periodic Data Integrity Check (PDIC) job * If you need to remove partially uploaded (orphan) files from the backup destination(s) to free up space, as partially uploaded (orphan) files will remain in the backup destination(s) when backup jobs with large files (i.e. database, VMware/Hyper-V, Windows System) backups are terminated unexpectedly or crashes