Content Matrix 9.8 - Performance Optimization Guide

Database (DB)

The DB adapter is a read-only adapter designed for source side connections. If possible, always use the database adapter as the source for migrations, as it is the fastest adapter available in the application. It is also particularly useful for WAN based migrations or migrations to Office 365. This is because you can take database backups of your Content DBs, and move the resulting .bak files to a SQL Server on the target LAN (or Azure VMs in the case of O365 migrations), and then do a local migration.

DB connections look like this in the Metalogix Content Matrix UI once connected:

While the Database adapter does have some limitations, such as the inability to migrate Managed Metadata Services from one farm to another, you can use Metalogix Extensions Web Services (MEWS) for that part of the migration, and the DB Adapter for the rest of the migration for best performance when migrating between an on premises source and target.

Local Object Model (OM)

The OM adapter is the second fastest adapter available in the application, and the fastest adapter for writing content. It can only be accessed when Metalogix Content Matrix is directly installed on a WFE server in the SharePoint farm. This adapter is preferred if Metalogix Content Matrix is installed on a WFE server in the target SharePoint farm .

OM farm connections look like this in the Metalogix Content Matrix UI once connected:

Metalogix Extensions Web Service (MEWS)

The MEWS adapter is a very fast adapter, but requires installation of a solution on the source or target SharePoint farm which it is being used in. The solution is included in the Metalogix Content Matrix installer, and can be installed by running the installer on any WFE in the target SharePoint farm and selecting the “Install Metalogix Content Matrix SharePoint WSPs” button, then checking the box to install the “SharePoint Extensions Web Service.” If the target SharePoint farm will be connected to remotely, this adapter is preferred.

MEWS farm connections look like this in the Metalogix Content Matrix UI once connected:

NOTE:  The distinguishing factor between an OM connection and a MEWS connection is the “Local Connection” or “Remote Connection” string to the right of the connection.

Special Considerations for SharePoint Online Targets

Migrations from SharePoint on premises (on-prem) to SharePoint Online (referenced as SPO in this document), have a number of significant factors that make them more complex and time consuming than on premises to on premises SharePoint migrations. These factors include:

·Functional and Application Programming Interface (API) differences between SharePoint on-prem and SPO that result in some on-prem elements not being easy or possible to migrate to SPO.

·Performance-based limitations as a result of Microsoft’s protection mechanisms to ensure that no single SPO tenant/client can cause an entire multi-tenant farm to be unstable.

·Performance impact of the physical distance between a client’s on-prem SharePoint environment(s) and their SPO farm location.

This section explains why these limitations exist, and helps prepare Metalogix Content Matrix clients to plan a migration to SPO. This includes:

·Listing and explaining the functional and API limitations and their significance on migrations.

·Explaining the migration API leveraging Azure Storage to enhance the performance of content migrated to SPO.

·Ensuring that you allocate the appropriate time and consideration required when migrating their on premises farms to SPO.

The information in this section is essential reading for anyone migrating from SharePoint on-prem to SPO.