Differences

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

--- public:documents_and_guides:v8:obm:exchange-mail-level-backup-ews:preparation [2020/04/29 13:49]
ronnie.chan created
+++ public:documents_and_guides:v8:obm:exchange-mail-level-backup-ews:preparation [2020/05/04 18:27] (current)
ronnie.chan
@@ Line 7: / Line 7: @@
 ==== 2.1.1 Software Requirement ====
-Refer to the following article for the list of compatible operating systems and application versions.
+Refer to the following article for the list of compatible operating systems and application versions. \\ [[public:8001_faq:ahsay_software_compatibility_list_scl_for_version_8.1_or_above|FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above]]
-FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above
 ==== 2.1.2 Antivirus Exclusion Requirement ====
@@ Line 15: / Line 13: @@
 To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to the following article the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list: http://wiki.ahsay.com/doku.php?id=public:8014_faq:suggestion_on_antivirus_exclusions
-NOTE
+<WRAP info>
 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.
+</WRAP>
 ==== 2.1.3 Upgrade VMware Tools Requirement ====
@@ Line 25: / Line 23: @@
 Below is the warning message that will be displayed if the version of the VMware Tools is less than 10.0.5.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image062.png?800}}
-NOTE
+<WRAP info>
+For more information about the upgrade of VMware Tools, refer to [[public:5288_ahsayobc_crash_on_vm_with_vmware_tools_pre-10.0.5.|this article]].
-For more information about the upgrade of VMware Tools, refer to this article http://wiki.ahsay.com/doku.php?id=public:5288_ahsayobc_crash_on_vm_with_vmware_tools_pre-10.0.5.
+</WRAP>
 ==== 2.1.4 AhsayOBM Installation ====
-AhsayOBM v8.1.0.0 or above must be installed either on the Exchange Server  2016 / 2019 hosting the database or on the remote backup machine.
+  * AhsayOBM v8.1.0.0 or above must be installed either on the Exchange Server  2016 / 2019 hosting the database or on the remote backup machine.
+  * AhsayOBM v8.3.0.96 or above must be installed either on the Exchange Server 2013  hosting the database or on the remote backup machine.
-AhsayOBM v8.3.0.96 or above must be installed either on the Exchange Server 2013  hosting the database or on the remote backup machine.
 ==== 2.1.5 Microsoft Exchange Mailbox Add-On Module ====
@@ Line 43: / Line 41: @@
 Please contact your backup service provider for more details.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image064.png?800}}
 ==== 2.1.6 AhsayOBM Licenses ====
-AhsayOBM licenses are calculated on a per device basis.
+AhsayOBM licenses are calculated on a per device basis:
-.   For backup of mailboxes on a standalone Microsoft Exchange 2013 / 2016 / 2019 Server, one AhsayOBM license is required.
+  * For backup of mailboxes on a standalone Microsoft Exchange 2013 / 2016 / 2019 Server, one AhsayOBM license is required.
+  * For backup of mailboxes on a Microsoft Exchange Server 2013 / 2016 / 2019 DAG setup, the number of AhsayOBM licenses required is equal to the number of DAG members in the DAG. For example, if there are three DAG members then three AhsayOBM licenses are required.
-.   For backup of mailboxes on a Microsoft Exchange Server 2013 / 2016 / 2019 DAG setup, the number of AhsayOBM licenses required is equal to the number of DAG members in the DAG. For example, if there are three DAG members then three AhsayOBM licenses are required.
 Please contact your backup service provider for more details
@@ Line 76: / Line 75: @@
 Scheduled backup is required if you choose to back up in DAG option on Exchange server as AhsayOBM on all DAG members will base on the scheduled backup time to start backup on all the 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.
+  * 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.
-.   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.
 However, for backup and restore on a remote backup machine, as the operation for single node can be done either manually or automatically, a scheduled backup is not required.
@@ Line 85: / Line 83: @@
 Ensure all nodes have mailbox role. This can be checked by accessing the Exchange admin center (EAC).
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image066.png?800}}
 ==== 2.1.13 Operating System ====
-.   For AhsayOBM installed on the Exchange Server 2013/2016/2019, the operating system must be Windows Server 2012/ 2012 R2/ 2016 / 2019 or above.
+  * For AhsayOBM installed on the Exchange Server 2013/2016/2019, the operating system must be Windows Server 2012/ 2012 R2/ 2016 / 2019 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 / 2019 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 / 2019 or above.
 ==== 2.1.14 Supported Exchange Server 2013 / 2016 / 2019 Version ====
