Chatee ahora con Soporte
Chat con el soporte

Metalogix Essentials for Office 365 2.5 - Performance Optimization Guide

Performance Optimization Guide

Introduction

Metalogix Essentials for Office 365 allow users to migrate their data into SharePoint Online and also to backup both SharePoint and Office 365 data (OneDrive for Business and Exchange Online).  

This goal of this documents is to help provide several best practices for performance optimization around migration and backup using Metalogix Essentials for Office 365. These topics include: hardware, host, software and network recommendations.  

The following should be considered as guidance to optimize performance and throughput using this solution. For information about usage or features of the software, please refer to the User Guide found in the software’s Help menu or visit the following link: http://documents.quest.com/Metalogix-Essentials-For-Office-365

Understanding the Architecture

Before we begin describing methods that can be used to improve migration and backup performance, it is important to briefly understand the architecture of the Essentials for Office 365 solution.

Firstly, the solution is a client side application which means that it needs to be installed to either a physical or virtual computer to run.  From this host computer, all operations will be performed and all data will pass through.  Think of the software as sitting between your source and destination locations, whether that be an on premise SharePoint you are migrating to SharePoint Online or a OneDrive for Business site in Office 365 that is being backed up to Azure storage.

The diagram below provides a basic example of how Essentials for Office 365 communicates.  This simple example places the software between source and destination and highlights the data flow during a migration or backup operation. METALO~2_img5

As we will discuss a little later, any obstacles or hurdles that sit in the process of this data flow (load balancers, firewalls, antivirus scanners, VPN, etc.) may have a negative impact on throughput.  Wherever and whenever possible, we want to establish a path of least resistance.

To summarize, the typical deployment of Essentials for Office 365 is to install it on a host machine that sits between source and destination, allow the source data to pass through this host on its journey to the target.  Now, let’s begin to explore if this typical deployment is the optimal deployment to maximize performance.

Requirements

If you wish to explore all possible or recommended steps, then be prepared to become close friends with your IT department as permissions or exceptions may need to be granted in a few areas.  In general, typical deployments only require minimal permissions on the host machine and lower level SharePoint permissions, however optimized deployments can require slightly more.

Herramientas de autoservicio
Base de conocimientos
Notificaciones y alertas
Suporte de productos
Descargas de software
Documentación técnica
Foros de usuarios
Tutoriales en video
Aviso de actualizaciones de páginas web (RSS)
Comuníquese con nosotros
Obtenga asistencia con las licencias
Soporte Técnico
Ver todos
Documentos relacionados