Replicator 7.4 - Upgrade Guide

Introduction

The last few versions of Replicator for SharePoint introduced a number of future-ready features, including:

oA redesigned, and more open package file format for easy and immediate log file reading and support.

oThe removal of unused features.

oAdded stability with new adaptive mode technology and communication protocols.

oThe groundwork for enhanced synchronization and monitoring.

It was an important upgrade for users running earlier editions of Replicator, and upgrading was highly recommended so that users could make use of the new open package format. Now, with the Replicator 7.4 June 2017 release (7.4.1706.x), the new package file format comes standard, and the legacy version has been deprecated. It is necessary that all farm nodes be upgraded to the Replicator May 2017 release (7.3.1705.x) in order for replication to work with future versions of Replicator.

This document discusses two ways of upgrading to version 7.4.1706.x and later from previous versions of Replicator, namely:
 

§Upgrading all nodes at once

§Performing a rolling upgrade

Upgrading Nodes at Once

The simplest way to ensure a smooth upgrade to Replicator version 7.4.1706.x or later is to upgrade all nodes at the same time. This ensures that all nodes are able to communicate with each other through the utilization of the new XML package format.

If all nodes are capable of being upgraded at the same time, perform the following steps:

1.Before starting the upgrade, when possible, it is best practice to verify that packages in Monitor Replication have been completed.

2.Pause inbound and outbound package processing from the Configure Web Application page for all nodes. This is done by selecting the "Yes" option, as shown below, and then clicking "OK" to save changes.

3.Install Replicator version 7.4.1706.x or later over the existing version on all nodes. Refer to the In-Place Upgrade of Replicator section of the Metalogix Advanced Installation Guide for details on this method of upgrading Replicator.

4.Un-pause inbound and outbound package processing on all nodes by selecting the "No" option, and then clicking "OK" to save changes.

Replicator will now be able to replicate packages with future versions of the product.

Performing a Rolling Upgrade

It is not always possible to upgrade all nodes at the same time. If this is the case, a rolling upgrade can be performed, whereby nodes are upgraded as time allows. Throughout the course of a rolling upgrade, there will be mixed versions of Replicator working alongside nodes that have already been upgraded to Replicator version 7.3.1705.x (or later).

To perform a rolling upgrade:

1.Before starting the upgrade, when possible, it is best practice to verify that packages in Monitor Replication have been completed.

2.Pause inbound and outbound package processing from the Configure Web Application page for all nodes that are "generating" packages for replication. This is done by selecting the "Yes" option, as shown below, and then clicking "OK" to save changes.

3.Ensure that all nodes are running Replicator version 7.2 or later. If they are not, Replicator 7.1, build 7.1.11208.176 or later should now be installed over the existing version on all nodes. Then perform the 7.2 upgrade process.
Refer to the In-Place Upgrade of Replicator section of the Metalogix Advanced Installation Guide for details on this method of upgrading Replicator.

4.Install Replicator version 7.3.1705.x on all nodes.
 
Once the newest version of Replicator has been installed on all nodes, package processing can be re-enabled by selecting the "No" option shown in the image above, and then clicking "OK" to save changes.

 
The Replicator 7.4 June 2017 release (7.4.1706.x) roll-out can now begin as time allows.