-·         MS Exchange Server 2013 Cumulative Update 3 (CU3) or later is supported.
+  * MS Exchange Server 2013 Cumulative Update 3 (CU3) or later is supported.
+  * MS Exchange Server 2016 Cumulative Update 4 (CU4) or later is supported.
-·         MS Exchange Server 2016 Cumulative Update 4 (CU4) or later is supported.
+  * MS Exchange Server 2019 Cumulative Update 1 (CU1) or later is supported
-·         MS Exchange Server 2019 Cumulative Update 1 (CU1) or later is supported
 ==== 2.1.15  Exchange Servers Properties ====
@@ Line 106: / Line 103: @@
 Example: Get-ExchangeServer | Format-List Name, Edition,AdminDisplayVersion
-Please refer to the following Microsoft article for details of MS Exchange build numbers and releases: https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019
+Please refer to the following Microsoft article for details of MS Exchange build numbers and releases: [[https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019]]
 ==== 2.1.16  Windows User Account Permission ====
@@ Line 112: / Line 109: @@
 The Windows user account used for the backup must be a member of the following security groups.
-Exchange Server 2013/2016/2019
+<WRAP indent>
+=== Exchange Server 2013/2016/2019 ===
-*       Discovery Management (including ApplicationImpersonation and Mailbox Search)
-*       Organization Management
-*       Public Folder Management
-Login to the Exchange admin center, under permissions, admin roles.  Assign the user to be running the backup as member of the following admin roles:
-*       Discovery Management (including the following Roles):
-o   ApplicationImpersonation
-o   Mailbox Search
-*       Organization Management
-*       Public Folder Management
-Exchange Server 2013
-*       Microsoft Exchange Security \ Organization Management
-*       Users \ Administrator
-*       Users \ Domain Admins
+  * Discovery Management (including ApplicationImpersonation and Mailbox Search) \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image068.png?800}}
+  * Organization Management  \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image070.png?800}}
+  * Public Folder Management  \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image072.png?800}} \\ \\ Login to the Exchange admin center, under **permissions, admin roles**.  Assign the user to be running the backup as member of the following **admin roles**:
+    * Discovery Management (including the following **Roles**):
+      * ApplicationImpersonation
+      * Mailbox Search
+    * Organization Management
+    * Public Folder Management
-*       Users \ Enterprise Admins
+=== Exchange Server 2013 ===
-Ex2013_permission-resize.PNG
+  * Microsoft Exchange Security \ Organization Management
+  * Users \ Administrator
+  * Users \ Domain Admins
+  * Users \ Enterprise Admins \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image074.png?800}}
-Steps to check the current settings
+=== Steps to check the current settings ===
-.   Click Start > Control Panel > Administrative Tools, and then click Active Directory Users and Computers.
+. Click Start > **Control Panel** > **Administrative Tools**, and then click **Active Directory Users and Computers**.
-.   Browse to the organization unit containing the corresponding operating system account.
+. Browse to the organization unit containing the corresponding operating system account.
-.   Right click on the user, and select Properties.
+. Right click on the user, and select **Properties**.
 Select the Member Of tab to check on the membership setting.
+</WRAP>
 ==== 2.1.17 Enabling Mailbox ====
 The Windows user account must have an Exchange Server mailbox. Refer to the URL below for more information.
