Essentials for Office 365 2.11 - Performance Optimization Guide

64-bit Architecture

Windows 64-bit architecture is strongly recommended due to the advancement in memory allocation over

32-bit.  A 64-bit architecture will allow memory allocation to the Essentials software greater than the

1.5GB maximum from old, so please be sure that both your hardware and software are 64-bit compatible.

Antivirus Scanners and Exceptions

Antivirus Scanners are applications that are great for keeping bad things out, but not so great when you are running operations that move large amounts of data quickly (i.e. migrations and backup).  If at all possible, disable all antivirus and malware scanners that are actively monitoring your host machine.  If a complete disable is not possible, please strongly consider adding exceptions to the following locations:

•Metalogix Essentials for Office 365 installation directory.  By default, this is C:\Program

Files\Quest\Essentials or C:\Program Files (x86)\Quest\Essentials

•Metalogix Essentials for Office 365 workspace directory.  By default, this is C:\Users\{UserDirectory}\Essentials

•Metalogix Essentials for Office 365 temporary directory.  By default, this is

C:\Users\{UserDirectory}\AppData\Local\Temp

•Metalogix Essentials for Office 365 backup location.  If you are storing backups locally, please add this location(s) to the exception list as well.

Other Software

This should go without saying, but if possible please dedicate the entire host machine to running the migration and/or backup only.  If you are running the Essentials software on your laptop while you are also running Outlook, web browser sessions or any other software, they will all compete for system resources thus leading to performance degradation.  Whenever possible, the minimal amount of software should be running on the host.

Deployment Location

Earlier in the Architecture section we outlined how Essentials for Office 365 sits “between” source and destination repositories, but that may not always be the optimal deployment.  Although Essentials operates as a “no server side” install piece of software, there may be instances when installing it to your source or destination server or SharePoint WFE may provide a substantial performance increase.  If you reference the Architecture diagram, you will notice the data flows from source through Essentials (on the host) and then ultimately to the destination, but what if Essentials was deployed on to the source or destination directly?  That would minimize one entire network transfer from the operation leading to a more direct source to destination content move.  As you can imagine, in some environments this can lead to very impressive performance gains and if possible, one of our more strongly recommended configurations.