User Tools

Site Tools

You are here: Ahsay Wiki » Welcome to AhsayWiki » New Index and Backup Process Implementation » New Index and Backup Processes Introduced in Ahsay v8.3
public:new-index-v8:new-processes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
public:new-index-v8:new-processes [2020/04/28 15:04]
ronnie.chan 		public:new-index-v8:new-processes [2020/04/28 15:31] (current)
ronnie.chan
Line 1: Line 1:
-====== New Indexing ​and Backup Processes Introduced in Ahsay v8.3 ======+====== New Index and Backup Processes Introduced in Ahsay v8.3 ======
  
 Four new processes were introduced in the Ahsay Backup Software v8.3.0.0 (or above) to provide better backup performance,​ robustness and data integrity: Four new processes were introduced in the Ahsay Backup Software v8.3.0.0 (or above) to provide better backup performance,​ robustness and data integrity:
Line 11: Line 11:
 ==== 1.1 Index Conversion ==== ==== 1.1 Index Conversion ====
 <WRAP indent> <WRAP indent>
 +~~NOCACHE~~
  
 === For AhsayOBM/​AhsayACB client === === For AhsayOBM/​AhsayACB client ===
Line 118: Line 119:
 Corrupted index files will no longer be recoverable. Corrupted index files will remain in the backup destination(s) and can only be removed by manually running the Data Integrity Check on the AhsayOBM/​AhsayACB client or AhsayCBS Web Console for Run on Server (Office 365 and Cloud File) backups. It is advisable to perform a Data Integrity Check regularly to ensure that NO corrupted data will remain in the backup destination(s). Corrupted index files will no longer be recoverable. Corrupted index files will remain in the backup destination(s) and can only be removed by manually running the Data Integrity Check on the AhsayOBM/​AhsayACB client or AhsayCBS Web Console for Run on Server (Office 365 and Cloud File) backups. It is advisable to perform a Data Integrity Check regularly to ensure that NO corrupted data will remain in the backup destination(s).
 </​WRAP>​ </​WRAP>​
 +
 +===== 3. Post-Backup Data Validation Check =====
 +
 +Although as part of the current backup process, a checksum validation is already performed on the backup files to ensure data integrity and recoverability,​ in addition, to provide peace of mind, an additional post-backup data validation check is now performed in v8.3.
 +
 +The post-backup data validation check will perform the following:
 +
 +1. The number of 16 or 32 MB data blocks in the backup destination(s) is identical to the number of blocks transferred
 +
 +2. The individual sizes of each data block in the backup destination(s) is identical to the sizes of each block transferred ​
 +
 +After performing a backup job, click the {{public:​new-index-v8:​ahsay-backup-software-v83-new-index-implementation-04.png}} button to display the detailed backup log. This will show if the post-backup data validation check has completed successfully. ​
 +
 +The screenshot below shows an example of the post-backup data validation check process in a backup job.
 +
 +{{public:​new-index-v8:​ahsay-backup-software-v83-new-index-implementation-05b.png}}
 +
 +===== 4. Periodic Data Integrity Check (PDIC) =====
 +
 +Data integrity is a core focus of the Ahsay backup software. It is important to maintain the overall accuracy, completeness,​ and consistency of the backup data throughout its lifecycle. To ensure that these objectives are met, Periodic Data Integrity Check (PDIC) is implemented which performs automated error-checking and validation procedures throughout a backup job process. ​
 +
 +Also, as part of the PDIC, the storage statistics for the backup set are recalculated to maintain up-to-date and accurate data usage which guarantees consistent customer billing experience. ​
 +
 +During a backup job, the PDIC is performed to ensure the validity and recoverability of the backup data.
 +
 +This is how the periodic data integrity check (PDIC) will run: 
 +
 +1. At the start of the backup job, the PDIC will check for the physical data blocks (.bak files) in the backup destination(s)
 +
 +{{public:​new-index-v8:​ahsay-backup-software-v83-periodic-data-integrity-check-01.png}}
 +
 +2. If there are physical data blocks (.bak files) found which do not exist in the index (i.e. data blocks with NO related index), then these physical data blocks will be automatically removed from the backup destination(s)
 +
 +{{public:​new-index-v8:​ahsay-backup-software-v83-periodic-data-integrity-check-02b.png}}
 +
 +3. The statistics on the Data area and Retention area are recalculated
 +
 +After the backup job, click the button to display the detailed backup log. This will show if the PDIC had run and completed successfully. There are two possible outcomes in performing the PDIC: 
 +
 +a. The PDIC job is completed without data blocks related issues encountered ​
 +
 +b. The PDIC job has detected data blocks with NO related index
 +
 +**Result 1**
 +
 +The screenshot below shows an example of a backup job where the PDIC has run and has NOT detected any issues on the physical data blocks.
 +
 +{{public:​new-index-v8:​ahsay-backup-software-v83-periodic-data-integrity-check-04b.png}}
 +
 +**Result 2**
 +
 +The screenshot below shows an example of a backup job where the PDIC has run and has identified data blocks (.bak files) which do not exist in the index file. These physical data blocks are automatically deleted from the backup destination(s).
 +
 +{{public:​new-index-v8:​ahsay-backup-software-v83-periodic-data-integrity-check-05b.png}}
 +
 +<WRAP important>​
 +The PDIC only checks for the physical data blocks (.bak files) directly, instead of checking each file in the index, so if there are index files found to be corrupted, then these index files and its associated data blocks can only be removed from the backup destination(s) by manually running the Data Integrity Check on the AhsayOBM/​AhsayACB client or AhsayCBS Web Console for Run on Server (Office 365 and Cloud File) backups. It is advisable to perform a Data Integrity Check regularly to ensure that NO corrupted data will remain in the backup destination(s).
 +</​WRAP>​
 +
 +==== What conditions will trigger a Periodic Data Integrity Check ====
 +
 +During a backup job, the Periodic Data Integrity Check (PDIC) operation will be triggered under **EITHER** of the following conditions:
 +
 +  * Will be triggered on a weekly basis, usually on the first run of backup job that falls on any one 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 7 days ago, then the subsequent PDIC job(s) will run 7 days from that day onwards.
 +
 +==== Which types of backup jobs will initiate a Periodic Data Integrity Check ====
 +
 +Periodic Data Integrity Check (PDIC) can be initiated by the following types of backup job:
 +
 +  * Manual backup job on the AhsayOBM/​AhsayACB client
 +
 +  * Manual backup job on the AhsayCBS Web Console for Run on Server (Office 365 and Cloud File)
 +
 +  * Scheduled backup job on the AhsayOBM/​AhsayACB client
 +
 +  * Scheduled backup job on the AhsayCBS Web Console for Run on Server (Office 365 and Cloud File)
 +
 +  * Continuous backup job on the AhsayOBM/​AhsayACB client
 +
 +  * Continuous backup job on the AhsayCBS Web Console for Run on Server (Office 365 and Cloud File)
 +
 +  * Windows System Tray Icon backup job
 +
 +  * Windows Logout Reminder-initiated backup job
 +
 +  * RunBackupSet.bat script (only applicable for Windows platform)
 +
 +  * RunBackupSet.sh script (only applicable for Linux/​FreeBSD platform)
 +
 +  * AhsayCBS Web Console server-initiated backup job
 +
 +
public/new-index-v8/new-processes.1588057445.txt.gz · Last modified: 2020/04/28 15:04 by ronnie.chan

Page Tools