How to Upgrade or Reinstall an Application Module to Protect Previously Unprotected Features

Follow
Summary

This Knowledgebase article describes how to upgrade a Neverfail Application Module, and how to reinstall a Neverfail Application Module to protect previously unprotected application components. The procedures described in this article require Administrator-level access to both servers in the Neverfail pair, and can be performed with no application downtime.

More Information

This process should be used in the following situations:

  1. When Neverfail releases a new version of an Application Module (AM) or Application Module Extension (AMX) and you wish to upgrade to this new version.
  2. When you wish to reconfigure the service protection provided by an Application Module or Application Module Extension to include additional components, or to exclude one or more components that are currently protected.

Procedure

In the procedures described below:

  • 'AM' refers to a Neverfail Application Module.
  • 'AMX' refers to a Neverfail Application Module eXtension.
  • 'AM(X)' may refer to a Neverfail Application Module, or an Application Module eXtension, or both.

Component Protection

Application Module install scripts use the status of application services to determine which components require protection, based on two simple rules, when the AM(X) script is run by the Setup.exe program:

  • Is the service Startup Type 'Automatic'?
  • Is the service Status 'Started'?

If either of these criteria is evaluated as TRUE for any service specified by the AM(X) script, then the components for that service will be protected.

Protection includes:

  • Adding the service to the start and stop scripts.
  • Adding the service to the monitoring configuration.
  • Setting appropriate file and registry filters.

Services that are disabled, stopped, or not present, will not be protected by the AM(X). To protect a previously unprotected service, or remove protection for a currently protected service, you will need to uninstall the AM(X) and install it again. This process ensures that the protection criteria are completely re-evaluated; allowing an Administrator to install or enable application components after Neverfail Heartbeat has been implemented and then reinstalls the AM(X) to protect these new components.

Module Dependency Checking

Neverfail Heartbeat evaluates dependencies on a 'first in, last out' basis, so the order in which components are installed is important. Component dependencies are displayed on the 'Select Components to Uninstall' screen of the Setup program. Selecting a component on this screen will automatically force all modules below it to be selected for uninstall as well. Removing a component that has no items below it, will not cause any other module to be removed.

Note: In the event that Neverfail Heartbeat has been upgraded using a Service Pack Upgrade, the last component listed will be the Service Pack Upgrade. You should first uninstall the desired AM(X) and reinstall the Service Pack (using the specific version Upgrade Knowledgebase article) and then reinstall the new AM(X) to address this situation.

Examples

  1. Exchange 2003 Example - Enabling and protecting the Exchange IMAP4 service (where this is a previously unused and unprotected service).

    By default, Exchange 2003 is installed with the IMAP4 service disabled. If the Neverfail for Exchange Application Module was installed with the service in this state then the service would not be protected. If Exchange client access requirements change, and an Administrator wants to enable clients to use this service, then the Administrator will need to:

    1. Uninstall the Exchange Application Module on Primary and Secondary Servers.
    2. Set the IMAP4 service to 'Automatic' on the Primary and Secondary Servers.
    3. Reinstall the Exchange Application Module on the Primary and Secondary Servers.
  2. SQL Server Example - Installing a new SQL Server instance.

    To install a new instance of SQL Server, an Administrator would follow this procedure:

    1. Uninstall the SQL Server Application Module on Primary and Secondary Servers.
    2. Install the new instance on the Primary and Secondary Servers.
    3. Reinstall the SQL Server Application Module on the Primary and Secondary Servers.
  3. Module Dependency Example - Reinstalling the Exchange Application Module with the Symantec Mail Monitor for Exchange AMX.

    If your Exchange Application Module needs to be reinstalled and you have an AMX installed (for example, Symantec MailMonitor for Exchange), then you will need to uninstall both components:

    1. Select the Exchange Application Module for uninstall on both Primary and Secondary Servers. This will automatically select the Symantec AMX for uninstall as well.
    2. Reconfigure the Exchange services as required.
    3. Add the AM(X) scripts to be installed in the following order: Exchange, and then Symantec.

Script Extensions

During the install procedure you will be asked to locate the module install scripts. The 'Browse' dialogue will allow you to select from a list of various file types [ *.amx | *.vbs | *.nfs | *.* ].

For Application Modules that ship with the Neverfail Heartbeat kit:

  • Exchange
  • SQL Server
  • File Server

The scripts will have a .vbs extension, and can be found in the extracted Neverfail Heartbeat Kit.

All other Application Modules or AM(X)s that are downloaded from the appropriate product area of the Neverfail Partner Extranet, as individual packages, will have the .amx extension.

Please make sure you have all required packages available on the Primary and Secondary servers before beginning this process. If you are reinstalling one of the AMs shipped with the Heartbeat core, you will need to make sure you have the Neverfail Heartbeat kit on the server pair.

