User Tools

Site Tools


public:5005_faq:frequently_asked_questions_about_ahsay_cloud_backup_suite_7

FAQ: Frequently Asked Questions about Ahsay Cloud Backup Suite 7

Article ID: 5005
Reviewed: 07/01/2016

Product Version:
Ahsay Software: Post-7.3
OS: All platforms

Description

The following are some Frequently Asked Questions on Ahsay Cloud Backup Suite.

Table of Contents:

  1. Which cloud storage services are supported by AhsayCBS (Cloud Backup Suite)?
  2. How do I perform a backup to a local destination then import the data onto a cloud storage destination (e.g. seed load)?
  3. How do I start AhsayOBM in 32bit mode (to create an Exchange mail level backup set or to start a mail level backup job)?
  4. How do I start a data integrity check for backup data stored in the backup destination?
  5. Backup account profiles are stored in a new format, can you explain on the new changes?
  6. Backup data are stored in new structure, can you explain on the new changes?
  7. Can backup accounts of version 6.x be migrated to version 7.3 or above?
  8. Which version of Java is bundled with AhsayCBS (Cloud Backup Suite)?
  9. Cannot install AhsayACB on a Windows server operating system, why?
  10. Can I create multiple backup sets for my AhsayACB account?
  11. Retained data are not cleared according to the retention policy configured?
  12. Can I deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients using the Auto Update Agent (AUA)?
  13. Can I modify settings of the system routine jobs (e.g. enable / disable, start time, job specific settings)?

  1. Which cloud storage services are supported by AhsayCBS (Cloud Backup Suite)?

    Answer) Refer to the following KB articles for the list of cloud storage services are supported by AhsayCBS:

    FAQ: Ahsay Software Compatibility List (SCL) for version 7.3 or above (5001)


  2. How do I perform a backup to a local destination then import the data onto a cloud storage destination (e.g. seed load)?

    Answer) Refer to the following KB articles for detail instruction:

    FAQ: How to perform backup to a local destination then import the data to a cloud storage destination? (5007)


  3. How do I start AhsayOBM in 32bit mode (to create an Exchange mail level backup set or to start a mail level backup job)?

    Answer) Starting from AhsayOBM version 7.3, 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.


  4. How do I start a data integrity check for backup data stored in the backup destination?

    Answer) Starting from AhsayCBS (Cloud Backup Suite) version 7.3, a data integrity check can only be started via the client application or via API call. Refer to the following KB article for details:

    FAQ: How to perform a data integrity check for backup data stored in the backup destination? (5004)

    To start a data integrity check for legacy backup set created in version 6 or for client without GUI (e.g. to start the check via API), refer to the following KB article for details:

    FAQ: How to run a Cyclic Redundancy Check (CRC) for legacy backup set created in version 6 (or for client without GUI)? (5055)


  5. Backup account profiles are stored in a new format, can you explain on the new changes?

    Answer) In previous versions of AhsayOBS, user profile of each backup account is saved individually within the user home path of each account.

    Ahsay Online Backup Suite 6:
    On the backup server:

    • %Userhome%\username\db\Profile.xml


    On the client computer, the local profile is saved as Profile.sys file within the .obm / .acb config folder at:

    • ...\.obm\config\Profile.sys


    Ahsay Cloud Backup Suite 7:
    Starting from AhsayOBS version 7.3, unlike previous versions where each account's profile is saved individually as separate file, user profiles of all backup accounts are saved in a single users.xml file on the backup server at:

    • %Installhome%\conf\users.xml


    This file contains the settings of all backup accounts, as well as settings of all backup sets.

    On the client computer, the local profile is saved as settings.sys file within the .obm / .acb config folder at:

    • ...\.obm\config\settings.sys


    This file contain information of the corresponding backup account, backup sets' setting, and most importantly, the encryption setting of all backup sets.


  6. Backup data are stored in new structure, can you explain on the new changes?

    Answer) The indexing and file structure of backup data was redesigned for AhsayCBS (Cloud Backup Suite) version 7.

    Ahsay Online Backup Suite 6:
    In previous versions 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:

    • %backup_destination%\%username%\db
    • %backup_destination%\%username%\files


    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:

    • %backup_destination%\%username%\files\%backupset_id%\


    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:

    • %backup_destination%\%username%\files\%backupset_id%\index.bdb
    • %backup_destination%\%username%\files\%backupset_id%\r-index.bdb


    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.

    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:


    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.

    Ahsay Cloud Backup Suite 7:
    Changes were made to the file structure in an attempt to improve the backup and restore performance.

    In version 7, multiple folders reside under the user home:

    • %Userhome%\%username%\db
    • %Userhome%\%username%\files
    • %Userhome%\%username%\%backupset_1_id%
    • %Userhome%\%username%\%backupset_2_id%
    • %Userhome%\%username%\%backupset_3_id%
    • ...


    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 & 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.

    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.

    • %Userhome%\%username%\files\%backupset_id%\info.xml


    Backup data and encryption settings of a backup set are now stored within the corresponding backup set ID folder:

    • %backup_destination%\%backupset_id%\blocks
    • %backup_destination%\%backupset_id%\settings
    • %backup_destination%\%backupset_id%\Snapshots


    Note:
    %backup_destination% can be AhsayOBS server's user home, a local storage, or a cloud storage destination.

    The 'blocks' folder contain backed up data of the backup set:

    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\2
    • ...


    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.

    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.

    Backup data are indexed with the following files (compressed):

    • %backup_destination%\%backupset_id%\blocks\index. b2b .*.cgz
    • %backup_destination%\%backupset_id%\blocks\index. xml .*.cgz
    • %backup_destination%\%backupset_id%\blocks\index- s0 *.cgz


    Where:

    • index. b2b .*.cgz is the actual index file
    • index. xml .*.cgz is a file containing information of the index file
    • index- s0 *.cgz is a temporary file

    Data uploaded by the backup client to the backup destination are stored in the following format:

    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000.bak
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000001.bak
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000002.bak
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\0\000000_000003.bak
    • ...
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000.bak
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000_000001.bak
    • %backup_destination%\%backupset_id%\blocks\YYYY-MM-DD-hh-mm-ss\1\010000_000002.bak
    • ...


    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.

    Regarding the structure of:

    000000.bak
    000000_000001.bak
    000000_000002.bak
    000000_000003.bak
    ...
    000001.bak
    000002.bak
    ...

    Source files that are 16 MB or smaller 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.

    This also reduces the number of files in the backup destination.

    Source files that are larger than 16 MB will be split up into multiple 32 MB 'block' files when transferred to the backup destination.

    For example, a file with size of 100 MB would be split up into 4 'block' files:

    000000.bak - 32 MB
    000000_000001.bak - 32 MB
    000000_000002.bak - 32 MB
    000000_000003.bak - 4 MB

    Note:
    For AhsayOBM installation on NAS (a new feature of version 7)

    • Source files that are 8 MB or smaller are 'combined' into a single 8 MB 'block' file when they are transferred to the backup destination
    • Source files that are larger than 8 MB will be split up into multiple 8 MB 'block' files when they are transferred to the backup destination

    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.

    The 'settings' folder contain the encryption settings of the backup set (if the Encryption Recovery option is enabled by the backup user).


    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.


  7. Can backup accounts of version 6.x be migrated to version 7.3 or above?

    Answer) AhsayCBS version 7.5.0.0 or above, fully support the migration of v6 backup accounts and backup set is fully supported as well as v6 AhsayOBM / AhsayACB clients.

    The data structure of existing backed up data will remain the same (for AhsayCBS version 7.5), or the data structure can be migrated to the new format (for AhsayCBS version 7.7 or above).

    Note:
    AhsayCBS version 7.3.2.0 does not support v6 AhsayOBM / AhsayACB clients.

  8. Which version of Java is bundled with AhsayCBS (Cloud Backup Suite)?

    Answer) AhsayCBS is bundled with Java version 1.7 update 76.


  9. Cannot install AhsayACB on a Windows server operating system, why?

    Answer) Starting from version 7.3.2.0, AhsayACB can only be installed on Windows 'desktop' operating system, such as Windows 7, 8 or 8.1 ... etc.

    The following error message will be displayed when installing AhsayACB on a Windows server operating system, such as Windows Server 2012:


    Note:
    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:

    FAQ: Ahsay Software Compatibility List (SCL) for version 7.3 or above (5001)


  10. Can I create multiple backup sets for my AhsayACB account?

    Answer) Starting from version 7.3.2.0, 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:


  11. Retained data are not cleared according to the retention policy configured?

    Answer) The retained data within the backup destination may not be cleared because the retention policy job is not enabled for the backup set.

    Starting from version 7.3.2.0, the retention policy job (job for clearing retained data) is now enabled via the AhsayOBM / ACB client application.

    You can enable this job via the client user interface with the following steps:

    For the retention policy job to start after a manual backup job:

    • Login to the client user interface, select 'Backup'.
    • Select the corresponding backup set, then select 'Show advanced options'.
    • Under Retention Policy, enable the checkbox 'Run Retention Policy after backup'.


    For the retention policy job to start after a scheduled backup:

    • Login to the client user interface, select 'Backup Sets'.
    • Select the corresponding backup set, then select 'Backup Schedule'.
    • Configure the existing schedule, or create a new backup schedule, enable the checkbox 'Run Retention Policy after backup'.


    The retention policy job will be performed when the manual or a scheduled backup job is completed.

    You can also manually start the retention policy job within the client interface:

    • Login to the client user interface, select 'Utilities'.
    • Select the corresponding backup set, then select the backup destination location (e.g. OBS, local storage).
    • Click the 'Start' button to start the retention policy job.



  12. Can I deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients using the Auto Update Agent (AUA)?

    Answer) No, it is not possible to deploy an unofficial hotfix or a custom version to AhsayOBM / ACB clients with AUA.


  13. Can I modify settings of the system routine jobs (e.g. enable / disable, start time, job specific settings)?

    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.

    There are 3 types of system routine jobs:

    • Quarter Hourly Jobs (jobs that are performed at 0, 15, 30, 45 minutes of every hour). These jobs are performed in the following order:

      • Run Backup Check
        System job to check on backup set triggered to start.

      • Low Disk Space
        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 < 80% )

      • Restore Job Report
        System job sending restore job report to users with restore job completed in the past 15 minutes.

      • Storage Logging
        System job logging storage usage statistic.

      • Low Destination Space Reminder
        System job for sending low disk space reminder to administrator ( when free space on any predefined destination is < 80% )

      • Setting Change Report
        System job sending setting change report to user.

      • Backup Job Report
        System job sending backup job report to users with backup job completed in the past 15 minutes.

      • Inactive User Report
        System job for sending inactive user report to administrator.

    • Hourly Jobs (jobs that are performed every hour). These jobs are performed in the following order:

      • Backup Job Reminder Report
        System job sending missed backup job reminder to user.

      • RDR License Check
        System job performing license check (for the redirector module).

      • License Expiry Check
        System job performing license expiration check.

    • Daily Jobs (jobs that are performed daily). These jobs are performed at 06:00 daily in the following order:

      • Upload User Usage
        System job sending account usage of the backup server to the license server.

      • RDR Upload User Usage
        System job sending account usage to the license server (for the redirector module).

      • RDR Monthly License Usage
        System job sending monthly meter license usage to the license server (for the redirector module).

      • Monthly License Usage
        System job sending monthly meter license usage to the license server.

      • Auto Save
        System job sending server's configuration settings and user profiles to Ahsay.

      • System Log Removal
        System job removing obsoleted system log ( logs > 365 days ).

      • Remove Trial User
        System job removing expired trial users.

      • Disable Trial User
        System job suspending expired trial users.

      • RPS Retention Policy
        System job removing obsolete files from the retention area based on the retention policy setting (for the replication module).

      • RPS CRC Check
        System job performing Cyclic Redundancy Check (CRC) of replicated files.

      • Retention Policy
        System job removing obsolete files from the retention area for all users based on each backup sets' retention policy setting.

      • Backup Quota Reminder Report
        System job sending quota reminder to user close to exceeding quota limit ( when free quota is < 20% ).

      • Trial User Reminder
        System job sending reminder to trial user with trial period about to be expired ( when trial period expired in < 7 days ).

Keywords

CBS, java, retention, import, seedload, structure, profile, version, 7, index

public/5005_faq/frequently_asked_questions_about_ahsay_cloud_backup_suite_7.txt · Last modified: 2018/06/28 12:00 by edward.chan