+<WRAP indent>
-Exchange Server 2013/2016/2019
+=== Exchange Server 2013/2016/2019 ===
-Refer to the following article from Microsoft for more details on how to check if an account is mailbox enabled and how to enable it:
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image076.png?800}}
-https://docs.microsoft.com/en-us/Exchange/recipients/create-user-mailboxes?view=exchserver-2019
+Refer to the following article from Microsoft for more details on how to check if an account is mailbox enabled and how to enable it: [[https://docs.microsoft.com/en-us/Exchange/recipients/create-user-mailboxes?view=exchserver-2019]]
-Exchange Server 2013
+=== Exchange Server 2013 ===
 Refer to the following article from Microsoft for more details on how to check if an account is mailbox enabled.
-https://docs.microsoft.com/en-us/exchange/create-user-mailboxes-exchange-2013-help
+[[https://docs.microsoft.com/en-us/exchange/create-user-mailboxes-exchange-2013-help]]
-Grant Mailbox Access Permission (Full Access)
+=== Grant Mailbox Access Permission (Full Access) ===
 Enter the following command in the Exchange Management Shell
@@ Line 175: / Line 161: @@
 Get-Mailbox | Add-MailboxPermission –User “%os_username%” –AccessRights FullAccess
-Example: granting permission to “administrator” account
+**Example:** granting permission to “administrator” account
 Get-Mailbox | Add-MailboxPermission –User “administrator” –AccessRights FullAccess
+</WRAP>
 ==== 2.1.18  Login Name Format Requirement ====
@@ Line 186: / Line 173: @@
 Ensure that the “Hide from address lists” option is unchecked for all mailboxes to be selected for backup.  Mailbox hidden from the address list will not be shown in the backup source selection menu.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image078.png?800}}
 ==== 2.1.20  Port Configuration ====
-As Exchange 2013 / 2016 / 2019 mail level backup and restore is implemented using Microsoft EWS API (Exchange Web Services), which enables AhsayOBM to access mailbox items such as email message, meetings, notes, calendar, contact, etc., without any additional installation or complicated setup required on the Exchange 2013 / 2016 / 2019 Server or remote backup machine, only port 443 must be configured to allow communication between AhsayOBM and Exchange server.
+As Exchange 2013 / 2016 / 2019 mail level backup and restore is implemented using Microsoft EWS API (Exchange Web Services), which enables AhsayOBM to access mailbox items such as email message, meetings, notes, calendar, contact, etc., without any additional installation or complicated setup required on the Exchange 2013 / 2016 / 2019 Server or remote backup machine, only **port 443** must be configured to allow communication between AhsayOBM and Exchange server.
 ==== 2.1.21  Exchange related Windows Services ====
-Ensure all MS Exchange related services have been started, particularly the MS Exchange Information Store.
+Ensure all MS Exchange related services have been started, particularly the **MS Exchange Information Store**.
-To verify this setting, launch the Services menu by clicking Start then typing “Services” in the search box. All Exchange related services should be started by default, in case it is not, turn it on by right clicking the item and then select Start.
+To verify this setting, launch the Services menu by clicking Start then typing “Services” in the search box. All Exchange related services should be started by default, in case it is not, turn it on by right clicking the item and then select **Start**.
-Ex2013_Services-resize.PNG
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image080.png?800}}
 ==== 2.1.22  MS Exchange Databases ====
@@ Line 203: / Line 192: @@
 Ensure the MS Exchange Mailbox and Public Folder databases are mounted. This can be verified by Exchange Management Shell or Exchange Admin Center (EAC).
-*       Type the following command in the Exchange Management Shell.
+  * Type the following command in the Exchange Management Shell.
+<WRAP indent>
+<code>
 Get-MailboxDatabase
+</code>
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image082.png?800}}
-*       Exchange Admin Center (EAC)
+</WRAP>
+  * Exchange Admin Center (EAC) \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image084.png?800}}
 ==== 2.1.23 Windows PowerShell ====
-Windows PowerShell 5.1 Engine for Exchange Server 2016/2019
+<WRAP indent>
+=== Windows PowerShell 5.1 Engine for Exchange Server 2016/2019 ===
 Ensure that Windows PowerShell 5.1 Engine is installed.
@@ Line 218: / Line 214: @@
 To install the feature:
-.   Navigate to Server Manager > Manage, then select Add Roles and Features.
+  * Navigate to **Server Manager** > **Manage**, then select **Add Roles and Features**.
-.   On the Select installation type screen, select Role-based or feature-based installation.
+  * On the **Select installation type** screen, select **Role-based or feature-based** installation.
-.   Select the target server.
+  * **Select** the target server.
-.   On the Select features screen, go to the Features option, check the box next to Windows PowerShell 5.1 Engine.
+  * On the Select **features** screen, go to the **Features** option, check the box next to **Windows PowerShell 5.1 Engine**. \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image086.png?800}}
-Windows PowerShell 2.0 Engine for Exchange Server 2013
+=== Windows PowerShell 2.0 Engine for Exchange Server 2013 ===
 Make sure the Windows PowerShell 2.0 Engine is installed.
@@ Line 232: / Line 228: @@
 To install the feature:
-.   Navigate to Server Manager > Manage, then select Add Roles and Features.
+  * Navigate to Server Manager > Manage, then select Add Roles and Features.
-.   On the Select installation type screen, select Role-based or feature-based installation.
+  * On the Select installation type screen, select Role-based or feature-based installation.
-.   Select the target server.
+  * Select the target server.
-.   On the Select features screen, go to the Features option, check the box next to Windows PowerShell 2.0 Engine.
+  * On the Select features screen, go to the Features option, check the box next to Windows PowerShell 2.0 Engine. \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image088.png?800}}
-Ex2013_PS2-resize.PNG
+</WRAP>
 ==== 2.1.24 .Net Framework ====
