User Tools

Site Tools


public:8020_faq:faq_about_ahsay_cloud_backup_suite_8

Differences

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

Link to this comparison view

public:8020_faq:faq_about_ahsay_cloud_backup_suite_8 [2019/01/31 14:44]
edward.chan created
public:8020_faq:faq_about_ahsay_cloud_backup_suite_8 [2019/01/31 14:59] (current)
edward.chan
Line 1: Line 1:
 +=====  FAQ: Frequently Asked Questions about Ahsay Cloud Backup Suite 8   =====
  
 +<​html>​
 + <​b>​
 +  Article ID:
 + </​b>​
 + 8020
 + <​br/>​
 + <​b>​
 +  Reviewed:
 + </​b>​
 + ​31/​01/​2019
 + <​br/>​
 + <​br/>​
 + <​b>​
 +  Product Version:
 + </​b>​
 + <​br/>​
 + Ahsay Software: 8.1 or above
 + <​br/>​
 + OS: All platforms
 +</​html>​
 +
 +===== Description =====
 +The following are some Frequently Asked Questions on Ahsay Cloud Backup Suite.
 +
 +<​html>​
 + <​b>​Table of Contents</​b>:​
 + <​ol>​
 +  <​li><​font color=black>​
 +   <a href="#​Which%20cloud%20storage%20services%20are%20supported%20by%20AhsayCBS%20(Cloud%20Backup%20Suite)?">​
 +    Which cloud storage services are supported by AhsayCBS (Cloud Backup Suite)?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​How%20do%20I%20perform%20a%20backup%20to%20a%20local%20destination%20then%20import%20the%20data%20onto%20a%20cloud%20storage%20destination%20(e.g.%20seed%20load)?">​
 +    How do I perform a backup to a local destination then import the data onto a cloud storage destination (e.g. seed load)?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​How%20do%20I%20start%20AhsayOBM%20in%2032bit%20mode%20(to%20create%20an%20Exchange%20mail%20level%20backup%20set%20or%20to%20start%20a%20mail%20level%20backup%20job)?">​
 +    How do I start AhsayOBM in 32bit mode (to create an Exchange mail level backup set or to start a mail level backup job)?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​How%20do%20I%20start%20a%20data%20integrity%20check%20for%20backup%20data%20stored%20in%20the%20backup%20destination?">​
 +    How do I start a data integrity check for backup data stored in the backup destination?​
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Backup%20account%20profiles%20are%20stored%20in%20a%20new%20format,​%20can%20you%20explain%20on%20the%20new%20changes?">​
 +    Backup account profiles are stored in a new format, can you explain on the new changes?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Backup%20data%20are%20stored%20in%20new%20structure,​%20can%20you%20explain%20on%20the%20new%20changes?">​
 +    Backup data are stored in new structure, can you explain on the new changes?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Can%20backup%20accounts%20of%20version%206.x%20be%20migrated%20to%20version%208%20or%20above?">​
 +    Can backup accounts of version 6.x be migrated to version 8.1 or above?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Which%20version%20of%20Java%20is%20bundled%20with%20AhsayCBS%20(Cloud%20Backup%20Suite)?">​
 +    Which version of Java is bundled with AhsayCBS (Cloud Backup Suite)?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Cannot%20install%20AhsayACB%20on%20a%20Windows%20server%20operating%20system,​%20why?">​
 +    Cannot install AhsayACB on a Windows server operating system, why?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Can%20I%20create%20multiple%20backup%20sets%20for%20my%20AhsayACB%20account?">​
 +    Can I create multiple backup sets for my AhsayACB account?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Retained%20data%20are%20not%20cleared%20according%20to%20the%20retention%20policy%20configured?">​
 +    Retained data are not cleared according to the retention policy configured?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Can%20I%20deploy%20an%20unofficial%20hotfix%20or%20a%20custom%20version%20to%20AhsayOBM%20/​%20ACB%20clients%20using%20the%20Auto%20Update%20Agent%20(AUA)?">​
 +    Can I deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients using the Auto Update Agent (AUA)?
 +   </​a>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <a href="#​Can%20I%20modify%20settings%20of%20the%20system%20routine%20jobs%20(e.g.%20enable%20/​%20disable,​%20start%20time,​%20job%20specific%20settings)?">​
 +    Can I modify settings of the system routine jobs (e.g. enable / disable, start time, job specific settings)?
 +   </​a>​
 +  </​font></​li>​
 + </​ol>​
 +<br>
 +
 + <​ol>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Which%20cloud%20storage%20services%20are%20supported%20by%20AhsayCBS%20(Cloud%20Backup%20Suite)?">​
 +     Which cloud storage services are supported by AhsayCBS (Cloud Backup Suite)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) Refer to the following KB articles for the list of cloud storage services are supported by AhsayCBS:
 +   <​br/>​
 +   <​br/>​
 +   <a href="​http://​wiki.ahsay.com/​doku.php?​id=public:​8001_faq:​ahsay_software_compatibility_list_scl_for_version_8.1_or_above#​Supported%20Cloud%20Storage%20for%20Cloud%20File%20Backups">​
 +   FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above
 +   </​a>​
 +   <​br>​
 +   <​br>​
 +  </​font></​li>​
 +   <​br/>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​How%20do%20I%20perform%20a%20backup%20to%20a%20local%20destination%20then%20import%20the%20data%20onto%20a%20cloud%20storage%20destination%20(e.g.%20seed%20load)?">​
 +     How do I perform a backup to a local destination then import the data onto a cloud storage destination (e.g. seed load)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) Refer to the following KB articles for detail instruction:​
 +   <​br/>​
 +   <​br/>​
 +   <a href="​http://​wiki.ahsay.com/​doku.php?​id=public:​8021_faq:​how_to_seedload_to_a_cloud_destination">​
 +   FAQ: How to perform backup to a local destination then import the data to a cloud storage destination?​
 +   </​a>​
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +   <​br/>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​How%20do%20I%20start%20AhsayOBM%20in%2032bit%20mode%20(to%20create%20an%20Exchange%20mail%20level%20backup%20set%20or%20to%20start%20a%20mail%20level%20backup%20job)?">​
 +     How do I start AhsayOBM in 32bit mode (to create an Exchange mail level backup set or to start a mail level backup job)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) You can simply start AhsayOBM as you would normally (e.g. double-clicking on the desktop icon or the system tray icon), when creating a MS Exchange mail level backup set or performing a manual MS Exchange mail level backup job.
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​How%20do%20I%20start%20a%20data%20integrity%20check%20for%20backup%20data%20stored%20in%20the%20backup%20destination?">​
 +     How do I start a data integrity check for backup data stored in the backup destination?​
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) A data integrity check can only be started via the client application or via API call. Refer to the following KB article for details:
 +   <​br/>​
 +   <​br/>​
 +   <a href="​http://​wiki.ahsay.com/​doku.php?​id=public:​8004_faq:​how_to_run_a_data_integrity_check">​FAQ:​ How to run a Data Integrity Check for backup data stored in backup destination?</​a>​
 +   <​br>​
 +   <a href="​http://​wiki.ahsay.com/​doku.php?​id=public:​8008_faq:​how_to_run_a_data_integrity_check_on_linux_cli">​FAQ:​ How to run a Data Integrity Check on Linux (CLI) machine?</​a>​
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Backup%20account%20profiles%20are%20stored%20in%20a%20new%20format,​%20can%20you%20explain%20on%20the%20new%20changes?">​
 +     ​Backup account profiles are stored in a new format, can you explain on the new changes?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) For older version of AhsayOBS such as version 6, user profile of each backup account is saved individually within the user home path of each account.
 +   <​br/>​
 +   <​br/>​
 +   <​b>​
 +    <u>
 +     Ahsay Online Backup Suite 6:
 +    </b>
 +   </​u>​
 +   <​br/>​
 +   On the backup server:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\username\db\Profile.xml
 +     <​br>​
 +     <​br>​
 +    </​font></​li>​
 +   </​ul>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_0.png"/> ​
 +   <​br/>​
 +   <​br/>​
 +   On the client computer, the local profile is saved as Profile.sys file within the .obm / .acb config folder at:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​...\.obm\config\Profile.sys
 +     <​br>​
 +     <​br>​
 +    </​font></​li>​
 +   </​ul>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_1.png"/> ​   ​
 +   <​br/>​
 +   <​br/>​
 +   <​b>​
 +    <u>
 +     Ahsay Cloud Backup Suite 8:
 +    </b>
 +   </​u>​
 +   <​br/>​
 +   For AhsayCBS version 8 (started since v7), user profiles of <​u>​all</​u>​ backup accounts are saved in a <​u>​single</​u>​ users.xml file on the backup server at:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%Installhome%\conf\users.xml
 +     <​br>​
 +     <​br>​
 +    </​font></​li>​
 +   </​ul>  ​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_2.png"/>  ​
 +   <​br/>​
 +   <​br/>​
 +   This file contains the settings of <​u>​all</​u>​ backup accounts, as well as settings of <​u>​all</​u>​ backup sets.<​br><​br>​
 +
 +   On the client computer, the local profile is saved as settings.sys file within the .obm / .acb config folder at:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​...\.obm\config\settings.sys
 +     <​br>​
 +     <​br>​
 +    </​font></​li>​
 +   </​ul>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_3.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   This file contain information of the corresponding backup account, backup sets' setting, and most importantly,​ the encryption setting of all backup sets.
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Backup%20data%20are%20stored%20in%20new%20structure,​%20can%20you%20explain%20on%20the%20new%20changes?">​
 +     ​Backup data are stored in new structure, can you explain on the new changes?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) Compared to older version of AhsayCBS such as version 6, the indexing and file structure of backup data are enhanced.
 +   <​br/>​
 +   <​br/>​
 +   <​b>​
 +    <u>
 +     Ahsay Online Backup Suite 6:
 +    </u>
 +   </​b>​
 +   <​br/>​
 +   For older version of Ahsay software, users' settings (username, password, quota), backup sets' settings, as well as backup data are stored in 2 main folders (the '​db'​ and '​files'​ folder) within the backup destination (e.g. user home, local copy destination) of each backup account:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%username%\db
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%username%\files
 +    </​font></​li>​
 +    <br>
 +    <br>
 +    </ul>
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_4.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   User account and its backup sets' info are stored within the '​db'​ folder (as Profile.xml),​ while backup data are stored within the '​files'​ folder in the following format:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%username%\files\%backupset_id%\
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_5.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   ​Backup data are indexed by these 2 files, regardless of the backup data size. The index.bdb file for indexing of data within the current area, and the r-index.bdb file for indexing of data within the retention area:
 +   <​br>​
 +   <​br>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%username%\files\%backupset_id%\index.bdb
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%username%\files\%backupset_id%\r-index.bdb
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_6.png"/>​
 +   <​br>​
 +   <​br>​
 +   ​Disadvantage of such indexing system is that, as all data of each account are indexed with only 2 files, the possibility of multiple processes (e.g. replication,​ rebuild, backup, restore) accessing the same index file increase.
 +   <​br>​
 +   <​br>​
 +   ​Another disadvantage of the previous file structure is that, backup data are stored in a "1 to 1" format, each file is uploaded and saved as individual file within the backup destination in hashed format, regardless of the size of the file:
 +   <​br>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_7.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   This can potentially be a problem for backup set with a huge number of files, as each file is compressed, encrypted, and uploaded individually (even for a tiny file), creating a huge overhead, that slow down a backup significantly.
 +   <​br/>​
 +   <​br/>​
 +   <​b>​
 +    <u>
 +     Ahsay Cloud Backup Suite 8:
 +    </u>
 +   </​b>​
 +   <​br/>​
 +   ​Changes were made to the file structure in an attempt to improve the backup and restore performance.
 +   <​br/>​
 +   <​br/>​
 +   For AhsayCBS version 8 (started since v7), multiple folders reside under the user home:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\db
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\files
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\%backupset_1_id%
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\%backupset_2_id%
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\%backupset_3_id%
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ...
 +    </​font></​li>​
 +   </​ul>​
 +   <​br>​
 + <​img style="​width:​35%;​ border:thin solid black" ​
 +src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_8.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   ​Accounts'​ setting and backup sets' setting are no longer saved within each account'​s user home path (e.g. as '​Profile.xml'​ in previous version). ​ They are now saved in a single location within AhsayOBS'​s installation directory (refer to the previous Q &amp; A for details). ​ Only user logs, backup client logs, backup reports, and other individual account'​s information,​ such as account storage logs are saved within the '​db'​ folder.
 +   <​br/>​
 +   <​br/>​
 +   ​Information on backup sets' type (e.g. file, system state type ... etc.) are saved under the '​files'​ folder within each backup set's respective backup set ID folder, in the '​info.xml'​ file.
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%Userhome%\%username%\files\%backupset_id%\info.xml
 +    </​font></​li>​
 +   </​ul>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_9.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   ​Backup data and encryption settings of a backup set are now stored within the corresponding backup set ID folder:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\settings
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\Snapshots
 +    </​font></​li>​
 +   </​ul>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_10.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   Note:
 +   <​br/>​
 +   ​%backup_destination% can be AhsayOBS server'​s user home, a local storage, or a cloud storage destination.
 +   <​br/>​
 +   <​br/>​
 +   The '​blocks'​ folder contain backed up data of the backup set:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\2
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ...
 +    </​font></​li>​
 +   </​ul>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_11.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   A new 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 will be stored under that particular folder.
 +   <​br/>​
 +   <​br/>​
 +   For changes that occurs on the client computer (e.g. moved files, updated files), files are not moved within the backup destination (e.g. AhsayOBS, local destination,​ cloud service destination) across different directories,​ across the '​Current'​ and '​Retention'​ directories as in the previous file structure. ​ Instead, the index files would be updated to reflect the changes, reducing the I/O operation on the backup destination.
 +   <​br/>​
 +   <​br/>​
 +   ​Backup data are indexed with the following files (compressed):​
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\index.<​font color=#​FF0000>​b2b</​font>​.*.cgz</​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\index.<​font color=#​FF0000>​xml</​font>​.*.cgz</​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\index-<​font color=#​FF0000>​s0</​font>​*.cgz</​font></​li>​
 +   </​ul>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_12.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   ​Where:​
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​index.<​font color=#​FF0000>​b2b</​font>​.*.cgz is the actual index file
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​index.<​font color=#​FF0000>​xml</​font>​.*.cgz is a file containing information of the index file
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​index-<​font color=#​FF0000>​s0</​font>​*.cgz is a temporary file
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +   Data uploaded by the backup client to the backup destination are stored in the following format:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000001.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000002.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000003.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ...
 +     <​br/>​
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000_000001.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​%backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000_000002.bak
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ...
 +    </​font></​li>​
 +   </​ul>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_13.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   When the number of block files within '​0'​ reaches 8192, a new folder is created (folder name increment of 1), restricting the maximum number of files within each folder.
 +   <​br/>​
 +   <​br/>​
 +   ​Regarding the structure of:
 +   <​br/>​
 +   <​br/>​
 +   ​000000.bak
 +   <​br/>​
 +   ​000000_000001.bak
 +   <​br/>​
 +   ​000000_000002.bak
 +   <​br/>​
 +   ​000000_000003.bak
 +   <​br/>​
 +   ...
 +   <​br/>​
 +   ​000001.bak
 +   <​br/>​
 +   ​000002.bak
 +   <​br/>​
 +   ...
 +   <​br/>​
 +   <​br/>​
 +   ​Source files that are <u>16 MB or smaller</​u>​ are '​combined'​ into a single 16 MB '​block'​ file before they are transferred to the backup destination (e.g. AhsayOBS, local destination,​ cloud service destination),​ reducing the overhead during the upload.
 +   <​br/>​
 +   <​br/>​
 +   This also reduces the number of files in the backup destination.
 +   <​br/>​
 +   <​br/>​
 +   ​Source files that are <​u>​larger than</​u>​ 16 MB will be split up into multiple 32 MB '​block'​ files when transferred to the backup destination.
 +   <​br/>​
 +   <​br/>​
 +   For example, a file with size of 100 MB would be split up into 4 '​block'​ files:
 +   <​br/>​
 +   <​br/>​
 +   ​000000.bak - 32 MB
 +   <​br/>​
 +   ​000000_000001.bak - 32 MB
 +   <​br/>​
 +   ​000000_000002.bak - 32 MB
 +   <​br/>​
 +   ​000000_000003.bak - 4 MB
 +   <​br/>​
 +   <​br/>​
 +   Note:
 +   <​br/>​
 +   For AhsayOBM installation on NAS
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     ​Source files that are <u>8 MB or smaller</​u>​ are '​combined'​ into a single 8 MB '​block'​ file when they are transferred to the backup destination
 +     <​br/>​
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​Source files that are <​u>​larger than</​u>​ 8 MB will be split up into multiple 8 MB '​block'​ files when they are transferred to the backup destination
 +    </​font></​li>​
 +   </​ul>​
 +   <​br/>​
 +   An advantage of this design is that, for an upload that was interrupted by temporarily network issue, only the individual '​block'​ file would be re-uploaded (block which failed to upload), instead of the entire file.
 +   <​br/>​
 +   <​br/>​
 +   The '​settings'​ folder contain the encryption settings of the backup set (if the Encryption Recovery option is enabled by the backup user).
 +   <​br>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_14.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   ​While,​ the '​Snapshots'​ folder is there for the replication module.
 +   If replication is enabled, during RESYNC or REPLAY mode, changes to the account will be saved in the '​Snapshots'​ folder, to be replicated.
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Can%20backup%20accounts%20of%20version%206.x%20be%20migrated%20to%20version%208%20or%20above?">​
 +     Can backup accounts of version 6.x be migrated to version 8.1 or above?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) AhsayCBS version 8 support migration of version 6 backup accounts and backup set, version 6 AhsayOBM / AhsayACB clients can still connects to version 8 AhsayCBS for backup (only best effort support).
 +   <​br/>​
 +   <​br/>​
 +   The data structure of existing backed up can be migrated to the file format of AhsayCBS version 8.
 +
 +   <​br>​
 +   <​br>​
 +   <​br>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Which%20version%20of%20Java%20is%20bundled%20with%20AhsayCBS%20(Cloud%20Backup%20Suite)?">​
 +     Which version of Java is bundled with AhsayCBS (Cloud Backup Suite)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) AhsayCBS is bundled with OpenJDK version 1.8_181-13.
 +   <​br/>​
 +      <img style="​width:​75%;​ src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_15.png"/>​
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Cannot%20install%20AhsayACB%20on%20a%20Windows%20server%20operating%20system,​%20why?">​
 +     ​Cannot install AhsayACB on a Windows server operating system, why?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) AhsayACB can only be installed on Windows '​desktop'​ operating system, such as Windows 7, 8, 10 ... etc.
 +   <​br/>​
 +   <​br/>​
 +   The following error message will be displayed when installing AhsayACB on a Windows server operating system, such as Windows Server 2012:
 +   <​br>​
 +   <​br>​
 +      <img style="​width:​35%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_16.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   Note:
 +   <​br/>​
 +   This is a limitation for AhsayACB installation on Windows, you can still AhsayACB on a Mac OS X computer. Refer to the following KB article for the list of supported OS platforms:
 +   <​br/>​
 +   <​br/>​
 +   <a href="​http://​wiki.ahsay.com/​doku.php?​id=public:​8001_faq:​ahsay_software_compatibility_list_scl_for_version_8.1_or_above">​FAQ:​ Ahsay Software Compatibility List (SCL) for version 8.1 or above</​a>​
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Can%20I%20create%20multiple%20backup%20sets%20for%20my%20AhsayACB%20account?">​
 +     Can I create multiple backup sets for my AhsayACB account?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) Yes, you can create multiple backup sets for your AhsayACB account. Further to a file type backup set, you can also create an IBM Lotus Notes backup set and a MS Windows System backup set:
 +   <​br>​
 +   <​br>​
 +      <img style="​width:​65%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_17.png"/>​
 +   <​br>​
 +   <​br>​
 +   <​br>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Retained%20data%20are%20not%20cleared%20according%20to%20the%20retention%20policy%20configured?">​
 +     ​Retained data are not cleared according to the retention policy configured?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) Retained data within the backup destination are not cleared because the retention policy job is not enabled for the backup set.
 +   <​br/>​
 +   <​br/>​
 +   For AhsayOBM / ACB version 8, the retention policy job (job for clearing retained data) is now enabled via the AhsayOBM / ACB client application.
 +   <​br/>​
 +   <​br/>​
 +   You can enable this job via the client user interface with the following steps:
 +   <​br/>​
 +   <​br/>​
 +   For the retention policy job to start after a manual backup job:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     Login to the client user interface, select '​Backup'​.
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​Select the corresponding backup set, then select 'Show advanced options'​.
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     Under Retention Policy, enable the checkbox 'Run Retention Policy after backup'​.
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +      <img style="​width:​65%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_18.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   For the retention policy job to start after a scheduled backup:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     Login to the client user interface, select '​Backup Sets'.
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​Select the corresponding backup set, then select '​Backup Schedule'​.
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​Configure the existing schedule, or create a new backup schedule, enable the checkbox 'Run Retention Policy after backup'​.
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +      <img style="​width:​65%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_19.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   The retention policy job will be performed when the manual or a scheduled backup job is completed.
 +   <​br/>​
 +   <​br/>​
 +   You can also manually start the retention policy job within the client interface:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     Login to the client user interface, select '​Utilities'​.
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     ​Select the corresponding backup set, then select the backup destination location (e.g. OBS, local storage).
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     Click the '​Start'​ button to start the retention policy job.
 +    </​font></​li>​
 +    <br>
 +   </​ul>​
 +      <img style="​width:​65%;​ border:thin solid black" src="​http://​wiki.ahsay.com/​lib/​exe/​fetch.php?​media=public:​5005_20.png"/>​
 +   <​br/>​
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Can%20I%20deploy%20an%20unofficial%20hotfix%20or%20a%20custom%20version%20to%20AhsayOBM%20/​%20ACB%20clients%20using%20the%20Auto%20Update%20Agent%20(AUA)?">​
 +     Can I deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients using the Auto Update Agent (AUA)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) No, it is not possible to deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients with AUA.
 +   <​br/>​
 +   <​br/>​
 +  </​font></​li>​
 +  <br>
 +  <​li><​font color=black>​
 +   <​b>​
 +    <a name="​Can%20I%20modify%20settings%20of%20the%20system%20routine%20jobs%20(e.g.%20enable%20/​%20disable,​%20start%20time,​%20job%20specific%20settings)?">​
 +     Can I modify settings of the system routine jobs (e.g. enable / disable, start time, job specific settings)?
 +    </a>
 +   </​b>​
 +   <​br/>​
 +   <​br/>​
 +   ​Answer) No, it is not possible to modify settings of any system routine jobs. All system routine jobs are performed according to their schedules and cannot be disabled.
 +   <​br/>​
 +   <​br/>​
 +   There are 3 types of system routine jobs:
 +   <​br/>​
 +   <​br/>​
 +   <​ul>​
 +    <​li><​font color=black>​
 +     <​b>​
 +      <​u>​Quarter Hourly Jobs</​u></​b>​ (jobs that are performed at 0, 15, 30, 45 minutes of every hour). These jobs are performed in the following order:
 +     <​br/>​
 +     <​br/>​
 +     <​ul>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Run Backup Check
 +       </​b>​
 +       <​br/>​
 +       ​System job to check on backup set triggered to start.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Low Disk Space
 +       </​b>​
 +       <​br/>​
 +       ​System job sending low disk space reminder to administrator ( when free space on the System Home, User Home, Receivers'​ System Home, Receivers'​ User Home is &lt; 80% )
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Restore Job Report
 +       </​b>​
 +       <​br/>​
 +       ​System job sending restore job report to users with restore job completed in the past 15 minutes.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Storage Logging
 +       </​b>​
 +       <​br/>​
 +       ​System job logging storage usage statistic.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Low Destination Space Reminder
 +       </​b>​
 +       <​br/>​
 +       ​System job for sending low disk space reminder to administrator ( when free space on any predefined destination is &lt; 80% )
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Setting Change Report
 +       </​b>​
 +       <​br/>​
 +       ​System job sending setting change report to user.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Backup Job Report
 +       </​b>​
 +       <​br/>​
 +       ​System job sending backup job report to users with backup job completed in the past 15 minutes.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Inactive User Report
 +       </​b>​
 +       <​br/>​
 +       ​System job for sending inactive user report to administrator.
 +      </​font></​li>​
 +     </​ul>​
 +     <​br/>​
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     <​b><​u>​Hourly Jobs</​u></​b>​ (jobs that are performed every hour). These jobs are performed in the following order:
 +     <​br/>​
 +     <​br/>​
 +     <​ul>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Backup Job Reminder Report
 +       </​b>​
 +       <​br/>​
 +       ​System job sending missed backup job reminder to user.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        RDR License Check
 +       </​b>​
 +       <​br/>​
 +       ​System job performing license check (for the redirector module).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        License Expiry Check
 +       </​b>​
 +       <​br/>​
 +       ​System job performing license expiration check.
 +      </​font></​li>​
 +     </​ul>​
 +     <​br/>​
 +    </​font></​li>​
 +    <​li><​font color=black>​
 +     <​b><​u>​Daily Jobs</​u></​b>​ (jobs that are performed daily). These jobs are performed at 06:00 daily in the following order:
 +     <​br/>​
 +     <​br/>​
 +     <​ul>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Upload User Usage
 +       </​b>​
 +       <​br/>​
 +       ​System job sending account usage of the backup server to the license server.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        RDR Upload User Usage
 +       </​b>​
 +       <​br/>​
 +       ​System job sending account usage to the license server (for the redirector module).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        RDR Monthly License Usage
 +       </​b>​
 +       <​br/>​
 +       ​System job sending monthly meter license usage to the license server (for the redirector module).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Monthly License Usage
 +       </​b>​
 +       <​br/>​
 +       ​System job sending monthly meter license usage to the license server.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Auto Save
 +       </​b>​
 +       <​br/>​
 +       ​System job sending server'​s configuration settings and user profiles to Ahsay.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        System Log Removal
 +       </​b>​
 +       <​br/>​
 +       ​System job removing obsoleted system log ( logs &gt; 365 days ).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Remove Trial User
 +       </​b>​
 +       <​br/>​
 +       ​System job removing expired trial users.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Disable Trial User
 +       </​b>​
 +       <​br/>​
 +       ​System job suspending expired trial users.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        RPS Retention Policy
 +       </​b>​
 +       <​br/>​
 +       ​System job removing obsolete files from the retention area based on the retention policy setting (for the replication module).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        RPS CRC Check
 +       </​b>​
 +       <​br/>​
 +       ​System job performing Cyclic Redundancy Check (CRC) of replicated files.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Retention Policy
 +       </​b>​
 +       <​br/>​
 +       ​System job removing obsolete files from the retention area for all users based on each backup sets' retention policy setting.
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Backup Quota Reminder Report
 +       </​b>​
 +       <​br/>​
 +       ​System job sending quota reminder to user close to exceeding quota limit ( when free quota is &lt; 20% ).
 +       <​br/>​
 +       <​br/>​
 +      </​font></​li>​
 +      <​li><​font color=black>​
 +       <​b>​
 +        Trial User Reminder
 +       </​b>​
 +       <​br/>​
 +       ​System job sending reminder to trial user with trial period about to be expired ( when trial period expired in &lt; 7 days ).
 +      </​font></​li>​
 +     </​ul>​
 +    </​font></​li>​
 +   </​ul>​
 +  </​font></​li>​
 + </​ol>​
 +</​html>​
 +
 +===== Keywords =====
 +CBS, java, retention, import, seedload, structure, profile, version, 7, index
public/8020_faq/faq_about_ahsay_cloud_backup_suite_8.txt · Last modified: 2019/01/31 14:59 by edward.chan