How to Upgrade to Neverfail Heartbeat V5.2.2

Follow

Summary

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


More Information

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

  • 4.6.1
  • 4.6.2
  • 4.7.0
  • 4.7.1
  • 5.0 (controlled release)
  • 5.0.1
  • 5.0.2
  • 5.0.3
  • 5.1.0
  • 5.1.1
  • 5.2.0

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

Upgrading to Neverfail V5.2.2 for SQL Server, Fileserver and Exchange

This article explains how to upgrade the following editions of Neverfail Heartbeat to V5.2.2:

  • Neverfail for Exchange
  • Neverfail for SQL Server
  • Neverfail for File Server
  • Neverfail for SharePoint

In the procedure described below, the term ‘Supported Application Module’ is used to refer to the Neverfail for Exchange, Neverfail for SQL Server or Neverfail for File Server Application Module, as appropriate to your edition of Neverfail Heartbeat.

Note: If your Neverfail Heartbeat deployment includes the Supported Application Module along with other Application Modules, please contact Neverfail Support. Otherwise, use the procedure described below.

The process of upgrading Neverfail for Exchange, Neverfail for SQL Server, or Neverfail for File Server to V5.2.2 takes place in 5 distinct phases:

  1. Saving user-configurable settings
  2. Uninstalling the existing Supported Application Module
  3. Upgrading Neverfail Heartbeat
  4. Installing the new version of the Supported Application Module
  5. Loading the user-configurable settings.