-.Net Framework 4.6.2 Features for Exchange Server 2016/2019
+<WRAP indent>
-Ensure .Net Framework 4.6.2 Features is installed. Please refer to the following URL for detailed information: https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016
+=== .Net Framework 4.6.2 Features for Exchange Server 2016/2019 ===
-This feature can be enabled by accessing Server Manager > Dashboard > Manage > Add Roles and Features Wizard > Feature Page.
+Ensure .Net Framework 4.6.2 Features is installed. Please refer to the following URL for detailed information: [[https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016]]
-.Net Framework 4.6.2 Features for Exchange Server 2013
+This feature can be enabled by accessing **Server Manager > Dashboard > Manage > Add Roles and Features Wizard > Feature Page**.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image090.png?800}}
+=== .Net Framework 4.6.2 Features for Exchange Server 2013 ===
 If you are using Exchange server 2013 on Windows server 2012, please install .Net Framework 3.5 Features.
-This feature can be enabled by accessing Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page.
+This feature can be enabled by accessing **Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page**.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image091.jpg?800}}
+</WRAP>
 ==== 2.1.25 Remote Exchange Management Shell ====
@@ Line 261: / Line 265: @@
 Enter the following command in Exchange Management Shell to enable this feature.
+<code>
 >Set-User "%os_username%" -RemotePowerShellEnabled $True
+</code>
 Reboot the Exchange Server after executing the command.
+<WRAP info>
-NOTE:
 Remote Shell in Microsoft Exchange Server enables you to manage your server running Exchange.
+</WRAP>
 ==== 2.1.26  LAN Manager Authentication Level ====
+<WRAP indent>
-Exchange Server 2013
+=== Exchange Server 2013 ===
 The LAN Manager Authentication level configured on the Exchange Server must be level 3 or above. Follow the steps below to check the settings.
-.   Click Start > Control Panel > Administrative Tools, and then click Local Security Policy.
+a. Click **Start > Control Panel > Administrative Tools**, and then click **Local Security Policy**. \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image093.png?800}}
-Ex2013_NTLMv2-resize.PNG
-.   Under Security Settings, expand Local Policies > Security Options, then click Network security: LAN Manager authentication level.
+b. Under **Security Settings**, expand **Local Policies > Security Options**, then click **Network security: LAN Manager authentication level**.
-.   Make sure that the setting is configured to use NTLMv2, for example:
+c. Make sure that the setting is configured to use NTLMv2, for example:
-*         Send NTLMv2 response only
+  * Send NTLMv2 response only
+  * Send NTLMv2 response only. Refuse LM
+  * Send NTLMv2 response only. Refuse LM & NTLM \\ {{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image095.png?800}}
-*         Send NTLMv2 response only. Refuse LM
+</WRAP>
-*         Send NTLMv2 response only. Refuse LM & NTLM
+==== 2.1.27  IISAuthenticationMethods Setting ====
-Ex2013_NTLMv2_2-resize.PNG
+Verify if the IISAuthenticationMethods is set to Basic only. If so, change the setting with the commands below.
-.1.27  IISAuthenticationMethods Setting
+<WRAP indent>
-Verify if the IISAuthenticationMethods is set to Basic only. If so, change the setting with the commands below.
+=== Exchange Server 2013 ===
-Exchange Server 2013
+a. Click **Start > Microsoft Exchange Server > Exchange Management Shell**.
-.   Click Start > Microsoft Exchange Server > Exchange Management Shell.
+b. Enter the following command to check on the IISAuthenticationMethods setting:
-.   Enter the following command to check on the IISAuthenticationMethods setting:
+<code>
 >Get-OutlookAnywhere
+</code>
+c. If it is set to {Basic} only, enter the following command to modify the setting:
-.   If it is set to {Basic} only, enter the following command to modify the setting:
+<code>
 >Set-OutlookAnywhere -Identity:"%Server%\Rpc (Default Web Site)" -IISAuthenticationMethods Basic,NTLM,Negotiate
+</code>
 Reboot the Exchange server.
-===== 2.2    Supported Source =====
+</WRAP>
+===== 2.2 Supported Source =====
 Below is the supported mailbox type of Exchange Server 2013 / 2016 / 2019 Mail Level backup.