Uninstall / Install Procedure

Preparation

NOTE: This procedure can be performed with no application downtime.

  1. Launch the Neverfail Heartbeat Management Client.
  2. Check the current role of the Primary server. If the Primary server is currently passive, perform a switchover so that the Primary server becomes active.
  3. Shut down Neverfail Heartbeat, choosing to leave the protected applications running.

The following procedures require Administrator access to both servers.

Uninstalling AM(X)s

On the Primary active server, do the following:

  1. To use the installed version of the setup.exe, use Start -> All Programs -> Neverfail -> Uninstall or Modify .

    Note: You should always use the latest version of Setup.exe.
  2. Click Next to pass through the License Configuration screen (unless you need to amend the licensing details, in which case you should do so now).
  3. Select 'Uninstall Selected Components' and then press Next .
  4. Select the components to be uninstalled.
  5. Press Next and then Next again.
  6. Review the Report section for errors or warnings.
  7. Press Next and then Finish to complete the uninstall.

On the Secondary Passive server, do the following:

  1. Disconnect or disable the Public Network Connection.
  2. To use the installed version of the setup.exe, use Start -> All Programs -> Neverfail -> Uninstall or Modify .

    Note: You should always use the latest version of Setup.exe.
  3. Click Next to pass through the License Configuration screen (unless you need to amend the licensing details, in which case you should do so now).
  4. Select 'Uninstall Selected Components' and then press Next .
  5. Select the components to be uninstalled.
  6. Press Next and then Next again.
  7. Review the Report section for errors or warnings.
  8. Press Next and then Finish to complete the uninstall.
  9. Right-click the 'Neverfail System Tray' icon.
  10. Select 'Configure Server' wizard.
  11. Select the 'Machine' tab
  12. Set the 'Identity' to 'Secondary'
  13. Set the 'Role' to 'Passive'
  14. Click Finish to save changes and dismiss the wizard.
  15. Reconnect or Enable the Public Network Connection.

When the AM(X)s have been removed from BOTH servers, reconfigure the application on the Primary and Secondary servers. This will involve one or more of the following actions:

  • Installing the additional application components you wish to protect.
  • Uninstalling the application components you no longer wish to protect.
  • Enabling protection on a service by making sure that the 'Startup Type' is set to 'Automatic'.
  • Disabling protection for a service by setting the 'Startup Type' to 'Disabled' or 'Manual' and ensuring the 'Status' is 'Stopped'. Now proceed to the next section, 'Installing AM(X)s'.

Installing AM(X)s

On the Primary active server:

  1. From the folder \R2\bin under the Neverfail program directory, launch Setup.exe.

    Note: You should always use the latest version of Setup.exe.
  2. Select 'Install AM(X)' press Next .
  3. Press Add and then Browse to select the path to the AM(X) script. Select the .amx or .vbs script and press OK . Repeat this for all required AMs or AMXs
  4. Press Next when all scripts have been added.
  5. Review the 'Installation Summary' report and press Next .
  6. Review the 'Pre-Install Check Report'.
  7. If there are any failures or warnings resolve the issue and then click Back .
  8. Press Next to run the pre-install checks again.
  9. If there are no errors, the 'Next' button will be enabled.
  10. Press Next and then Finish to complete the installation.

On the Secondary Passive server:

  1. From the folder \R2\bin under the Neverfail program directory, launch Setup.exe.

    Note: You should always use the latest version of Setup.exe.
  2. Select 'Install AM(X)' press Next .
  3. Press Add and then Browse to select the path to the AM(X) script. Select the .amx or .vbs script and press OK . Repeat this for all required AMs or AMXs
  4. Press Next when all scripts have been added.
  5. Review the 'Installation Summary' report and press Next .
  6. Review the 'Pre-Install Check Report'.
  7. If there are any failures or warnings resolve the issue and then click Back .
  8. Press Next to run the pre-install checks again.
  9. If there are no errors, the 'Next' button will be enabled.
  10. Press Next and then Finish to complete the installation.

Confirm Upgrade

  1. Restart Neverfail Heartbeat on the Primary and Secondary servers.
  2. Start the Management Client to ensure that the Full System Check has started.
  3. If the configuration changes have resulted in new data locations being protected then review the protected file set using the 'Data' tab.
  4. If the configuration changes have resulted in new services being protected: - Launch the 'Configure Monitoring' ( Start -> All Programs -> Neverfail ), select the appropriate module from the drop-down menu and review the list of protected services. View the start.bat file (on both servers) to make sure that the appropriate services are present or absent, depending upon the configuration change.
  5. When the Full System Check has completed, perform a switchover and check that the configuration changes have been applied to the Secondary server as well.

Applies To

Neverfail Heartbeat v5.2.x and Earlier


Related Information

None

KBID-462

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.