Upgrading PeerLink File Collaboration

To v3.6 and newer

Tech Brief #

114

Revision

008

Last Updated

27 Jul 2017

IMPORTANT NOTE: Starting with File Collaboration v3.6, the PeerLink Hub and PeerLink Agent have been renamed to the Peer Management Center (PMC) and Peer Agent. The interface of the PMC is basically the same as the PeerLink Hub but you will no longer see references to "PeerLink" or the "Hub".

To upgrade the environment, please download the new Peer Management Center (PMC) installer to your Hub/PMC server. If using Windows Failover Cluster, please download the new clustered Agent installer to all cluster nodes in the environment. For all non-clustered Agents, please download the new non-clustered Agent installer. Direct download links are provided by the Peer Software team.

IMPORTANT NOTE: The same Agent installer CANNOT BE USED for Agents attached to Windows Failover Clusters and non-clustered Agents. There is a cluster installer for the clustered Agents, and a non-cluster installer for the non-clustered Agents.
IMPORTANT NOTE: When upgrading Agents attached to Windows Failover Clusters, the centralized upgrade mechanism from within the Peer Management Center CANNOT BE USED. It can still be used on all non-clustered Agents in the environment.

The remaining steps are broken down into four sections:

  • Backing up existing configurations
  • Upgrading the Peer Management Center / PeerLink Hub
  • Upgrading non-Clustered Agents
  • Upgrading Agents that are attached to a Windows Failover Cluster

Backing up existing configurations

The upgrade installer for the Peer Management Center automatically retains previous configuration information and logs. However, if you would like an additional backup of the configuration, please do the following:

  1. From within the existing Peer Management Center Client (or PeerLink Hub Client if earlier than v3.6), stop all running File Collaboration Jobs and close the Client.
  2. Open the Services manager (services.msc) and stop all services that reference "Peer Management Center" (such as "Peer Management Center Service") or "PeerLink" (such as the "PeerLink Hub Service").
  3. Navigate to the installation directory of the PMC or Hub (typically C:\Program Files\Peer Software\Peer Management Center --or-- C:\Program Files\Peer Software\PeerLink), then into subfolder Hub\workspace.
  4. Select the dbjobs, and prefs folders along with any files that end with .ini. Copy all of these items to a backup location (such as your Desktop).
    NOTE: Before backing up the db folder, be sure to check the size of this folder. If it's more than 1 GB in size, we recommend NOT backing up the filecollaboration subfolder within the db folder.

Upgrading the Peer Management Center / PeerLink Hub

  1. From within the existing Peer Management Center Client (or PeerLink Hub Client if earlier than v3.6), stop all running File Collaboration Jobs and close the Client.
  2. Run the new Peer Management Center Installer. This installer will automatically remove the old version of the PMC or PeerLink Hub. If prompted during the uninstall process, DO NOT check the option to "Delete all existing session and job data from disk".
  3. Once the install is complete, open the Peer Management Center Client and if prompted, install any upgraded licenses.
  4. All Agents should say that an upgrade is required.
  5. Upgrade all Agents as noted below.
  6. Once all Agents are upgraded and have reconnected, restart the appropriate File Collaboration Jobs.

Upgrading non-Clustered Agents

If you will be upgrading connected Agents through the Peer Management Center, please follow these steps:

  1. In the Agent Summary panel of the Peer Management Center Client, select all connected Agents that are listed as requiring software updates. If you have more than 20 Agents, we suggest selecting 20 Agents at a time.
  2. Right-click and select Install Software Updates. This process will push new software to each Agent, stop the Agent, install the update, and then restart the Agent. This process can take several minutes depending on your connection speed and on the version of the Agent from which you are upgrading.
  3. When each Agent reconnects, it should no longer be marked as requiring a software update.

If you will be manually upgrading the Agents, please follow these steps:

  1. Remote Desktop to one Windows Server where the Agent is installed.
  2. Run the new Agent installer. The new installer will automatically uninstall the old version of the Agent. When prompted by the installer, make sure that the Broker settings are correct and match those of the prior install.
  3. Once the install process is complete, check the Peer Management Center Client to ensure that the Agent has successfully reconnected and no longer requires a software update.
  4. Repeat for all other Agents.

Upgrading Agents that are attached to a Windows Failover Cluster

IMPORTANT NOTE: These steps are for upgrading existing Agents in Windows Failover Cluster environments. They are NOT designed for adding new Agents. Contact support@peersoftware.com for more information on how to attach a new Agent to a Windows Failover Cluster.

To upgrade the clustered Agents:

  1. Remote Desktop to one Windows Server Cluster Node where the Agent is installed.
  2. Within the Windows Failover Cluster Manager, disable the Agent service that is attached to each clustered file server role.
  3. Run the new clustered Agent installer. The new installer will automatically uninstall the old version of the Agent. When prompted by the installer, make sure that the Broker settings are correct and match those of the prior install.
  4. When asked by the installer for the number of clustered file server roles, set it to the total number of roles that will run with an attached Agent across all nodes in this particular cluster. This number MUST MATCH that of the previous install.
  5. When prompted for each clustered file server role, enter in the exact file server role name and the Agent working directory. The working directory will point to a location on a cluster disk attached to that clustered file server role. These settings MUST MATCH those of the previous install.
  6. Repeat for all other cluster nodes where the Agent is installed.
  7. Once all nodes have been upgraded, manually restart the Agent services attached to each clustered file server role from within the Windows Failover Cluster Manager.