How to Upgrade to Neverfail Replicator V5.2.2

Follow

Summary

This Knowledgebase article describes the steps to take when upgrading to Neverfail Replicator V5.2.2.


More Information

The upgrade to V5.2.2 can be applied to the following versions of Neverfail Replicator:

  • 5.2.1

Note: This procedure does NOT apply to upgrading to Neverfail Heartbeat V5.2.2. For information about how to upgrade to Neverfail Heartbeat V5.2.2, please see Knowledgebase article #1371 - 'How to Upgrade to Neverfail Heartbeat V5.2.2'.

Upgrading to Neverfail Replicator V5.2.2

During some parts of the procedure, the passive server will need to be isolated from the network by physically disconnecting the principal (public) NIC. For this reason, the procedure described below should not be attempted unless:

  1. You have access to the passive server via a local console (i.e. via a dedicated keyboard and mouse attached to the server, or via a KVM switch or similar device attached to the server); OR
  2. You can obtain Terminal Services/Remote Desktop access to the passive server via one of its channel NICs. This may be possible if the channel connection is via a LAN rather than via crossover cables.

Procedure

  1. On a remote client PC, or the active server, as appropriate, download the following packages from the 'Products / Downloads' area of the Neverfail Partner Extranet:

    Neverfail Replicator V5.2.2 – Extract the contents to a folder and copy this folder (referred to below as the 'update kit' folder) to both of the servers in your Neverfail pair, and to any remote client PCs running the Neverfail Heartbeat Management Client. The Service Pack is contained in this zip file and is called "ServicePack.nfs".
  2. Shutdown Neverfail Replicator.
  3. Close all remaining instances of the 'Neverfail Server Pairs Overview' window, and any other Neverfail management interfaces.

    Note: Ensure that the SCOPE MMC Snapin, if present, is closed prior to proceeding.
  4. Isolate the passive server from the network, by physically disconnecting the principal (public) NIC.
  5. On the active Server:
    1. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    2. Select the option 'Install Service Pack'.
    3. If prompted, enter a corresponding license.
    4. Enter the path to the "ServicePack.nfs" file in the update kit folder.
    5. Follow the on screen instructions to complete the update.
  6. On the passive server:
    1. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    2. Select the option 'Install Service Pack'.
    3. If prompted, enter a corresponding license.
    4. Enter the path to the "ServicePack.nfs" file in the update kit folder.
    5. Follow the on screen instructions to complete the update.
  7. On any remote client PCs:
    1. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    2. Select the option 'Install Service Pack'.
    3. Enter the path to the "ServicePack.nfs" file in the update kit folder.
    4. Follow the on screen instructions to complete the update.
  8. On both the active and passive server, open the TCP/IP properties for the channel NIC/s and check that the Neverfail Packet Filter Driver is not installed on this network card (cleared). The Neverfail Packet Filter Driver should not operate on the Neverfail Channel NIC/s but should be installed (selected) on any principal (public) network connections. If the Neverfail Packet Filter Driver is selected on the Neverfail Channel NIC/s, please uncheck it before proceeding to the next step.
  9. Run the Neverfail Server Configuration wizard utility on both servers and check that the identities, IP addresses, and roles are correct. If necessary, enter the correct license key on the Secondary server.
  10. Reconnect the passive server to the network by reconnecting the principal (public) NIC. Do not start Replicator on the passive server yet.
  11. Start Neverfail Replicator on the active server.
  12. Start Neverfail Replicator on the passive server and allow the servers to connect.
  13. On a remote client PC, or the active server, as appropriate, use the Neverfail Heartbeat Management Client to check that the Neverfail Channel is connected and that a Full System Check is in progress.

Note: The Management Client version must be the same as the version running on the Neverfail Replicator pair you wish to connect to.


Applies To

Neverfail Replicator V5.2.1


Related Information

None

KBID-1372

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.