It is necessary to complete all five phases in the order given above.

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:

  • 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
  • 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 Heartbeat 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"
    • The version of the Supported Application Module appropriate for Neverfail Heartbeat V5.2.2 – Extract the contents to a folder and copy this folder (referred to below as the 'Supported Application Module' folder) to both of the servers in your Neverfail pair.
    • SQL Server Preserve Settings Utilities - Download U-PreserveSettingsUtilities-yyyy-mm-dd.zip and extract the content to <Neverfail>\R2\Bin on the active server. This zip file contains 4 utilities:
      • getpAllSettings.bat – used to save all Neverfail Heartbeat settings to a text file in human-readable format (default file: C:\NFConfigDump.txt).
      • getsFileFilters.bat – used to save a list of the Neverfail Heartbeat file filters to a text file in human-readable format (default file: C:\NFFileFilters.txt).
      • doSaveSettings.bat – used to save Neverfail Heartbeat user-configurable settings to an XML file (default file C:\NFSettings.xml).
      • doLoadSettings.bat – used to load Neverfail Heartbeat user-configurable settings from an XML file (default file C:\NFSettings.xml).
  2. These utilities can be used with Neverfail for Exchange and Neverfail for File server, as well as with Neverfail for SQL Server.

    Note: the doSaveSettings.bat/doLoadSettings.bat utilities will not save/load the Neverfail Heartbeat file filters or Neverfail Heartbeat Data Rollback Module shadow history. After the upgrade process is completed, manually add back any missing custom file filters, making reference to NFFileFilters.txt file.

    The Preserve Settings Utilities use the login and password from the current Windows session to authenticate with Neverfail Heartbeat. Any of the following accounts will have the correct privileges:

    1. The Domain Administrator for the domain hosting the Heartbeat server pair.
    2. The local Administrator account on the server pair.
    3. Any domain user who is a member of the 'Administrators' group on the server pair.

    If you choose the third option, an “Invalid Username/Password” error may be
    returned when the scripts are executed. To avoid this, you should first
    register the user account with Heartbeat, by issuing the 'addTrustedClient'
    command from the nfcmd utility on the active server:

    1.  Launch <Neverfail_installation_path>\R2\bin\nfclient.exe.

    2.  Provide the short username CN "common name" (i.e., "Besadmin" not
    Domain\Besadmin")under which you are logged in (the account needs
    to have local or domain administrator rights) and password.

    3.  Run the following command:

    addTrustedClient 127.0.0.1 <short username> administrator

    Note: Replace the <short username> string with the short username that will be treated as a trusted client.

    4.  Run the following command: bye.

    For example, to register user Besadmin on the local system, you would run the
    following command on the server where the Heartbeat service is running:

    addTrustedClient 127.0.0.1 Besadmin administrator

  3. On the active server (usually the Primary):
    1. From <Neverfail>\R2\Bin, run getpAllSettings.bat. Wait for the utility to finish executing, and then open C:\NFConfigDump.txt with a text editor and check that the file is not corrupted or empty. Rename C:\NFConfigDump.txt to C:\NFConfigDump_Before.txt
    2. From <Neverfail>\R2\Bin, run getsFileFilters.bat. Wait for the utility to finish executing, and then open C:\NFFileFilters.txt with a text editor and check that the file is not corrupted or empty. Verify that all of your current Neverfail Heartbeat File Filters are listed in the file.
    3. From <Neverfail>\R2\Bin, run doSaveSettings.bat. Wait for the utility to finish executing, and then open C:\NFSettings.xml using Internet Explorer, which should be able to render this file in human-readable format, in order to check that the file is not corrupted or empty. If your version of Explorer will not render the file, open it in notepad instead, taking care not to alter the file content in any way. Close the file when you have checked it.
  4. Shutdown Neverfail Heartbeat, selecting the option to 'Exit Neverfail Heartbeat but leave protected applications running'.
  5. 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.
  6. Isolate the passive server from the network, by physically disconnecting the principal (public) NIC.
  7. On the active Server:
    1. Set the Neverfail Server R2 service to Manual via the Windows Service Control Manager (SCM).
    2. Run 'Uninstall' from Start -> Programs -> Neverfail .
    3. Select the option 'Uninstall Selected Components'.
    4. Select the Supported Application Module and follow the on-screen instructions to complete the process.
    5. Reboot the server to complete the uninstall.
    6. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    7. Select the option 'Install Service Pack'.
    8. If prompted, enter a corresponding license.
    9. Enter the path to the "ServicePack.nfs" file in the update kit folder.
    10. Follow the on-screen instructions to complete the update.
    11. Once complete you will be prompted to restart the server – perform the restart.
  8. On the passive Server:
    1. Set the Neverfail Server R2 service to manual via the Windows Service Control Manager (SCM).
    2. Run 'Uninstall' from Start -> Programs -> Neverfail .
    3. Select the option 'Uninstall Selected Components'.
    4. Select the Supported Application Module and follow the on-screen instructions to complete the process.
    5. Reboot the server manually to complete the uninstall.
    6. Uninstalling an Application Module will usually make your Secondary passive server Primary and active. This is normal behavior. If this occurs, you should reconfigure the server’s identity and role using the 'Configure Server wizard', so that the server has identity = Secondary and Role = passive (see Knowledgebase article #460 - 'Removing an Application Module (AM) or Application Module eXtension (AMX) may cause Secondary passive to become Primary active' for more details). This should be done before proceeding to the next step. Once you have reconfigured the server as Secondary / passive, start the Neverfail Server R2 service using the SCM, and then stop it again. This operation will enable the Neverfail Heartbeat Packet Filter on the principal (public) NIC.
    7. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    8. Select the option 'Install Service Pack'.
    9. If prompted, enter a corresponding license.
    10. Enter the path to the "ServicePack.nfs" file in the update kit folder.
    11. Follow the on screen instructions to complete the update.
    12. Once complete you will be prompted to restart the server.

      Warning: At this point, you will have an upgraded version of Neverfail Heartbeat with no Supported Application Module installed. Do NOT attempt to start Neverfail Heartbeat until you have completed the remainder of the upgrade procedure.

      Note: Before installing the Supported Application Module, check that Neverfail Heartbeat is stopped on both servers, and that no Neverfail management tools are running.
  9. On the active server:
    1. Open the Windows Service Control Manager (SCM), and check that all Supported Application services with Startup Type set to ‘Automatic’ are running.
    2. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    3. Select the option 'Install AM'.
    4. On the "License Configuration" dialog click Next , or add a corresponding license if necessary.
    5. Enter the path to the "<Supported Application>.vbs" file in the Supported Application Module folder.
    6. Follow the on screen instructions to complete the update.
  10. On the passive server:
    1. Open the Windows Service Control Manager (SCM), and check that all Supported Application services have the Startup Type set to ‘Automatic’.
    2. Locate the update kit folder on the disk and run "Setup.exe" to start the install wizard.
    3. Select the option 'Install AM'.
    4. On the 'License Configuration' dialog click Next , or add a corresponding license if necessary.
    5. Enter the path to the "<Supported Application>.vbs" file in the Supported Application Module folder.
    6. Follow the on screen instructions to complete the update.
    7. After the installation process ends, stop all of the protected services using one of the following methods:
    • Manually, via the Windows Service Control Manager
    • From the Windows Command Prompt, by changing directory to <Neverfail>\R2\bin and running the <Neverfail>\R2\Scripts\<SupportedApplication>\Stop.bat script.

    Use the Windows SCM to double-check that all of the protected services are stopped and have Startup Type set to Manual.

  11. 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.
  12. 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.
  13. On both active and passive server, set the Neverfail Server R2 service to Automatic via the Windows Service Control Manager.
  14. 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.
  15. Reconnect the passive server to the network, by reconnecting the principal (public) NIC. Do NOT start Heartbeat on the passive server yet.
  16. On the active server:

    1. Start Neverfail Heartbeat.
    2. From <Neverfail>\R2\Bin, run doLoadSettings.bat. Wait for the utility to finish executing.
    3. On the active server, or a remote client, open the Neverfail Heartbeat Management Client. Navigate to Data > Configuration , and manually check the list of File Filters. Add back any missing custom file filters, making reference to NFFileFilters.txt. The new Application Module may set additional filters automatically; so you should not delete any filters.
    4. From <Neverfail>\R2\Bin, run getpAllSettings.bat. Wait for the utility to finish executing, and then open C:\NFConfigDump.txt with a text editor and check that the file is not corrupted or empty. Rename C:\NFConfigDump.txt to C:\NFConfigDump_After.txt
    5. Compare C:\NFConfigDump_Before.txt and C:\NFConfigDump_After.txt files, either manually or using the Windows ‘fc’ command or any equivalent tool. Investigate and resolve any differences in configuration between the initial state of Heartbeat prior to the upgrade, and the final state on completion of the upgrade.
  17. Start Neverfail Heartbeat on the passive server and allow the servers to connect. Heartbeat will automatically copy any configuration changes from the active server to the passive server.
  18. 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 Heartbeat pair you wish to connect to.


Applies To

As Indicated Above


Related Information

None

KBID-1371

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.