合作伙伴请登入

Partner Portal

最新 AhsayCBS v
发布于:

V6 和 V7 之间的差异

Last modified date: Dec 7, 2015

AhsayCBS

AhsayCBS AhsayOBM 和 AhsayACB 备份和还原复制模块重定向模块

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
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)
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 backpu 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 (e.g. Full database backup with Differential In-file Delta) Incremental (e.g. Full database backup with Incremental In-file Delta) Note: The In-file Delta setting cannot be configured for MS SQL Server backup set. Transaction Log backup (if enabled in the backup schedule) will automatically be converted to an Incremental backup type after upgrading to version 7. 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. 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.
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. Hyper-V Cluster Setup for Windows 2008 R2, 2012, 2012 R2 are supported.
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.
Oracle Database Server Backup		The backup process for Oracle Database Server is the same as version 6. 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: How to instantly startup a VMware virtual machine with the Run Direct feature (with migration)? How to instantly startup a VMware virtual machine with the Run Direct feature (without migration)? 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.