-Mailbox Level
+^ Mailbox Level ^^
+^ Item ^ Supported? ^
-Item
+^ User mailbox |	✔	|
+^ Public Folder |	✔	|
+^ Public Folder Mailbox |	✔	|
-Supported?
+^ Room Mailbox |	✔	|
+^ Equipment Mailbox |	✔	|
+^ Shared Mailbox |	✔	|
-Item
-Supported?
-User mailbox
-✔
-Room Mailbox
-✔
-Public Folder
-✔
-Equipment Mailbox
-✔
-Public Folder Mailbox
-✔
-Shared Mailbox
-✔
 Below are the items that you can backup or restore from an Exchange Server 2013 / 2016 / 2019 Mail Level backup set.
-Folder Level
+^ Folder Level ^^
+^ Folder ^ Supported? ^
-Item
+^ Inbox |	✔	|
+^ Drafts |	✔	|
+^ Sent Items |	✔	|
-Supported?
+^ Deleted Items |	✔	|
+^ Archive |	✔	|
+^ Notes |	✔	|
-Item
+^ RSS Feeds |	✔	|
+^ Junk Email |	✔	|
+^ Tasks |	✔	|
-Supported?
+^ Calendar |	✔	|
+^ Contacts |	✔	|
-Inbox
-✔
-RSS Feeds
-✔
-Drafts
-✔
-Junk Email
-✔
-Sent Items
-✔
-Tasks
-✔
-Deleted Items
-✔
-Calendar
-✔
-Archive
-✔
-Contacts
-✔
-Notes
-✔
 ===== 2.3 Limitation =====
@@ Line 442: / Line 352: @@
 For backup and restoration of Exchange 2013 / 2016 / 2019 Mail Level backup set, there is some limitation:
-.         If you are trying to restore item(s) from one mailbox to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).
+a. If you are trying to restore item(s) from one mailbox to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).
-Example: Item from “Inbox” folder of Mailbox-A will be restored to the “Inbox” folder of the alternate location Mailbox-B; Item from “Drafts” folder of Mailbox-A will be restored to the “Drafts” folder of the alternate location Mailbox-B.
+**Example:** Item from “Inbox” folder of Mailbox-A will be restored to the “Inbox” folder of the alternate location Mailbox-B; Item from “Drafts” folder of Mailbox-A will be restored to the “Drafts” folder of the alternate location Mailbox-B.
-.         If you are trying to restore item(s) from several mailboxes to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) in alternate location mailbox with the same name of the original folder(s).
+b. If you are trying to restore item(s) from several mailboxes to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) in alternate location mailbox with the same name of the original folder(s).
-Example: Item from “Inbox” folder of Mailbox-A and Mailbox-B will be restored to the “Inbox” folder of the alternate location Mailbox-C.
+{{public:documents_and_guides:obm:exchange-mail-level-backup-ews:image097.png?800}}
-.         Restore of mailbox items or public folder items is only supported if the according mailbox or public folder exists.
+**Example:** Item from “Inbox” folder of Mailbox-A and Mailbox-B will be restored to the “Inbox” folder of the alternate location Mailbox-C.
-.         Only Alternate Location is supported for restoring mailbox items to another domain.
+c. Restore of mailbox items or public folder items is only supported if the according mailbox or public folder exists.
-.         Restore of mailbox item(s) in public folder to an alternate location mailbox is not supported.
+d. Only Alternate Location is supported for restoring mailbox items to another domain.
-Example: Restore of mailbox item(s) in public folder from Mailbox-A to alternate location Mailbox-B is not supported.
+e. Restore of mailbox item(s) in public folder to an alternate location mailbox is not supported.
-.         If you are trying to restore the mailbox item to a destination mailbox which has a different language setting than the original mailbox, AhsayOBM will restore mailbox item(s) to their respective destination folder based on the translation listed below.
+**Example:** Restore of mailbox item(s) in public folder from Mailbox-A to alternate location Mailbox-B is not supported.
+f. If you are trying to restore the mailbox item to a destination mailbox which has a different language setting than the original mailbox, AhsayOBM will restore mailbox item(s) to their respective destination folder based on the translation listed below.
 For folders such as ‘Calendar’ or ‘Notes’, a new folder ‘Calendar’ or ‘Notes’ will be created.
