public:features:data-integrity-check:home
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:features:data-integrity-check:home [2020/04/28 12:42] ronnie.chan |
public:features:data-integrity-check:home [2020/10/06 17:25] (current) ronnie.chan |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| * CloudBacko user interface | * CloudBacko user interface | ||
| - | |||
| - | * AhsayCBS Web Console for Run on Server (Office 365 and Cloud File) Backup | ||
| * //RunDataIntegrityCheck.sh// script file (applicable for FreeBSD/Linux (CLI) operating systems only) | * //RunDataIntegrityCheck.sh// script file (applicable for FreeBSD/Linux (CLI) operating systems only) | ||
| Line 149: | Line 147: | ||
| ===== How does Data Integrity Check (DIC) compare with Periodic Data Integrity Check (PDIC) ===== | ===== How does Data Integrity Check (DIC) compare with Periodic Data Integrity Check (PDIC) ===== | ||
| - | |||
| - | Periodic Data Integrity Check (PDIC) 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 v4.1 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 ==== | ==== Comparison ==== | ||
| Line 169: | Line 155: | ||
| ^ Run Cyclic Redundancy Check (CRC) feature | ✓ | <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 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 the files and/or folders which appear in the index but do not exist in the backup destination(s) | ✓ | ✓ | |
| ^ Identify and remove partially uploaded (orphan) files from 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> | | ^ (TEST MODE) confirmation screen feature | ✓ | <color #ed1c24>X</color> | | ||
| ^ Update Storage Statistics | ✓ | ✓ | | ^ Update Storage Statistics | ✓ | ✓ | | ||
public/features/data-integrity-check/home.1588048970.txt.gz · Last modified: 2020/04/28 12:42 by ronnie.chan
Page Tools
