Chat now with support
Chat with Support

Metalogix Replicator 7.4 - Advanced Installation Guide

Hardware Requirements

Component

Requirement

Processor

Under normal circumstances, the Replicator processor requirements are the same as SharePoint. When replicating large amounts of SharePoint content, Replicator uses a greater amount of CPU capacity. The expected load is comparable to up to 10 full time users accessing the web front end.

Memory

Replicator Basic and Standard editions require at least 1.25 GB of available memory.

 

Replicator Enterprise Edition requires at least 1.5 GB of available memory.

 

Additionally, ensure there is approximately 10 times the size of the largest file you expect to replicate in available memory.

 

For example, if you are using Replicator Standard Edition and expect to replicate files that are 25 MB and smaller, then you should have 1.5 GB (1.25 + 10 x 0.025) of available memory for Replicator.

Disk Space

At least 500 MB of free disk space in the %TEMP% folder of the server where Replicator is installed.

 

At least 20 GB of free disk space in a shared network folder. This is for your Replicator Data Folders. This number is a rough guideline and is affected by how frequently changes occur in your SharePoint environment, how often packages are cleared, and several other Replicator configuration settings.

 

At least 4 GB of free disk space in SQL Server is required where the SharePoint configuration database is stored.

Software Requirements

Component

Requirement

Operating System

Any of:

·Windows Server 2019

·Windows Server 2016

·Windows Server 2012 R2

·Windows Server 2012

·Windows Server 2008 R2

·Windows Server 2008

·Windows Server 2003 SP1

 

If you are using Replicator on Windows Server 2003, then you must also install the following from http://download.microsoft.com:

·Background Intelligent Transfer Service (BITS) 2.5 or higher

·.NET Framework 3.5 or higher

SharePoint

Any of:

·Microsoft Office SharePoint Server 2019

·Microsoft Office SharePoint Server 2016

·Microsoft SharePoint Server 2013

·Microsoft SharePoint Foundation 2013

·Microsoft SharePoint Server 2010

·Microsoft SharePoint Foundation 2010

·Windows SharePoint Services 3.0

·Microsoft Office SharePoint Server 2007

 

Replicator does not support SharePoint standalone installations. The SharePoint standalone installation option includes a built-in database and restricts your SharePoint environment.

 

Replicator does not support the use of the built-in Network Service account as your SharePoint farm application pool account.

Database

Any of:

·SQL Server 2017

·SQL Server 2016

·SQL Server 2014

·SQL Server 2012

·SQL Server 2008 R2

·SQL Server 2008

·SQL Server 2005

 

Replicator does not support any database installed automatically by the SharePoint installer. Refer to Migrate content databases from Windows Internal Database to an instance of SQL Server for more information.

Ports

Ports 7357 and 7358 must be available for Replicator interprocess communication on the server where you install Replicator. If these ports are not available, then contact Metalogix Support for further instructions.

Windows PowerShell

If you want to run Replicator administration commands in Windows PowerShell, then you must install PowerShell before installing Replicator.

Remote Differential Compression

To use Differencing Compression with Replicator, you must install the Remote Differential compression feature on servers in each farm where Replicator is installed.

 

In Windows Server 2012, 2012 R2, 2008 R2, and 2008, this can be done from Server Manager.

 

On Windows Server 2003, you must download and install the feature from http://download.microsoft.com.

Access Requirements

Component

Requirement

Installing User

The Replicator installer must be run under a user account that is:

·A member of the Local Administrators group on each server in the farm that replicator functionality will be deployed to.

·A member of the Central Administration Application Pool. This is usually the Farm Admin account.

·"Db_owner" of the SharePoint Config DB in SQL Server, as well as a "dbcreator", "securityadmin", and member of the "public" role.
 

This applies to all servers in the farm running either the Windows SharePoint Services Web Application service, or the Microsoft SharePoint Foundation Web Application service.

Application Pool Accounts

If you have different application pool accounts for Central Administration and your web applications, then add the user to the SharePoint configuration database and grant them the "public" role. This is done because permissions are copied from the SharePoint configuration to the replicator databases.

 

Although this change can be done manually after installing Replicator, it is much simpler to grant these permissions prior to installation.

Server Access

HTTP or HTTPS access to all replication servers, without proxies requiring a separate login.

SharePoint Access

Access to the Windows SharePoint Services SQL servers, via NTLM or Kerberos.

Firewalls

If there is a firewall separating the farms, then you must configure the firewall to allow servers in one farm to access a web front end in the other farm.

Activation

Replicator activates your license key during its installation by contacting a Quest server. Replicator will periodically refresh the activation as it runs.

 

For customers without an Internet connection or who want to review the information that is being sent to Quest, offline activation is available. Installations using offline activation must be manually refreshed every 365 days. For more information, see the ActivateOffline command in the Replicator Command Line Reference Guide.

Replicator Service

The user you run replication services under must be a Central Administration Application Pool user.

Server Manager

IIS 6 Metabase Compatibility Server Role must be enabled in Server Manager so that Replicator Configuration wizard can check prerequisites.

Availability Requirements

Component

Requirement

IIS and SharePoint

Replicator deploys solutions to the Central Administration and Web Front-end servers and must restart IIS to do this. A brief service outage will occur on these servers during the deployment process.

 

Related Documents