Chat now with support
Chat with Support

Metalogix Content Matrix 9.4 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Metalogix StoragePoint Content is Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Configuring Settings for Migrations Using the Import Pipeline

Navigation:  Modifying Content Matrix Configuration and Settings > Client Side Configuration >

Configuring Settings for Migrations Using the Import Pipeline

Metalogix Content Matrix has various XML properties that can be modified to fine-tune or help troubleshoot your Import Pipeline migrations.  These properties can be found in the EnvironmentSettings.xml file.

For a list of supported migration actions, see Objects and Actions Supported for Using the Import Pipeline.

Batch Size Settings

The following XML properties can optionally be modified. However, it is generally recommended to not modify these values unless you are encountering issues when migrating using the Import Pipeline.

UploadManagerMaxBatchesToUpload

This controls the number of batches that can be uploaded simultaneously to Azure storage. The default value is 2 and the value must be a positive integer. Only increase this value in small increments (4, 5, 6, etc.), and only when taking into consideration your total upload bandwidth, resources such as CPU and free memory on the workstation that is performing the migration, batch size, and so on.

<XmlableEntry>

   <Key>UploadManagerMaxBatchesToUpload</Key>

   <Value>2</Value>

</XmlableEntry>

UploadManagerBatchSizeItemThreshold

This key controls the maximum batch size in item count, including all folders and documents, to be used if Content Matrix will be submitting batches according to number of items. The default value is 200 and the value must be a positive integer.

<XmlableEntry>

   <Key>UploadManagerBatchSizeItemThreshold</Key>

   <Value>200</Value>

</XmlableEntry>

UploadManagerBatchSizeMBSizeThreshold

This key controls the maximum batch size to be used if Content Matrix will be submitting batches according to size. The default value is 1000 megabytes and the value must be a positive integer. The value should be set carefully, taking into consideration factors such as total upload bandwidth, speed of data retrieval from the source system, and so on.

<XmlableEntry>

   <Key>UploadManagerBatchSizeMBSizeThreshold</Key>

   <Value>1000</Value>

</XmlableEntry>

Batch Resubmission Settings

MaxAzureBatchRetryCount

This key controls the maximum number of times Content Matrix will resubmit the batch until it is successfully migrated.  (The default value is 5.)

<XmlableEntry>
   <Key>MaxAzureBatchRetryCount</Key>
   <Value>5</Value>
</XmlableEntry>

 

ErrorMessagesForRetryAzureBatch

This key specifies error conditions for which you want Content Matrix to resubmit a batch, when it normally would not.  

NOTE:  Separate multiple error messages with a pipe character (|), as shown in the example below.

<XmlableEntry>

   <Key>ErrorMessagesForRetryAzureBatch</Key>

   <Value>Item does not exist|Object Reference Not Set</Value>

 </XmlableEntry>

 

RetryBatchForCustomListWithVersions

By default, if you are migrating a batch that includes a list with a base type of CustomList (such as Announcements) and versioning is enabled, these lists are excluded from the resubmission, because duplicate items may be migrated to the target if the batch is resubmitted.  You can choose to include these types of lists in resubmissions, however, by  changing the value of the key RetryBatchForCustomListWithVersions from False to True.

NOTE:  If custom lists are being excluded from batch resubmissions and all items are not successfully migrated, you can migrate any outstanding items using incremental migration.

<XmlableEntry>

   <Key>RetryBatchForCustomListWithVersions</Key>

   <Value>False</Value>

 </XmlableEntry>

Special Purpose Settings

UploadManagerLocalTemporaryStorageLocation

This key indicates the directory in which the temporary binary files and manifest XML files for each batch are saved. If no filepath is specified, the default file path is used.

<XmlableEntry>

   <Key>UploadManagerLocalTemporaryStorageLocation</Key>

   <Value>C:\ProgramData\Metalogix\Temp folder sample</Value>

</XmlableEntry>

UploadManagerMaxRetryCountThresholdForJobResubmission

WARNING: This value should not be changed unless absolutely necessary.

This key controls the amount of time to wait for a response from the reporting queue before re-requesting a migration job. This value is specified in multiples of 15 seconds, meaning that the default value of 960 corresponds to 4 hours and the minimum value of 120 corresponds to 30 minutes. This value must be a positive integer greater than or equal to 120.

<XmlableEntry>

   <Key>UploadManagerMaxRetryCountThresholdForJobResubmission</Key>

   <Value>960</Value>

</XmlableEntry>

Configuring Content Matrix to Run in a FIPS-enabled Environment

Navigation:  Modifying Content Matrix Configuration and Settings > Client Side Configuration >

Configuring Content Matrix for a FIPS-enabled Environment

If your organization is subject to U.S. Federal Information Processing Standards (FIPS) and runs in a FIPS-enabled environment, you can make Content Matrix compatible with that environment by changing the value of the key FIPSEnabled in the EnvironmentSettings.xml file to True.

Environment Settings FIPS

Changing Resource Utilization Settings

Navigation:  Modifying Content Matrix Configuration and Settings >

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

Navigation:  [No topics above this level]

Configuring Metalogix Content Matrix for Distributed Migration

You can use Distributed Migration to significantly improve the time it takes to complete large migration jobs by distributing 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 productivity from deployed resources.

The feature consist of a central Distributed Database and one or more Distributed Migration agents.

Distributed Migration New Model

Distributed Migration Components

Distributed Migration relys on the following components:

Distributed Database

This is a SQL Server database that contains the repository or queue of migration job definitions which the agents can run. Distributed Migration agents share the same Distributed Database.

NOTE:  The Distributed Database cannot be a SQL CE database.

Agents

Agents are physical or virtual machines on which you can run migrations remotely.  Installed on each agent are the Content Matrix Console and the Metalogix Agent Service, which handles job queuing and processing.  Any available agent can pull a migration job that has been set to Run Remotely directly from the Distributed Database.

Any logging information is then be sent to the Distributed Database.

When an agent is running a migration job, any interaction with the agent, such as changing a configuration setting, is not recommended.

If Distributed Migration was configured prior to version 9.2:

To provide more efficient resource utilization, the Distributed Migration model has been re-architected to eliminate the use of a Controller to push jobs to agents. Instead, Distributed Migration uses a Windows Service that allows any available agent to pull a migration job that has been set to Run Remotely directly from the Distributed Database.

If you configured Distributed Migration prior to version 9.2, you will need to reconfigure each agent in order to continue using Distributed Migration and to run any migration jobs remotely.

Refer to the Reconfiguring Distributed Migration After an Upgrade guide for more information.

 

NOTE:  You will notice after an upgrade that the Configure Distributed Migration and Configure Self-Service options no longer display in the Content Matrix Console ribbon (Self-Service Migration has been removed as of version 9.2) and the Manage Agents dialog is empty.  

Important Note About Global Mappings and Environmental Settings

The first time that a connection is made to the Distributed Database, Global (Domain, Url, Guid, and User) Mappings and environmental settings are copied from the connecting user's local machine and used by all agents. With subsequent connections to the Distributed Database, a pop-up displays with the option to overwrite Mappings and local settings with those used by the currently-connecting user's machine.

Distributed Migration User Mappngs prompt

Global Mappings and settings can be copied from any machine that connects to the Distributed Database, even if it is not configured as an agent.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating