public:microsoft_exchange_mail_level_2016
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:microsoft_exchange_mail_level_2016 [2019/08/20 14:11] ronnie.chan |
public:microsoft_exchange_mail_level_2016 [2022/11/28 11:05] (current) kirk.lim |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Microsoft Exchange 2016 Mail Level Backup Set ====== | + | ====== Microsoft Exchange 2016 / 2019 Mail Level Backup Set ====== |
| - | AhsayOBM allows you to back up individual mailboxes in your Microsoft Exchange Server 2016 with the MS Exchange Mail Level Backup Module. This module provides a set of tools to protect your mailboxes and public folders on Microsoft Exchange Server 2016. This includes backup and recovery of individual emails, contacts, calendars and other mail items in your mailboxes and public folders, with snapshots / versioning, and retention policy to protect even email that you may have accidentally deleted from your Exchange 2016 mailboxes or public folders. | + | Last modified: 2020/04/27 (Note: Content written for AhsayCBS v7+v8, and may generally apply to latest product release) |
| + | |||
| + | AhsayOBM allows you to back up individual mailboxes in your Microsoft Exchange Server 2016 / 2019 with the MS Exchange Mail Level Backup Module. This module provides a set of tools to protect your mailboxes and public folders on Microsoft Exchange Server 2016. This includes backup and recovery of individual emails, contacts, calendars and other mail items in your mailboxes and public folders, with snapshots / versioning, and retention policy to protect even email that you may have accidentally deleted from your Exchange 2016 / 2019 mailboxes or public folders. | ||
| Mail Level Backup must be utilized in conjunction with full Information Store Backup as Mail Level backup for Microsoft Exchange Server is not designed to fully protect an Exchange Server, but to facilitate easy backup and fast restoration of individual emails, contacts, calendars or public folder, etc. | Mail Level Backup must be utilized in conjunction with full Information Store Backup as Mail Level backup for Microsoft Exchange Server is not designed to fully protect an Exchange Server, but to facilitate easy backup and fast restoration of individual emails, contacts, calendars or public folder, etc. | ||
| Line 14: | Line 16: | ||
| Below is the system architecture diagram illustrating the major elements involved in the backup and restore process among the Microsoft Exchange Server 2016, AhsayOBM and AhsayCBS. | Below is the system architecture diagram illustrating the major elements involved in the backup and restore process among the Microsoft Exchange Server 2016, AhsayOBM and AhsayCBS. | ||
| - | ==== AhsayOBM installed on Exchange Server 2016 ==== | + | ==== AhsayOBM installed on Exchange Server 2016 / 2019 ==== |
| **Standalone:** The latest version of AhsayOBM is installed on the Exchange server which is connected to AhsayCBS backup server through LAN or internet. | **Standalone:** The latest version of AhsayOBM is installed on the Exchange server which is connected to AhsayCBS backup server through LAN or internet. | ||
| - | {{public:ahsay_wiki_module_exchange_2016_mail_01.png?640}} | + | {{public:content_components_exchange.png?640}} |
| **Database Availability Group (DAG):** The latest version of AhsayOBM is installed on all the DAG members on Exchange server which is connected to AhsayCBS backup server through LAN or internet, and all the DAG members share the same backup set. | **Database Availability Group (DAG):** The latest version of AhsayOBM is installed on all the DAG members on Exchange server which is connected to AhsayCBS backup server through LAN or internet, and all the DAG members share the same backup set. | ||
| - | {{public:ahsay_wiki_module_exchange_2016_mail_02.png?640}} | + | {{public:content_components_dag_2016.png?640}} |
| ==== AhsayOBM installed on Remote Backup Machine ==== | ==== AhsayOBM installed on Remote Backup Machine ==== | ||
| Line 28: | Line 30: | ||
| Standalone: The latest version of AhsayOBM is installed on the remote backup machine which is connected to Exchange server and AhsayCBS backup server through LAN or internet. | Standalone: The latest version of AhsayOBM is installed on the remote backup machine which is connected to Exchange server and AhsayCBS backup server through LAN or internet. | ||
| - | {{public:ahsay_wiki_module_exchange_2016_mail_03.png?640}} | + | {{public:content_components_exchange_remote.png?640}} |
| Database Availability Group (DAG): The latest version of AhsayOBM is installed on the remote backup machine which is connected to DAG members on Exchange server and AhsayCBS backup server though LAN or internet, and all the DAG members share the same backup set. | Database Availability Group (DAG): The latest version of AhsayOBM is installed on the remote backup machine which is connected to DAG members on Exchange server and AhsayCBS backup server though LAN or internet, and all the DAG members share the same backup set. | ||
| - | {{public:ahsay_wiki_module_exchange_2016_mail_04.png?640}} | + | {{public:content_components_dag.png?640}} |
| ---- | ---- | ||
| Line 45: | Line 47: | ||
| To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to the [[public:8014_faq:suggestion_on_antivirus_exclusions|list of processes and directory paths that should be added to all antivirus software white-list / exclusion list]]. | To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to the [[public:8014_faq:suggestion_on_antivirus_exclusions|list of processes and directory paths that should be added to all antivirus software white-list / exclusion list]]. | ||
| - | <WRAP prewrap><code> | + | <WRAP info> |
| - | NOTE | + | |
| The bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA. | The bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA. | ||
| - | </code></WRAP> | + | </WRAP> |
| ==== AhsayOBM Installation ==== | ==== AhsayOBM Installation ==== | ||
| Line 73: | Line 74: | ||
| ==== Java Heap Size ==== | ==== Java Heap Size ==== | ||
| - | The default Java heap size setting on AhsayOBM is 2048MB. For Exchange 2016 mail level backup, it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on amount of free memory available on your Exchange 2016 server. | + | The default Java heap size setting on AhsayOBM is 2048MB. For Exchange 2016 / 2019 mail level backup, it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on amount of free memory available on your Exchange 2016 server. |
| ==== Temporary Directory Folder ==== | ==== Temporary Directory Folder ==== | ||
| Line 89: | Line 90: | ||
| ==== Operating System ==== | ==== Operating System ==== | ||
| - | * For AhsayOBM installed on the Exchange Server 2016, the operating system must be Windows Server 2012/ 2012 R2/ 2016 or above. | + | * For AhsayOBM installed on the Exchange Server 2016 / 2019, the operating system must be Windows Server 2012/ 2012 R2/ 2016 or above. |
| * For AhsayOBM installed on the remote backup machine, the operating system must be Windows 7/ 8/ 8.1/ 10 or Windows Server 2008/ 2008 R2/ 2012/ 2012 R2/ 2016 or above. | * For AhsayOBM installed on the remote backup machine, the operating system must be Windows 7/ 8/ 8.1/ 10 or Windows Server 2008/ 2008 R2/ 2012/ 2012 R2/ 2016 or above. | ||
| Line 221: | Line 222: | ||
| * Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It's important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws. | * Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It's important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws. | ||
| * **Distributed Backup Solution:** For backup of multiple or mass backup sets, to achieve better backup performance and to minimize any unnecessary loading on the Exchange server, please consider deploying AhsayOBM on remote backup machines as distributed backup solution instead of on the MS Exchange server. | * **Distributed Backup Solution:** For backup of multiple or mass backup sets, to achieve better backup performance and to minimize any unnecessary loading on the Exchange server, please consider deploying AhsayOBM on remote backup machines as distributed backup solution instead of on the MS Exchange server. | ||
| - | * For backup of a large number of mailboxes, it is recommended to divide all mailboxes into multiple backup sets. By default, the MS Exchange 2016 mail level backup module can back up a maximum of 4 mailboxes concurrently (4 concurrent backup threads), while backing up a maximum of 4 mail items concurrently per mailbox (4 concurrent backup threads). Therefore, each backup set supports a maximum of 4x4=16 backup threads at a time. By splitting up all mailboxes into separate backup sets, the more backup sets, the faster the backup process can achieve. \\ \\ | + | * For backup of a large number of mailboxes, it is recommended to divide all mailboxes into multiple backup sets. By default, the MS Exchange 2016 mail level backup module can back up a maximum of 4 mailboxes concurrently (4 concurrent backup threads), while backing up a maximum of 4 mail items concurrently per mailbox (4 concurrent backup threads). Therefore, each backup set supports a maximum of 4x4=16 backup threads at a time. By splitting up all mailboxes into separate backup sets, the more backup sets, the faster the backup process can achieve. |
| <WRAP indent><WRAP indent> | <WRAP indent><WRAP indent> | ||
| Example-1: There are 100 mailboxes that need to be backup, you can divide 20 mailboxes into one backup set. | Example-1: There are 100 mailboxes that need to be backup, you can divide 20 mailboxes into one backup set. | ||
| Line 232: | Line 232: | ||
| | Backup-Set-4 | No.61 -- 80 | | | Backup-Set-4 | No.61 -- 80 | | ||
| | Backup-Set-5 | No.81 -- 100 | | | Backup-Set-5 | No.81 -- 100 | | ||
| - | <WRAP prewrap><code> | + | <WRAP info> |
| If there are new mailboxes added, you can create new backup set for the new mailboxes. | If there are new mailboxes added, you can create new backup set for the new mailboxes. | ||
| - | </code></WRAP> | + | </WRAP> |
| Example-2: There are 100 mailboxes that needs to be backup, you can divide mailboxes into backup sets in alphabetic order. | Example-2: There are 100 mailboxes that needs to be backup, you can divide mailboxes into backup sets in alphabetic order. | ||
| Line 243: | Line 243: | ||
| | Backup-Set-4 | P -- T | | | Backup-Set-4 | P -- T | | ||
| | Backup-Set-5 | U -- Z | | | Backup-Set-5 | U -- Z | | ||
| - | <WRAP prewrap><code> | + | <WRAP info> |
| If there are new mailboxes added, you can add the new mailboxes into the original backup set by the corresponding alphabetic order. | If there are new mailboxes added, you can add the new mailboxes into the original backup set by the corresponding alphabetic order. | ||
| - | </code></WRAP> | + | </WRAP> |
| </WRAP> | </WRAP> | ||
| </WRAP> | </WRAP> | ||
| + | ---- | ||
| + | ===== Backup Process Overview ===== | ||
| + | The following steps are performed during an Exchange Mail Level backup job: | ||
| - | + | {{public:ahsay_wiki_module_exchange_2016_mail_18.png?800}} | |
| ---- | ---- | ||
public/microsoft_exchange_mail_level_2016.1566281509.txt.gz · Last modified: 2019/08/20 14:11 by ronnie.chan