public:data_integrity_check
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
public:data_integrity_check [2020/04/28 11:18] ronnie.chan |
public:data_integrity_check [2020/04/28 12:05] ronnie.chan |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| * With Run Cyclic Redundancy Check (CRC) enabled | * With Run Cyclic Redundancy Check (CRC) enabled | ||
| + | |||
| + | <WRAP indent> | ||
| ==== With Run Cyclic Redundancy Check (CRC) disabled (Default mode) ==== | ==== With Run Cyclic Redundancy Check (CRC) disabled (Default mode) ==== | ||
| + | |||
| 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. | 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. | ||
| - | {{public:dic-v8-01.png}} | + | {{public:dic-v8-01a.png}} |
| <WRAP info> | <WRAP info> | ||
| Line 89: | Line 92: | ||
| * When a backup destination has encountered a hardware failure (e.g. a disk failure on an AhsayCBS user home drive or AhsayOBM/AhsayACB Local destination drive). | * When a backup destination has encountered a hardware failure (e.g. a disk failure on an AhsayCBS user home drive or AhsayOBM/AhsayACB Local destination drive). | ||
| + | |||
| + | </WRAP> | ||
| </WRAP> | </WRAP> | ||
| Line 145: | Line 150: | ||
| * Multiple backup destinations, corrupted items and index-related issues found with correct and incorrect storage statistics. \\ {{public:dic-v8-04.png}} | * Multiple backup destinations, corrupted items and index-related issues found with correct and incorrect storage statistics. \\ {{public:dic-v8-04.png}} | ||
| + | |||
| + | ===== How does Data Integrity Check (DIC) compare with Periodic Data Integrity Check (PDIC) ===== | ||
| + | |||
| + | Periodic data integrity check is performed at the beginning of a backup job, which provides an additional regular data integrity check of the backup data and updates the storage statistics for each backup set. The PDIC feature is enabled from v8.3.2.11 or above and cannot be turned off. This is to ensure a maximum protection of the backup data. | ||
| + | |||
| + | Unlike with the Data Integrity Check (DIC), the PDIC starts automatically and performs a quick check of all the backup destination(s) without the end user intervention. | ||
| + | |||
| + | The PDIC will be initiated automatically once **EITHER** of the following conditions is met: | ||
| + | |||
| + | * Will be triggered on a weekly basis, usually on the first run of backup job that falls on any of these days: Friday, Saturday, or Sunday | ||
| + | | ||
| + | * If there is no active backup job(s) running on Friday, Saturday, or Sunday, then the PDIC will be triggered on the next available backup job | ||
| + | |||
| + | E.g. If the last PDIC job was run more than seven (7) days ago, then the subsequent PDIC job(s) will run seven days from that day onwards. | ||
| + | |||
| + | ==== Comparison ==== | ||
| + | |||
| + | ^ Features ^ Data Integrity Check (DIC) ^ Periodic Data Integrity Check (PDIC) ^ | ||
| + | ^ Runs automatically | <color #ed1c24>X</color> | ✓ | | ||
| + | ^ Allows selection of backup destination(s) | ✓ | <color #ed1c24>X</color> | | ||
| + | ^ Run Cyclic Redundancy Check (CRC) feature | ✓ | <color #ed1c24>X</color> | | ||
| + | ^ Identify and remove the files and/or folders in the backup destination(s) which do not appear in the index | ✓ | ✓ | | ||
| + | ^ Identify and remove the files and/or folders which appear in the index but do not exist in the backup destination(s) | ✓ | <color #ed1c24>X</color> | | ||
| + | ^ Identify and remove partially uploaded (orphan) files from the backup destination(s) | ✓ | <color #ed1c24>X</color> | | ||
| + | ^ (TEST MODE) confirmation screen feature | ✓ | <color #ed1c24>X</color> | | ||
| + | ^ Update Storage Statistics | ✓ | ✓ | | ||
| ===== FAQs ===== | ===== FAQs ===== | ||
| - | * [[public:5004_how_to_run_a_data_integrity_check|How to run a Data Integrity Check for backup data stored in backup destination]] | ||
| * [[public:8008_faq:how_to_run_a_data_integrity_check_on_linux_cli|How to run a Data Integrity Check on Linux (CLI) machine]] | * [[public:8008_faq:how_to_run_a_data_integrity_check_on_linux_cli|How to run a Data Integrity Check on Linux (CLI) machine]] | ||
public/data_integrity_check.txt · Last modified: 2022/11/28 10:06 by kirk.lim