public:features:data-integrity-check:home
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
public:features:data-integrity-check:home [2020/04/28 11:59] ronnie.chan created |
public:features:data-integrity-check:home [2020/10/06 17:25] (current) ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Data Integrity Check ====== | + | ====== How does backup data integrity check work in CloudBacko ====== |
| - | ---- | + | |
| Last revision: 2020-04-28 | Last revision: 2020-04-28 | ||
| - | 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, all CloudBacko Pro, Lite and Home come with 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. Cloud storage, FTP / SFTP, or on-premise storage) to ensure that the backup data is recoverable. | + | 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, the latest CloudBacko Pro, Lite and Home come with 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. Cloud storage, FTP / SFTP, or on-premise 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: | 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: | ||
| Line 40: | 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 59: | Line 56: | ||
| This is the default setting of the data integrity check. Running a data integrity check on this mode allows CloudBacko 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 CloudBacko 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:features:data-integrity-check:dic-v8-01-cbk.png}} |
| <WRAP info> | <WRAP info> | ||
| Line 76: | Line 73: | ||
| If there is a discrepancy, this indicates that the file(s) on the backup destination(s) are corrupted. CloudBacko will remove these files from the backup destination(s). If these files still exist on the client machine on the next backup job, CloudBacko will upload the latest copy. | If there is a discrepancy, this indicates that the file(s) on the backup destination(s) are corrupted. CloudBacko will remove these files from the backup destination(s). If these files still exist on the client machine on the next backup job, CloudBacko will upload the latest copy. | ||
| - | {{public:dic-v8-02.png}} | + | {{public:features:data-integrity-check:dic-v8-02-cbk.png}} |
| For large file sizes, a **percentage progress** will be displayed throughout the data integrity check job when this setting is enabled: | For large file sizes, a **percentage progress** will be displayed throughout the data integrity check job when this setting is enabled: | ||
| - | {{public:dic-v8-02b.png}} | + | {{public:features:data-integrity-check:dic-v8-02c.png}} |
| <WRAP info> | <WRAP info> | ||
| Line 114: | Line 111: | ||
| ==== With Run Cyclic Redundancy Check (CRC) disabled (Default mode) ==== | ==== With Run Cyclic Redundancy Check (CRC) disabled (Default mode) ==== | ||
| - | {{public:dic-v8-03.png}} | + | {{public:features:data-integrity-check:dic-v8-03.png}} |
| ==== With Run Cyclic Redundancy Check (CRC) enabled ==== | ==== With Run Cyclic Redundancy Check (CRC) enabled ==== | ||
| - | {{public:dic-v8-05.png}} | + | {{public:features:data-integrity-check:dic-v8-05b.png}} |
| ===== Test Mode Confirmation Screen ===== | ===== Test Mode Confirmation Screen ===== | ||
| Line 147: | Line 144: | ||
| Below is an example of a (TEST MODE) confirmation screen with the following scenario: | Below is an example of a (TEST MODE) confirmation screen with the following scenario: | ||
| - | * 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:features:data-integrity-check:dic-v8-04.png}} |
| ===== 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 170: | 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.1588046391.txt.gz · Last modified: 2020/04/28 11:59 by ronnie.chan
Page Tools
