Backup Sets (Backup and Restore Operation) |
Version 6 |
Same in v7? |
Comments / Changes on v7 |
File Backup |
|
- File backup set can be created in the client UI at Backup Sets > Add
- File backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- Newly introduced in version 7.13. OpenDirect - Support the restore of individual files/folders within a compressed/image file without the need to restore the whole compressed/image file first. For AhsayOBM/AhsayACB File backup sets on Windows operating system.
.
|
Cloud File Backup |
|
- Newly introduced in version 7.9. The Cloud File Backup feature allows user to backup data stored on cloud storage to AhsayCBS or to another cloud storage destination.
- There are 2 types of Cloud File backup sets available:
- Run on Server Cloud File Backup (an agentless backup set, backup and restore are performed on the AhsayCBS admin / user console)
- Run on Client Cloud File Backup (an agent-based backup set, backup and restore are performed in the client UI)
- Run on Server Cloud File backup set can be created in the AhsayCBS admin / user web console at Backup / Restore > Users, Groups, Policies / Users > Backup Set
- Run on Server Cloud File backup set can be restored in the AhsayCBS admin / user web console at Backup / Restore > Users, Groups, Policies > Backup Set > Execute Job (Restore) or Backup / Restore > User > Backup Set > Execute Job (Restore)
- There are 2 restore destination that the user can select for a Run on Server Cloud File backup set:
- Original Location (e.g. to the same directory path on the original cloud storage)
- Alternate Location (e.g. to a different directory path on the original cloud storage)
- Run on Client Cloud File backup set can be created in the client UI at Backup Sets > Add
- Run on Client Cloud File backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 3 restore destination that the user can select for a Run on Client Cloud File backup set:
- Local Computer (e.g. to the local computer where AhsayOBM is installed)
- Original Location (e.g. to the same directory path on the original cloud storage)
- Alternate Location (e.g. to a different directory path on the original cloud storage)
|
IBM Lotus Domino Backup |
|
- The backup process for Lotus Domino and Notes is the same as version 6.
- Lotus Domino / Notes backup set can be created in the client UI at Backup Sets > Add
- The restore process is enhanced in version 7, Domino database can now be restored and mounted automatically by AhsayOBM.
- Lotus Domino / Notes backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can select:
- Original Location (e.g. to the original Domino server)
- Alternate Location (e.g. to another Domino server)
- The database selected for restore are restored automatically to the corresponding Domino server without the need to manually mount the restored database files (as in version 6). The entire restoration (restoration of the file, mounting of the database) is performed via the AhsayOBM UI.
- The user can also select to restore the raw database files if required.
|
MS Exchange Server Backup |
|
- The backup process for Exchange Server has been enhanced in version 7.
- Backup is performed using Volume Shadow Copy (even for Exchange 2007 Server), no staging of the database file is required during the backup process. MS Exchange 2003 is de-supported by AhsayOBM version 7.
- Exchange Server backup set can be created in the client UI at Backup Sets > Add
- The restore process for Exchange Server has also been enhanced in version 7. Exchange database can now be restored and mounted automatically by AhsayOBM (even for Exchange 2007 Server).
- Exchange Server backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can choose:
- Original Location (e.g. to the original Exchange server)
- Alternate Location (e.g. to another Exchange server)
- The database selected for restore are restored automatically to the corresponding Exchange server without the need to manually mount the restored database files (as in version 6 for Exchange 2007). The entire restoration (restoration of the file, mounting of the database) is performed via the AhsayOBM UI.
- The user can also select to restore the raw database files if required.
|
MS Exchange Mail Level Backup |
|
- Same as version 6, except administrator do not have to start AhsayOBM in x86 mode for x64 Exchange server when configuring the mail level backup set.
- Exchange Mail Level backup set can be created in the client UI at Backup Sets > Add
- Note that, MS Exchange 2003 has been de-supported by version 7.
- Exchange Mail Level backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can choose:
- Original Location (e.g. to the original Exchange server)
- Alternate Location (e.g. to another Exchange server)
- Newly introduced in version 7.15. Support MS Exchange 2016 mail level backup and restore.
- Index file enhancement for newly created MS Exchange 2016 mail level backup sets (one set of index files per mailbox).
|
MS SQL Server Backup |
|
- The backup process for SQL Server has been enhanced in version 7.
- AhsayOBM utilizes Volume Shadow Copy (VSS) for MS SQL backup in version 7, no staging of the database file is required during the backup process.
- SQL Server backup set can be created in the client UI at Backup Sets > Add
- The 3 backup types of a SQL backup in version 6 - "Database - Complete", "Database - Differential" and "Transactional Log", they are migrated as the following backup type in version 7 respectively:
- Full
- Differential
- Incremental
Important Note: Since the backup methodology is entirely different in verison 7, a Full database backup must be performed after upgrading AhsayOBM to version 7.
- Newly introduced in version 7.7. The option to configure In-file Delta setting, which was removed from AhsayOBM version 7.3 to 7.5, is re-introduced in version 7.7.
- The restore process has also been enhanced, SQL database can be restored automatically via AhsayOBM without having to manually mount the restored database.
- SQL Server backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can choose:
- Original Location (e.g. to the original SQL server)
- Alternate Location (e.g. to another SQL server)
- The user can also select to restore the raw virtual disk files if required.
- Newly introduced in version 7.11. Support of transaction log backup using ODBC method. Two backup methods are available for MS SQL Server VSS and ODBC:
- MS SQL Server backup sets upgraded from v6 will continue to use the ODBC method. After AhsayOBM upgrade to v7.11 the first backup job will default to a full database backup as part of the index and backup set migration process.
- Newly created backup sets can selected either VSS or ODBC backup method.
- Existing backup sets created in v7 using VSS cannot be converted to ODBC method. A new backup set must to be created.
- Both database and transaction log backups performed using the ODBC method will require addition free disk space on the temporary directory to accomodate the spooling of the database files.
Important Note: Recommended free space on the temporary folder should be 150% of the total database size for one backup destination (based on default Delta ratio setting of 50%), 200% of the database size for two backup destinations, 250% of the database size for three backup destinations etc.
|
MS Windows System Backup |
|
- The backup process for MS Windows System is the same as version 6.
- MS Windows System backup set can be created in the client UI at Backup Sets > Add
- The restore process for MS Windows System backup set is the same as version 6.
- MS Windows System backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
|
MS Windows System State Backup |
|
- The backup process for MS Windows System State is the same as version 6.
- MS Windows System State backup set can be created in the client UI at Backup Sets > Add
- The restore process for MS Windows System State backup set is the same as version 6.
- MS Windows System State backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
|
MS Hyper-V Backup |
|
- The backup process for MS Hyper-V backup has been enhanced in version 7.
- MS Hyper-V backup set can be created in the client UI at Backup Sets > Add
- Newly introduced in version 7. The "Run Direct" feature will allow users to backup their virtual machines to a backup destination (accessible to the hypervisor), for instant recovery / startup of their virtual machines.
- The restore process has also been enhanced, backed up virtual machine can be instantly restored / startup with the "Run Direct" feature (if enabled).
- MS Hyper-V backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can choose:
- Original Location (e.g. to the original Hyper-V server)
- Alternate Location (e.g. to another Hyper-V server)
- User can also select to restore the raw virtual disk files if required.
- Newly introduced in version 7.9. Ahsay Hyper-V Changed Block Tracking technology is introduced to improve Hyper-V's backup performance and efficiency by speeding up delta generation in incremental backups, making the backups much smaller and faster.
Note: The Change Block Tracking technology can only be used for backup set with backup destination set to a Local / Network / Removable storage. Refer to the Microsoft Hyper-V User Guide for details.
- Hyper-V Cluster Setup for Windows 2008 R2, 2012, 2012 R2, and 2016 are supported.
- Newly introduced in version 7.11. Support restore of Hyper-V guest virtual machines to another Hyper-V host (must be on the same Hyper-V version) for both Run Direct and Non-Run Direct backups.
- Newly introduced in version 7.11. Granular Restore - Support the restore of individual files/folders within a Hyper-V guest virtual machines running on Windows Operating System, without the need to boot up or restore the whole guest virtual machines first.
- Newly introduced in version 7.15. CBT Cluster Services supports all backup destinations on Hyper-V 2008 R2, 2012, and 2012 R2. Hyper-V 2016 RCT (Resilient Change Tracking) supports all backup destinations.
|
MySQL Backup |
|
- The backup process for MySQL is the same as version 6.
- MySQL backup set can be created in the client UI at Backup Sets > Add
- The restore process is enhanced in version 7, MySQL database can now be restored and mounted automatically by AhsayOBM.
- MySQL backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can select:
- Original Location (e.g. to the original MySQL server)
- Alternate Location (e.g. to another MySQL server)
- The database selected for restore are restored automatically to the corresponding MySQL server without the need to manually mount the restored database files (as in version 6). The entire restoration (restoration of the file, mounting of the database) is performed via the AhsayOBM UI.
- User can also select to restore the raw database files if required.
|
Office 365 Exchange Online Backup |
|
- Newly introduced in version 7.9. The Office 365 Exchange Online Backup feature allows user to backup Office 365 Exchange Online mailbox accounts (e.g. email, contact, calendar, etc.) for AhsayOBM.
- Office 365 Exchange Online backup set can be created in the client UI at Backup Sets > Add
- Office 365 Exchange Online backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can select for a Office 365 Exchange Online backup set:
- Original Location (e.g. to the original mailbox)
- Alternate Location (e.g. to a different mailbox within the same Office 365 setup)
- Newly introduced in version 7.11. Backup and restore of Office 365 mailboxes for AhsayACB users.
- Limited to two mailboxes, one personal mailbox per backup set.
- Mail items can only be restored to the original mailbox.
- Support agentless backup and restore from AhsayCBS.
- Newly introduced in version 7.15. Support backup and restore of Public folders.
- Index file enhancement for newly created backup sets (one set of index files per mailbox). Existing backup sets upgraded to v7.15 or above will undergo index migration to new index structure on the next backup job.
|
Oracle Database Server Backup |
|
- The backup process for Oracle Database Server has been enhanced since version 7.5.
- AhsayOBM utilizes Volume Shadow Copy (VSS) for Oracle database backup in version 7, no staging of the database file is required during the backup process.
- Oracle Database Server backup set can be created in the client UI at Backup Sets > Add
- The restore process is enhanced in version 7, Oracle database can now be restored and mounted automatically by AhsayOBM. Instruction can be found in the following KB article: How to restore and recover an Oracle database instance automatically?
- Oracle Database Server backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can select:
- Original Location (e.g. to the original Oracle server)
- Alternate Location (e.g. to another Oracle server)
- The database selected for restore are restored automatically to the corresponding Oracle server without the need to manually mount the restored database files (as in version 6). The entire restoration (restoration of the file, mounting of the database) is performed via the AhsayOBM UI.
- User can also select to restore the raw database files if required.
|
Shadow Protect Backup |
|
- The backup process for Shadow Protect has been enhanced, user can now encrypt the image file that is output to the temporary directory configured.
- Shadow Protect backup set can be created in the client UI at Backup Sets > Add
- The restore process is the same as version 6.
- Shadow Protect backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
|
VMware Backup |
|
- The backup process for VMware backup has been enhanced in version 7.
- VMware backup set can be created in the client UI at Backup Sets > Add
- Newly introduced in version 7, the "Run Direct" feature will allow users to backup their virtual machines to a backup destination (accessible to the hypervisor), for instant recovery / startup of their virtual machines. Instruction can be found in the following KB article: How to create a VMware backup set to be used with the Run Direct feature?
- The restore process has also been enhanced, backed up virtual machine can be instantly restored / startup with the "Run Direct" feature (if enabled). Instruction can be found in the following KB article:
- Newly introduced in version 7.9. The Run Direct feature is enhanced, allowing user to perform a Run Direct restore on the AhsayCBS user web console at Backup / Restore > Run Direct
- VMware backup set can be restored in the client UI at Restore > Select the corresponding backup set > Destination to Restore from > Restore files to
- There are 2 restore destination that the user can choose:
- Original Location (e.g. to the original VMware hypervisor)
- Alternate Location (e.g. to another VMware hypervisor)
- User can also select to restore the raw virtual disk files if required.
- Newly introduced in version 7.11. Support restore of VDDK backups to VMDK format using "Raw file" option. "Raw file" restore from VDDK to VMDK format is only supported for VDDK backup sets created on AhsayOBM v7.9.0.0 or above.
- Newly introduced in version 7.13. Granular Restore - Support the restore of individual files/folders within a VMware ESXi/vCenter guest virtual machines running on Windows Operating System, without the need to boot up or restore the whole guest virtual machines first.
|