This article describes a known issue with Neverfail Heartbeat Version 4.6
Uninstalling any Neverfail Heartbeat Application Module (AM) will result in the Secondary Passive (S / -) changing its identity and role to Primary Active (P / A). In its current state the Server is not visible on the network with the Public IP address. Before an Application Module can be installed on this server, or the Heartbeat service can be started the server's configuration must be changed back to Secondary Passive.
To resolve the configuration issue you must manually reconfigure the Secondary server as Secondary Passive (see Changing the Configuration)
- Server A is Primary Active and the Neverfail for SQL Server Application Module is uninstalled.
- Server B's identity will change from Secondary Passive to Primary Active.
Heartbeat must not be started with this configuration, Attempting to do so will result in:
- Two active servers attempting to connect, Heartbeat will exit during the handshake.
- IP and name conflicts.
Attempting to launch setup in this configuration will result in the license check failing on the hardware ID because the server does not contain the licensed hardware for the Primary server.
Changing the Configuration
On the Secondary Server (Server B in the example)
i. Check the NFServerR2 service is in a stopped state via the Windows Service Control Manager.
i. Go to Start->Programs->Neverfail->Configure Server (If the NFServerR2 service is running the Configure Server option will be greyed out)
ii. Select Machine Tab and set the Identity as Secondary and Role as Passive
iii. Click Finish