Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - Public Folder Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Connecting to Public Folders Connecting to SharePoint Preparing for Your Migration Configuring Copying Options Saving or Running a Migration Action Log Files Using PowerShell with Content Matrix Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Client Side Configuration

For an individual Metalogix Content Matrix Console instance, you can Configure Metabase Settings.

Configuring Metabase Settings

Metalogix Content Matrix lets you configure the location of the Metabase file, which is a SQL CE (Compact Edition) database file that is used for storing metadata for a specific purpose, for a Console instance.  The  metabase temporarily holds any migrating content's metadata so it can be moved into the target SharePoint instance. This allows for any metadata to be used with other features, such as Transformers.  The Metabase file itself is both created and deleted during the course of a migration action.

To configure Metabase settings:

1.In the Metalogix Content Matrix Console ribbon, choose Settings > Configure Default Metabase Settings to display the Change Metabase Default Settings dialog.

2.Select the appropriate configuration option.  Use the information in the following table for guidance.

Change Metabase Default Settings

If you want to …

Then …

specify a new folder in which to create the Metabase

·Select Provision New SQL Server Compact database.

·Click the folder icon (CONTEN~1_img239) and select the new location.

select an existing SQL Server Compact database (SDF) to use for the Metabase

·Select Use SQL Server Compact Database.

·Click the database/file icon (CONTEN~1_img240) and select the existing Metabase.

NOTE:  Metalogix Content Matrix will add and remove the Metabase tables during the migration.

select a SQL Server database in which to create and delete the Metabase tables

NOTE: This option allows Metalogix Content Matrix to place the Metabase directly into SQL Server. The main benefit being that it can allow for a performance boost when migrating large amounts of content, since it has a direct connection to SQL Server, and the Metabase logs will have a 4GB limitation that SQL Server files have.

·Select Use SQL Server database.

·Click the database icon (CONTEN~1_img241).

·Connect to the SQL Server using one of the following options:

§Manually enter the name or IP address for the SharePoint Database you want to connect to.

OR

§Chose a previously accessed SQL server from the drop-down.

OR

§Click [Browse] then navigate to and select either a Local or Network SQL server.

SQL Server Browser

3.Click [OK].

Changing Resource Utilization Settings

Metalogix Content Matrix can manage its performance level through the Resource Utilization Setting. This type of management is also known as throttling, and is used for any migration action that is run with Metalogix Content Matrix.

To edit Resource Utilization Settings:

From the Contrent Matrix Console ribbon, choose Settings > Edit Resource Utilization Settings.

Resource Utilizatin Settings

By default, the Efficiency value is set in the center or the slide bar. This is the recommended setting for best performance and resource utilization (use of RAM, CPU, Network and SharePoint load) during a migration.

If the slide bar is further to the left, the migration will run more slowly, but will have less chances of overloading the available resources and causing potential errors. If the slide bar is further to the right, it with use more system resources, and can speed the migration up, but could cause some potential errors if the system resources cannot handle the data being migrated. There is a chance that if the speed is too high, you would actually see a slowdown in the overall migration, because the migration is trying to run actions faster than the resources properly allow.

The actual values that are provided in the slide bar are determined by the systems resources (the system that has the Metalogix Content Matrix installed on it). A system with high resources will be able to run faster migrations, even if using the default setting, because over all available resources will be higher. This also means that the Efficiency and Speed values will have a larger spread between them. A system that has low resources will run more slowly, simply because it doesn't have the resources to run at faster levels. Again, this also affects the default values for Efficiency and Speed, since these numbers will be lower, and have a smaller spread between them.

NOTE: If the Efficiency is set to its maximum (all the way to the left), the migration will run more slowly, but the "slowest" speed will be the same between systems with high and low resources. The "slowest" value between systems will always be the same, however, the *"highest" value will be different based on the systems resources.

While this value can be set through the Contrent Matrix Console, you can also set it through the back end, if the UI setting does not seem to be working for you. Please contact Quest Support for more information on this back end setting.

Configuring Content Matrix for Distributed Migration

Metalogix Content Matrix can significantly improve the time it takes to complete migration jobs by using a distributed migration model. This model essentially consists of a Metalogix Content Matrix Console Controller (Host), a central jobs repository or queue, and one or more loosely-coupled Metalogix Content Matrix Console agents.

Distributed Migration Illustration

By automatically selecting the jobs from a central repository, Metalogix Content Matrix Console agents are able to distribute the workload efficiently across the resource pool. The distributed model enables parallel processing of migration jobs that reduces migration time, and enables higher utilization, better workload throughput and higher end-user productivity from deployed resources.

Connection icon

Distributed Migration supports the following SharePoint connection adapters:

·Metalogix Extensions Web Service (MEWS)

·SharePoint Client Side Object Model (CSOM)

·CSOM using the Azure Pipeline

Related Documents