How to Upgrade a Neverfail Server and Network Hardware

Follow

Summary

This Knowledgebase article provides information on how to perform a hardware upgrade on a Neverfail server or network hardware.


More Information

Making hardware changes to a server or network hardware should be well thought out and planned to minimize down time for an organization.  Assessing network changes is especially important when changes are planned for routers and switches that are used in routing channel traffic in a Neverfail WAN environment.

Procedure

If you need to change the hardware in your server, Neverfail provides a simple method of avoiding downtime of the protected application.  In table 1, it is assumed that the Primary server is the one being upgraded.

Note: Please see Knowledgebase article #120 - 'How to Remove or Change a NIC in the Primary or Secondary Server Without Causing Problems in the Continue Operations of the Neverfail Packet Filter Driver', if replacing Network Interface cards.  The following stages can avoid downtime of the protected application:

Server Step Instruction
Primary 1. Ensure the Primary server is passive. Perform a switch so that the server is passive and allow the pair to synchronize.
2. Shutdown Neverfail via the Management Client selecting the option ‘Shutdown Neverfail Heartbeat, but leave the protected applications running’.
3. Set Neverfail R2 service to manual via the SCM.
4. Shutdown Windows as normal via ‘Start Menu’.
5. Perform hardware upgrade or repair.
6. Start Server and log into Windows as normal.
7. Allow Plug and Play to install drivers or manually install them as necessary. Perform any restarts required.
8. Log back into Windows and set the Neverfail R2 service back to automatic.
Note: If running Neverfail Heartbeat v5.5.1 and earlier, you may need to generate a new Neverfail license key depending on what hardware has been changed.
Both 9. Start Neverfail on both servers and allow synchronizing.
Secondary 10. Once synchronized perform a switch back if required to the primary server.
Both 11. Test functionality as necessary.

Table 1 - Primary Server Upgrade

Server Step Instruction
Primary 1. Via the Management Client, ensure that the Primary server is active.
2. Shutdown Neverfail via the Management Client selecting the option ‘Shutdown Neverfail Heartbeat, but leave the protected applications running’.
Secondary 3. Set Neverfail R2 service to manual via the SCM
4. Shutdown Windows as normal via ‘Start Menu’.
5. Perform hardware upgrade or repair.
6. Start Server and log into Windows as normal.
7. Allow Plug and Play to install drivers or manually install them as necessary. Perform any restarts required.
8. Log back into Windows and set the Neverfail R2 service back to automatic.
Both 9. Start Neverfail on both servers and allow synchronizing.
10 Test functionality as necessary.

Table 2 - Secondary Server Upgrade

Network Hardware

Switches and Hubs

Neverfail should not require any additional steps to detect network hardware change unless these changes affect the TCP/IP settings across the connection of either server.

Note: See Server Hardware above and Knowledgebase article #120 - 'How to Remove or Change a NIC in the Primary or Secondary Server Without Causing Problems in the Continued Operations of the Neverfail Packet Filter Driver' for NIC instructions.

Neverfail Heartbeat in a Local Area Network (LAN)

Please be aware that if changes are made to routers or switches that affect the channel communications, then Neverfail Heartbeat must be shutdown.

Any changes made to IP addresses used for the channel and principal (public) connection must be reflected in the Neverfail Heartbeat configuration. Changes must be made using the ‘Server Configuration’ wizard while Neverfail Heartbeat is shutdown.

Server Step Instruction
Remote Management Client / Active Server 1. Shutdown Neverfail Heartbeat via the Management Client on both servers selecting the option ‘Shutdown Neverfail Heartbeat, but leave the protected applications running’.
Network 2. Carry out the network upgrade or repair.
Both 3. From a command line, ping the NF Channel IP address to make sure that the servers are visible to each other after the changes. This can be performed from Primary to Secondary or vice versa.
4. Restart Neverfail on the Primary and then the Secondary server.


Applies To

All Versions


Related Information

None

KBID-152

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.