User Tools

Site Tools


public:microsoft_exchange_server_database

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:microsoft_exchange_server_database [2019/08/15 18:28]
ronnie.chan [Best Practices and Recommendations]
public:microsoft_exchange_server_database [2019/08/26 11:55] (current)
ronnie.chan
Line 11: Line 11:
   - AhsayOBM must be installed on the Exchange server with mailbox role. \\ \\    - AhsayOBM must be installed on the Exchange server with mailbox role. \\ \\ 
   - Make sure the Exchange Server has been updated to the latest roll-up patch of that specific service pack. \\ \\  ​   - Make sure the Exchange Server has been updated to the latest roll-up patch of that specific service pack. \\ \\  ​
-  - Make sure that circular logging is disabled for all Information Store(s) or Public Folder selected for backup.\\ {{public:​ahsay_wiki_module_exchange_database_02.png}} ​\\ \\  +  - Make sure that circular logging is disabled for all Information Store(s) or Public Folder selected for backup.\\ \\  
-  - Make sure that the Microsoft Exchange Server add-on module has been enabled for your AhsayOBM user account. ​Contact your backup service provider for more details.\\ \\ +  - Make sure that the Microsoft Exchange Server add-on module has been enabled for your AhsayOBM user account.\\ {{public:​ahsay_wiki_module_exchange_database_02.png}}  ​\\ \\ 
   - The Exchange Server 2010/​2013/​2016 database files are no longer stored in the temporary directory during backup. However, the VSS-based Exchange backup will still require certain amount of disk space to operate. Microsoft suggested that certain shadow copy mechanism may require free space around 100% of the original database. Refer to the following URL for more information. ​ https://​docs.microsoft.com/​en-us/​exchange/​client-developer/​exchange-server-development \\ \\    - The Exchange Server 2010/​2013/​2016 database files are no longer stored in the temporary directory during backup. However, the VSS-based Exchange backup will still require certain amount of disk space to operate. Microsoft suggested that certain shadow copy mechanism may require free space around 100% of the original database. Refer to the following URL for more information. ​ https://​docs.microsoft.com/​en-us/​exchange/​client-developer/​exchange-server-development \\ \\ 
   - Temporary Directory folder is used by AhsayOBM for storing backup set index files and any incremental or differential delta files generated during a backup job. To ensure optimal backup/​restore performance,​ it is recommended that the folder is located on a local drive with plenty of free disk space.\\ \\    - Temporary Directory folder is used by AhsayOBM for storing backup set index files and any incremental or differential delta files generated during a backup job. To ensure optimal backup/​restore performance,​ it is recommended that the folder is located on a local drive with plenty of free disk space.\\ \\ 
Line 90: Line 90:
    ​State:​ [1] Stable    ​State:​ [1] Stable
    Last error: No error </​code>​    Last error: No error </​code>​
 +  - For Exchange server with Active Directory installed, a Windows System State backup must be performed regularly with the MS Exchange Server backup.\\ \\
 +  - (Applicable to Microsoft Exchange Server 2013/2016 only) \\ \\ If you are using Microsoft Exchange Server 2013/2016 on Windows Server 2012, please install .Net Framework 3.5 Features under Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page. \\  {{public:​ahsay_wiki_module_exchange_database_03.png?​800}} \\ \\ 
 +
 +===== Best Practices and Recommendations for Exchange Server in Data Availability Group (DAG) only =====
 +
 +  - System State backup must be performed regularly for the domain controller of the Exchange DAG setup. \\ \\
 +  - Scheduled backup is required if you choose to back up with DAG option, as AhsayOBM on all DAG members will base on the scheduled backup time to start backups on individual DAG member at the same time.  \\ \\ A DAG backup cycle is considered complete only when scheduled backup on all DAG members have been carried out. An email report will be generated when a complete DAG backup cycle has taken place. \\ \\ Please keep in mind that manual backup will only be considered as individual mail-level backup, and therefore will not be counted as part of the DAG backup cycle.
 +  - The MS Exchange Server Backup module will protect the Exchange server at the database level. If a full system backup (for bare-metal recovery) is required, please consider setting up a MS System Backup for each DAG member server. ​
 +  - To back up mailbox database within an Exchange DAG, AhsayOBM is required to be installed on each DAG member with mailbox role (e.g. servers that are hosting the mailbox databases). It is not necessary to install AhsayOBM on Exchange server with CAS (Client Access Server) role only.
 +
 +===== Overview of Backup Process =====
 +
 +{{public:​ahsay_wiki_module_exchange_database_04.png}}
  
 ===== Documentation ===== ===== Documentation =====
  
-  * [[https://​www.ahsay.com/​download/​download_document_v8_obm-user-guide-exchange-db.jsp|Microsoft Exchange Server Database Backup and Restore Guide]]+  * [[https://​www.ahsay.com/​download/​download_document_v8_obm-user-guide-exchange-db.jsp|Microsoft Exchange Server Database Backup and Restore Guide]] ​
  
 ===== Issues ===== ===== Issues =====
Line 103: Line 116:
   * [[public:​5119_issue:​invalid_backup_source_displayed_for_exchange_2007_server_backup_set_upgraded_from_version_6_to_7|Invalid backup source displayed for Exchange 2007 server backup set upgraded from version 6 to 7]]   * [[public:​5119_issue:​invalid_backup_source_displayed_for_exchange_2007_server_backup_set_upgraded_from_version_6_to_7|Invalid backup source displayed for Exchange 2007 server backup set upgraded from version 6 to 7]]
   * [[public:​5120_issue:​migratev6index.migrateindex_failed_to_migrate_v6_index_ms_exchange_dag_server_backup_set_upgraded_from_version_6_to_7|[MigrateV6Index.migrateIndex] Failed to migrate v6 index (MS Exchange DAG server backup set upgraded from version 6 to 7)]]   * [[public:​5120_issue:​migratev6index.migrateindex_failed_to_migrate_v6_index_ms_exchange_dag_server_backup_set_upgraded_from_version_6_to_7|[MigrateV6Index.migrateIndex] Failed to migrate v6 index (MS Exchange DAG server backup set upgraded from version 6 to 7)]]
-  * [[public:​5121_issue:​migratev6index.migratemultihostindices_failed_to_deserialize_v6_index_ms_exchange_dag_mail_level_backup_set_upgraded_from_version_6_to_7|[MigrateV6Index.migrateMultiHostIndices] Failed to deserialize v6 index (MS Exchange DAG mail level backup set upgraded from version 6 to 7)]]+  * [[public:​5121_issue:​migratev6index.migratemultihostindices_failed_to_deserialize_v6_index_ms_exchange_dag_mail_level_backup_set_upgraded_from_version_6_to_7|[MigrateV6Index.migrateMultiHostIndices] Failed to deserialize v6 index (MS Exchange DAG mail level backup set upgraded from version 6 to 7)]] 
public/microsoft_exchange_server_database.1565864896.txt.gz · Last modified: 2019/08/15 18:28 by ronnie.chan