-Backup source (English)
+^ Backup source (English) ^ Action ^ Destination mailbox with Chinese as default language settings ^
+^ Inbox | Merge | 收件箱 |
+^ Outbox | Merge | 寄件匣 |
+^ Sent Items | Merge | 寄件備份 |
+^ Deleted Items | Merge | 刪除的郵件 |
+^ Drafts | Merge | 草稿 |
+^ Junk E-Mail | Merge | 垃圾電郵 |
+^ Calendar | Create new folder | Calendar |
+^ Notes | Create new folder | Notes |
-Action
+===== 2.4 Best Practice and Recommendation =====
-Destination mailbox with Chinese as default language settings
-Inbox
-Merge
-收件箱
-Outbox
-Merge
-寄件匣
-Sent Items
-Merge
-寄件備份
-Deleted Items
-Merge
-刪除的郵件
-Drafts
-Merge
-草稿
-Junk E-Mail
-Merge
-垃圾電郵
-Calendar
-Create new folder
-Calendar
-Notes
-Create new folder
-Notes
-===== 2.4    Best Practice and Recommendation =====
 The following are some best practices or recommendations we strongly recommend you follow before you start any Exchange Server 2013 / 2016 / 2019 Mail Level backup and restore.
-*             Mail Level Backup must be utilized in conjunction with Database Level Backup to fully protect an Exchange Server.
+  * Mail Level Backup must be utilized in conjunction with Database Level Backup to fully protect an Exchange Server.
+  * Active Directory server should be protected by regular full Window System Backup at least once every two weeks.
-*             Active Directory server should be protected by regular full Window System Backup at least once every two weeks.
+  * For AhsayOBM installed on Exchange Server, enable scheduled backup jobs when system activity is low to achieve the best possible performance.
+  * The remote backup machine should be on the same LAN as the MS Exchange server for optimal backup and restore performance.
-*             For AhsayOBM installed on Exchange Server, enable scheduled backup jobs when system activity is low to achieve the best possible performance.
+  * To provide maximum data protection and flexible restore options, it is recommended to configure:
+  * At least one offsite or cloud destination
-*             The remote backup machine should be on the same LAN as the MS Exchange server for optimal backup and restore performance.
+  * At least one local destination for fast recovery
+  * 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.
-*             To provide maximum data protection and flexible restore options, it is recommended to configure:
+  * **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 2013 / 2016 / 2019 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.
-*       At least one offsite or cloud destination
-*       At least one local destination for fast recovery
-*             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.
-*             For backup of a large number of mailboxes, it is recommended to divide all mailboxes into multiple backup sets. By default, the MS Exchange 2013 / 2016 / 2019 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>
 Example-1: There are 100 mailboxes that need to be backup, you can divide 20 mailboxes into one backup set.
-Backup Set Name
+^ Backup Set Name ^ Mailbox Number ^
+^ Backup-Set-1 | No.1 -- 20 |
+^ Backup-Set-2 | No.21 -- 40 |
-Mailbox Number
+^ Backup-Set-3 | No.41 -- 60 |
+^ Backup-Set-4 | No.61 -- 80 |
-Backup-Set-1
+^ Backup-Set-5 | No.81 -- 100 |
+| Note: If there are new mailboxes added, you can create new backup set for the new mailboxes. ||
-No.1 -- 20
-Backup-Set-2
-No.21 -- 40
-Backup-Set-3
-No.41 -- 60
-Backup-Set-4
-No.61 -- 80
-Backup-Set-5
-No.81 -- 100
-Note: If there are new mailboxes added, you can create new backup set for the new mailboxes.
 Example-2: There are 100 mailboxes that needs to be backup, you can divide mailboxes into backup sets in alphabetic order.
-Backup Set Name
+^ Backup Set Name ^ Mailbox Name Start with ^
+^ Backup-Set-1 | A -- E |
+^ Backup-Set-2 | F -- J |
-Mailbox Name Start with
+^ Backup-Set-3 | K --O |
+^ Backup-Set-4 | P -- T |
-Backup-Set-1
+^ Backup-Set-5 | U -- Z |
+| Note: If there are new mailboxes added, you can add the new mailboxes into the original backup set by the corresponding alphabetic order. ||
+</WRAP>
-A -- E
-Backup-Set-2
-F -- J
-Backup-Set-3
-K --O
-Backup-Set-4
-P -- T
-Backup-Set-5
-U -- Z
-Note: If there are new mailboxes added, you can add the new mailboxes into the original backup set by the corresponding alphabetic order.

User Tools

Site Tools

Differences

Page Tools