Article ID: 8120
Reviewed: 29/07/2021

Product Version:
AhsayCBS: 8.3.0.0 or above
OS: All platforms

For backup data that are moved to retention unintentionally (e.g. backup source location (e.g. hard drive / USB drive) disconnected before a backup job or permission settings of files/folders were accidentially revoked):

No.	Type	Timestamp	Log
*	...	...	...
*	warn	YYYY/MM/DD hh:mm:ss	Backup source "%backup_source%" does not exist !
*	...	...	...

Since the AhsayOBM / AhsayACB backup client cannot detect the backup source location or files/folders, they will be treated as deleted by the AhsayOBM / AhsayACB backup client the data on the backup destination(s) will be moved to the retention area. **Where they will be permanently removed after they exceed the retention policy setting for the backup set.**

This document contains instruction on how to rollback such action (e.g. manually un-delete the data), so the data does not need to be re-uploaded again after the backup source drive is reconnected or permission settings of files/folders were corrected.

The following assumptions are made:

• Previous backup was performed on March 20, 2018 01:00:00.
• The backup source drive was disconnected before the sub-sequence backup, performed on March 21, 2018 03:00:00.
• Data backup by the previous job to backup destination AhsayCBS were detect and retain as deleted data.
• You want to revert the data snapshot the previous backup on March 20, 2018 01:00:00.

Important:
It is recommended to temporarily suspend the backup user to ensure that no backup / restore job is performed during the manual un-delete process.

Refer to the following steps to un-delete the data:

1. On the AhsayCBS web console, obtain the backup set ID of the affected backup set:
   
   
   • Under Backup / Restore, select Users, Groups & Policies.
   • Select Backup User, and the corresponding backup user, then Backup Set.
   • Select the affected backup set under Manage Backup Set, the backup set ID is listed under General
     
     
   


2. From the backup destination (e.g. AhsayCBS), browse to the blocks folder where the backup data are stored at:
   
   %backup_destination%\%backupset_id%\blocks
   
   For example
   For backup destination set to AhsayCBS on Windows
   
   E:\user\Username\1517279516004\blocks
   
   
   
   Note:
   A separate folder is created for each backup job according to its start time (YYYY-MM-DD-hh-mm-ss), under the blocks folder.  All files backed up by that job are stored in that particular folder.


3. Remove (or move to another location) all index files in the blocks folder:
   
   
   • %backup_destination%\%backupset_id%\blocks\index.db.*.cgz
   • %backup_destination%\%backupset_id%\blocks\index.metadata.cgz
   
   


4. Copy the index files from a previous backup job folder (the backup snapshot (YYYY-MM-DD-hh-mm-ss) which you would like to revert to), back to the blocks folder.
   
   For example
   To revert the backup snapshot to the backup on March 20, 2018 01:00:00, browse to
   
   E:\user\Username\1517279516004\blocks\2018-03-20-01-00-00
   
   Copy
   
   E:\user\Username\1517279516004\blocks\2018-03-20-01-00-00\index.db.*.cgz
   E:\user\Username\1517279516004\blocks\2018-03-20-01-00-00\index.metadata.cgz
   
   
   To
   
   E:\user\Username\1517279516004\blocks\index.db.*.cgz
   E:\user\Username\1517279516004\blocks\index.metadata.cgz
   
   
   
   Important:
   Once the backup snapshot is reverted, data backup by the latest backup (or sub-sequence backup after the snapshot which you have reverted to) will not be displayed in the restore menu.


5. Ensure that the issue to the backup source drive is resolved, then perform another backup job afterward.