public:module:microsoft_exchange_mail_level_2016:best_practices
Differences
This shows you the differences between two versions of the page.
|
public:module:microsoft_exchange_mail_level_2016:best_practices [2019/09/19 17:09] ronnie.chan created |
public:module:microsoft_exchange_mail_level_2016:best_practices [2019/09/19 17:09] ronnie.chan |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| * **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 CloudBacko Pro 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 CloudBacko Pro 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> |
| 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 36: | Line 36: | ||
| 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. | ||
| </WRAP> | </WRAP> | ||
| - | </WRAP> | + | </WRAP></WRAP> |
public/module/microsoft_exchange_mail_level_2016/best_practices.txt · Last modified: 2019/09/19 17:09 by ronnie.chan
Page Tools
