Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 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 Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are 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 Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files 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

Changing the Managed Metadata Migration Batch Size

In order to better handle operations that include the migration of Managed Metadata having a very large number of terms or keywords, Metalogix Content Matrix separates migration operations into batches. This helps prevent timeouts during migration operations.

The default batch size is 50 terms, but this value can be changed through a parameter in the EnvironmentSettings.xml file.

To change the Managed Metadata Migration Batch Size:

In the EnvironmentSettings.xml file, navigate to the MMDTermsBatchSize entry and change its value to the desired batch size. The value must be a positive integer.

Configuring Metabase Settings

Metalogix Content Matrix lets you configure the location of the Metalogix Metabase file, which is a SQL database file that is used for storing metadata for a specific purpose, for a Console instance.  The Metalogix 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 Metalogix 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 the same 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

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

SQL Server Browser

3.Click [OK].

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.

Connection String Setting for Azure Private (Paid) Containers

UploadManagerAzureStorageConnectionString

If you are using Azure Private (paid) Containers, this is the storage account information for your Azure Blob storage, which allows containers to be created and files to be uploaded. Enter your account name and key in the following format:

<XmlableEntry>

   <Key>UploadManagerAzureStorageConnectionString</Key>

   <Value>DefaultEndpointsProtocol=https;AccountName={your account name};AccountKey={your account key}</Value>

</XmlableEntry>

Example:

<XmlableEntry>

   <Key>UploadManagerAzureStorageConnectionString</Key>

   <Value>DefaultEndpointsProtocol=https;AccountName=jdave;AccountKey=pnl7TvOJETTnr6Pheodq2DnF0piOozEBIUdVs2hrr8+l4Jzk2PXqdK0gBEz2qESzkr1c2JVQYJZooQe26pd2AA</Value>

</XmlableEntry>

 

NOTE: When migrating using the Import Pipeline, the Azure endpoint URL depends on the provided Azure storage connection string.  Refer to the following Microsoft article for more information: https://docs.microsoft.com/en-gb/office365/enterprise/URLs-and-ip-address-ranges?redirectSourcePath=%252farticle%252foffice-365-URLs-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2

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 filepath of C:\ProgramData\Metalogix 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

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

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating