public:microsoft_exchange_server_database
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
public:microsoft_exchange_server_database [2017/09/30 14:37] felix.chou |
public:microsoft_exchange_server_database [2019/08/15 18:26] ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Microsoft Exchange Server Database Backup Set====== | ||
| + | AhsayOBM comes with the MS Exchange Server Backup module for backing up Microsoft Exchange Server's full database. | ||
| + | {{public:ahsay_wiki_exchange_database_backup_set.png?640}} | ||
| + | |||
| + | ===== Best Practices and Recommendations ===== | ||
| + | Please ensure that the following requirements are met by the Microsoft Exchange Server: | ||
| + | |||
| + | - The latest version of AhsayOBM is installed on the Exchange server / DAG member services. For Exchange Server 2010/2013/2016, Database Availability Group (DAG) backup option is available, please refer to Backing up Microsoft Exchange Server in Database Availability Group (DAG) for details.\\ \\ | ||
| + | - Ensure that all MS Exchange related services have been started, particularly the MS Exchange Information Store Service.\\ \\ To verify this setting, launch Services in Windows by clicking Start then typing “Services” in the search box. All Exchange related services should be started by default, in case if it is not, turn it on by right clicking the item then selecting Start.\\ {{public:ahsay_wiki_module_exchange_database_01.png}} \\ \\ | ||
| + | - 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 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 the Microsoft Exchange Server add-on module has been enabled for your AhsayOBM user account. Contact your backup service provider for more details.\\ \\ | ||
| + | - 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.\\ \\ | ||
| + | - Ensure that the Microsoft Exchange Writer is installed and running on the Exchange Server, and the writer state is Stable. This can be verified by running the vssadmin list writers command. | ||
| + | |||
| + | ===== Documentation ===== | ||
| + | |||
| + | * [[https://www.ahsay.com/download/download_document_v8_obm-user-guide-exchange-db.jsp|Microsoft Exchange Server Database Backup and Restore Guide]] | ||
| + | |||
| + | ===== Issues ===== | ||
| + | |||
| + | * [[public:5216_issue:cannot_start_shadow_copy_reason_the_writer_operation_failed_because_of_an_error_that_might_recur_if_another_shadow_copy_is_created._vss_e_writererror_nonretryable|“Cannot start shadow copy, reason =The writer operation failed because of an error that might recur if another shadow copy is created. (VSS_E_WRITERERROR_NONRETRYABLE)”]] | ||
| + | * [[public:5348_vss_e_flush_writes_timeout_during_exchange_server_backup|VSS_E_FLUSH_WRITES_TIMEOUT (MS Exchange server backup)]] | ||
| + | * [[public:5078_issue:incorrect_error_message_another_backup_job_is_still_running_is_displayed_ms_exchange_server_backup|Incorrect error message 'Another backup job is still running' is displayed (MS Exchange server backup)]] | ||
| + | * [[public:5088_issue:ms_exchange_server_backup_job_cannot_run_to_completion_for_backup_set_with_backup_schedule_disabled|MS Exchange server backup job cannot run to completion (for backup set with backup schedule disabled)]] | ||
| + | * [[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: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.txt · Last modified: 2022/11/28 11:05 by kirk.lim