Chat now with support
Chat with Support

Replicator 7.4 - Product and Concepts Guide

Factors Affecting Threading

Consider the following factors found within your SharePoint environment that will use threading:

·Outbound or inbound processing.

·Map families.


·Site collections.

·Classification queue numbers.

Each of these factors can be processed independently to distribute the load across multiple threads and will, therefore, determine the edition of Replicator that will best suit your environment. They also, therefore, determine how many threads you can take advantage of at a time.

Enterprise Edition

Enterprise Edition has a default of 10 threads working at the same time. This number can be increased to an unlimited number of threads operating at the same time. This is particularly convenient in a hub-and-spoke architecture, where Enterprise edition is set up at the hub. With Enterprise edition you will be able to handing incoming and outgoing processes for multiple spokes, allowing Replicator to function in real-time, even in more strenuous scenarios.

It is, however, important to keep in mind that we are limited by the number of threads that you can take advantage of, as replication works in sequence order.

Enterprise edition is also the only edition which allows horizontal scaling. With this edition you can use multiple engines, thereby allowing you to disperse the load placed on any one machine by dividing the load of processing between them.

Advantages for having multiple replication engines in a farm include:

1.In the event that one of your servers stop, you have another which will insure the continuity of replication operations. This ensures high availability on your farms.

2.You spread the load of processing packages between multiple replication engines, allowing your machines to work faster due to parallel processing.

For example, you can shape your farm to have two Enterprise Replication engines running in parallel. You can specify that each engine handle a maximum of five threads at a time, thereby evenly distributing the load placed on each engine. In turn, both engines will be able to work faster, optimizing both your system as well as the functionality of Replicator.


NOTE: that horizontal scaling is entirely transparent to the user, and therefore the use has no control of it.


Metalogix Replicator Specifications

This section summarizes the capabilities of Metalogix Replicator.

Editions and Features

Built from the ground up and based on Microsoft technologies, Replicator has matured to fully support mission critical applications. Our customers use our products in a wide variety of business applications including disaster recovery, mobile platform data replication, and fully distributed fringe data networks. The use of Replicator varies as widely as the variety of SharePoint deployments. To meet the needs of this diverse customer base, Replicator is available in several editions, with additional support for replicating SharePoint look and feel features.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating