Data Integrity Check Overview for AhsayACB

---

Data Integrity Check

The Data Integrity Check (DIC) is used to identify the data in the backup set that has index-related issues, remove any corrupted file(s) from the backup destination(s) to ensure the integrity of the backup data and its restorability, and update the storage statistics.

For an efficient management of overall storage size of the backup destination(s), the Data Integrity Check job will perform check for the backup destination(s) to remove old index files that are more than ninety (90) days old in the backup job folder(s).

Run Cyclic Redundancy Check (CRC)

When this option is enabled, the DIC will perform a check on the integrity of the files on the backup destination(s) against the checksum file generated at the time of the backup job.

If there is a discrepancy, this indicates that the files on the backup destination(s) are corrupted and will be removed from the backup destination(s). If these files still exist on the client machine on the next backup job, the AhsayACB will upload the latest copy of the files.

However, if the corrupted files are in the Retention Area, they will not be backed up again as the source file has already been deleted from the client machine.

The time required to complete a Data Integrity Check depends on several factors, including:

• Number of files and/or folders in the backup set(s)
• Bandwidth available on the client computer
• Hardware specifications of the client computer, such as disk I/O and CPU performance

---

Rebuild Index

When this option is enabled, the DIC will start rebuilding corrupted index and/or broken data blocks if there are any.

---

Delete Corrupted Data Blocks Permanently

When this option is enabled, it overrides the Recycle Bin setting of the backup set. The DIC will delete corrupted data blocks permanently instead of moving it to the Recycle Bin.

There are four (4) options in performing the Data Integrity Check:

Settings	Function
Option 1	For checking of index and data.
Option 2	For checking of index and integrity of files against the checksum file generated at the time of the backup job.
Option 3	For checking and rebuilding of index.
Option 4	For checking of index, integrity of files against the checksum file generated at the time of the backup job and rebuilding of index.

The following diagrams show the details process of the Data Integrity Check (DIC) in four (4) modes:

• Option 1

  Disabled Run Cyclic Redundancy Check (CRC) and Rebuild index - (Default mode)

• Option 2

  Enabled Run Cyclic Redundancy Check (CRC) and Disabled Rebuild index

• Option 3

  Disabled Run Cyclic Redundancy Check (CRC) and Enabled Rebuild index

• Option 4

  Enabled Run Cyclic Redundancy Check (CRC) and Rebuild index

---

Data Integrity Check (DIC) Process with Run Cyclic Redundancy Check (CRC) and Rebuild Index Disabled (Default Mode)

---

Data Integrity Check (DIC) Process with Run Cyclic Redundancy Check (CRC) Enabled and Rebuild Index Disabled

---

Data Integrity Check (DIC) Process with Run Cyclic Redundancy Check (CRC) Disabled and Rebuild Index Enabled

---

Data Integrity Check (DIC) Process with Run Cyclic Redundancy Check (CRC) and Rebuild Index Enabled

---

Perform a Data Integrity Check

1. Go to the Data Integrity Check tab in the “Utilities” menu.

   

2. Click the drop-down button to select a backup set.

   

3. Click the drop-down button to select a backup destination.

   

4. Click the Start button to begin the Data Integrity Check.

5. Provide the passcode for 2FA.

   

   The passcode will only be required if the backup user acocunt is set up with 2FA. Otherwise, proceed to the next step.

6. The Data Integrity Check will start running on the selected backup set(s) and backup destination(s).

   

7. Once the DIC is completed, click the View log button to check the detailed process of the Data Integrity Check.

   

   The detailed log of Data Integrity Check process will be displayed.

   

   The following options can be used for further viewing of the detailed DIC log:

   • Log filter

   • Show filter

   • Logs per page

   • Page

   

   Settings	Screenshot	Function
   Log filter		This option is used to display the logs of the previous Data Integrity Check jobs.
   Show filter		This option is used to sort the Data Integrity Check log by its status (i.e., All, Information, Warning, and Error). With this filter, it will be easier to sort the DIC logs by its status especially for longer Data Integrity Check logs.
   Logs per page		This option allows user to control the displayed number of logs per page.
   Page		This option allows user to navigate the logs to the next page(s).

   If the backup destination used for storing the backup set is an immutable destination, then the backup user account must be setup with 2FA in order to delete corrupted data blocks. If the backup user account does not have 2FA, DIC will proceed but there will be a warning in the logs since deleting of corrupted data blocks will not be allowed.

---

Data Integrity Check Completed with Errors

The following screenshot is an example of a Data Integrity Check completed with error(s). A Data Integrity Check is run on a backup set with an active backup job running which resulted in the Data Integrity Check to stop with error(s).

Clicking the View log button will display the details of the Data Integrity Check job error(s).

---

Data Integrity Check Result

There are two possible outcomes after the completion of a Data Integrity Check:

• Data Integrity Check is completed successfully with no data corruption or index-related issues detected;

• Corrupted data (e.g. index files, checksum files, and/or broken data blocks) has been detected

The screenshot below shows an example of a Data Integrity Check log with NO data corruption or index-related issues detected.

If any index-related error(s) or data corrupted item(s) is found, the (TEST MODE) confirmation screen will be displayed.

This is to inform the user of the following details:

• Backup set that contains an error

• Backup Destination

• Items found in index

• Data corrupted items

• Index broken data blocks

• Statistics (i.e. Correct or Incorrect)

---

Test Mode Confirmation

The (TEST MODE) confirmation screen will ONLY appear if either of the criteria below matches the backup data during the Data Integrity Check process:

• Deleted number of backup files is over 1,000

• Deleted number of backup file size is over 512 MB (in total)

• Deleted number of backup files is over 10% of the total backup files

Otherwise, the Data Integrity Check job will automatically take corrective actions.

There are three (3) options on the (TEST MODE) confirmation screen:

Option	Screenshot	Function
Yes		Corrupted data (e.g. index files, checksum files and/or broken data blocks) will be deleted and storage statistics will be updated.
No		No action(s) will be taken and a message will prompt.
View log		The detailed log of the Data Integrity Check process will be displayed.

Clicking No will display the following screen:

If the Exit button is clicked, the data integrity check result will be discarded.

If the Back button is clicked, it will go back to the (TEST MODE) confirmation screen.

Aside from viewing the Data Integrity Check logs directly on AhsayACB client, they can also be viewed on the file system of the AhsayACB client machine. For AhsayACB, the DIC logs are located in the following directory:

%UserProfile%\.acb\system\IntegrityCheck (Windows)
$UserProfile/.acb/system/IntegrityCheck (macOS)