We are committed to bringing you a comprehensive Exchange 2016 Mail Level backup solution with CloudBacko Pro. Below are some key areas that we can help to make your backup experience a better one.
We understand that restore could be a time and resources consuming process, which is why CloudBacko Pro is designed with advanced technologies to make restore a fast and efficient process by restoring individual mail items without the need to restore the whole Exchange server database.
CloudBacko Pro supports recovery directly to a live production MS Exchange server, so there is no service interruption or downtime incurred, and also the user mailboxes do not have to be disabled and can function normally during the recovery procedure.
The backup resources can be mailbox level, folder level and even item level.
CloudBacko Pro provides backup and restore option for different version of exchange server to fulfill your requirement.
You may wish to run backup at a specified time interval of your choice, that’s why we also allow you to set your own backup schedules so that you can take full control of the time when to perform backup.
We understand your Exchange mail objects may contain sensitive information that requires to be protected, that is why your backup data will be encrypted with the highest level of security measure.
The technology utilizes the computing power of multiple CPU cores for creating multiple backup and restore threads to produce fast backup and restore performance.
The default setting for MS Exchange 2016 mail level backup sets supports:
The index file structure has been re-designed to improve the backup and restore performance. Each Exchange 2016 mailbox will have its own individual index file instead of a single index file for all mailboxes within the backup set.
This new design eliminates any potential I/O performance bottlenecks when the index file is updated during each backup job, which can occur when using single index file structure for multi-thread concurrent backup.
The implementation of one index file per mailbox can significantly improve the overall resilience of backup and restore from index related issues.
For example, if a single index file is corrupted, it will only affect the corresponding mailbox, while other mailboxes selected for backup are unaffected.
To offer you with the highest flexibility of backup destination, you can now back up mail objects to a wide range of cloud storage destinations. Utilizing cloud destination backup gives you an extra layer of protection in the event of a local drive corruption, where you will still be able to retrieve data from the cloud destination. The list of supported destination can be found here: supported cloud destinations
CloudBacko Pro supports Mail Level backup and restore of Exchange Server 2016 by installing the client agent either on the Exchange server hosting the database, or on a remote backup machine.
Below is a comparison table on the differences on backup and restore with CloudBacko Pro installation on an Exchange server and on a remote backup machine.
|On Server Backup||Remote Backup|
|Backup|| * Backup jobs will utilize the Exchange server’s resources, so it may impact the server performance. If the load on Exchange server is already high, this can impact the backup performance. |
* There is minimal performance issue with the transfer of mail items from the Exchange mail store to CloudBacko Pro.
| * Backup jobs will utilize the remote backup machine’s resources, therefore, there is minimal impact on the Exchange server performance.
* Backup performance can be affected by the network connection speed between the Exchange server and the remote backup machine, especially for connection over the Internet.
* General backup performance issues can be easily resolved by installing CloudBacko Pro on a more powerful backup machine.
|Large Number of MailboxesLarge Number of Mailboxes|| * Backup of a large number of mailboxes can take more time to complete. |
For example, it may not be possible to run multiple mail level backup sets concurrently on the Exchange server for 1000 user mailboxes, as it may affect the server performance, so administrator may be limited to start one backup set at a time.
1 backup set can only have a total of 16 concurrent threads by default.
| * Backup of a large number of mailboxes can take less time to complete.
For example, 1000 user mailboxes can be divided into 5 separate backup sets of 200 mailboxes each. The 5 backup sets can be started concurrently on 1 machine or started by multiple machines.
5 backup sets * 16 concurrent threads = 80 concurrent threads
|Backup Scheduling||* For environment with limited backup window, there may not be sufficient time to complete both database and mail level backup jobs on a daily basis.|| * For environment with limited backup window, remote backup may be a good option as the mail level backup can be completed remotely, while the database backup can be completed on the Exchange server at the same time period.
* Continuous backup can be enabled without significant impact on the Exchange server performance, as backup jobs will utilize the resources of the remote backup machine.
|Restore||* The restore of mailbox items to another (standby) MS Exchange server, requires installation of CloudBacko Pro on the new MS Exchange server.|| * Easily restore mailbox items to another (standby) MS Exchange server, without the need to reinstall CloudBacko Pro.
* Restore mailbox items without direct / physical access to the MS Exchange server.
* Restore performance can be affected by any network connection issue between the Exchange server and the remote backup machine, especially if the connection is over the Internet.