How to Restart the Primary (active) Server

Follow

Summary

This Knowledgebase article provides information on how to restart a Primary (active) server running Neverfail Heartbeat.


More Information

When restarting a server running Neverfail Heartbeat, it is important to follow the Neverfail recommended procedure to prevent an 'Unclean' shutdown of Neverfail Heartbeat, which may result in some data loss.

The following procedure assumes that the Neverfail Heartbeat server pair is running with the Primary server as active and the Secondary server as passive.

Procedure

Neverfail Heartbeat v6.2 and Later

To restart the Primary (active) server, follow the steps below:

  1. Launch the Neverfail Heartbeat Management Client, by right-clicking the Neverfail Heartbeat system tray icon and selecting Manage Server , or by selecting the same option from Start > All Programs > Neverfail .
  2. Select the server pair you wish to manage and click Open .
  3. On the Server: Summary tab, check that the File System Status and Registry Status are both shown as 'Synchronized', and then click Shutdown .
  4. At this point, select the both the 'Primary' and 'Secondary' server option and 'Do not stop protected applications'. This will leave the application(s) running on the active server as Neverfail Heartbeat exits on both servers.  If you would like to troubleshoot the server with Neverfail Heartbeat and the protected application(s) offline, you should continue to step 5, and later the instructions below to restore default Neverfail Heartbeat startup settings. If not please skip the next step and continue to step 6.
  5. Set the 'NFServerR2' service to manual, and restart the server. This will prevent Neverfail Heartbeat , and the protected applications, from starting as the server boots. Continue to step 6.
  6. Restart both the Primary and Secondary servers. If you followed step 5 above, continue to Section 2, if not continue to step 7 below.

    Note: On Windows Server 2008, if any applications are running, you will be prompted to shutdown the application before shutting down or restarting Windows Server 2008.
  7. The servers will restart, reconnect, and perform a Full System Check. This may take some time to complete depending on the amount of protected data and bandwidth available. If this does not happen, you may need to contact your Neverfail Support representative for further instructions.

To restore the default Neverfail Heartbeat startup settings:

Note: All protected applications will still be unavailable at this point. Troubleshooting can now be initiated with Neverfail Heartbeat and the protected applications offline. Once finished follow the steps below to restore default settings.

  1. Check that the server role on the Primary (active) server is correctly set. Note: To do this, the Neverfail Heartbeat service must not be running.
  2. Right-click the Neverfail Heartbeat system tray icon and select Server Configuration wizard.
  3. From the Machine tab, check that the server is set to 'active'. If not, this should be changed to 'active'. This should already be the case if the server was active before stopping Neverfail Heartbeat. However, if the service failed to stop cleanly, it may be set to passive.
  4. Click Finish .
  5. Check that the server role on the Secondary (passive) server is correctly set. Note: To do this, the Neverfail Heartbeat service must not be running.
  6. Right-click the Neverfail Heartbeat system tray icon and select Server Configuration wizard.
  7. From the Machine tab, check the server is set to passive. If not this should be changed to passive. This should already be the case if the server was passive before stopping Neverfail Heartbeat .
  8. Click Finish .
  9. On the Primary (active) server, start Neverfail Heartbeat . Right-click the Neverfail Heartbeat system tray icon and select Neverfail Heartbeat . Ensure that the application services have started on the Primary (active) server. The services that are protected by Neverfail Heartbeat are listed in the START.BAT file in the Neverfail directory C:\Program Files\Neverfail\r2\scripts .
  10. On the Secondary (passive) server, start Neverfail Heartbeat . Right-click the Neverfail Heartbeat system tray icon and select Start Neverfail Heartbeat . Note: Application services should NOT start on this server, as it is passive, and not servicing client requests. Ensure that all protected services are stopped. The Services that are protected by Neverfail Heartbeat are listed in the START.BAT file in the Neverfail directory C:\Program Files\Neverfail\r2\scripts .
  11. Check using the Windows Services Management Console that the 'NFServerR2' service is set to 'Automatic' and 'Started' on both servers. If the service is not set to 'Automatic' set this now.
  12. Check that the servers have connected and started replication.
  13. Launch the Neverfail Heartbeat Management Client, by right-clicking the Neverfail Heartbeat system tray icon and selecting Manage Server , or by selecting the same option from Start > All Programs > Neverfail .
  14. Select the server pair you wish to manage and click Open .
  15. On the Server: Summary tab, check that the File System Status and Registry Status are both replicating and the direction is from Primary (active) server to the Secondary (passive) server. The Registry Status should quickly display as 'Synchronized'. The File System Status may take much longer depending on the amount of protected data.
  16. Logout of the Neverfail Heartbeat Management Client by selecting File > Exit and following the on-screen prompts.
  17. The server pair has now been restored to its default startup settings, and should be replicating normally. If this does not happen, you may need to contact your Neverfail Support representative for further instructions.

Neverfail Heartbeat v6.0 and Earlier

To restart the Primary (active) server, follow the steps below:

  1. Launch the Neverfail Heartbeat Management Client, by right-clicking the Neverfail system tray icon and selecting Manage Server , or by selecting the same option from Start > All Programs > Neverfail .
  2. Login at the prompt. Select the server pair you wish to manage and click Open .
  3. On the System > Status & Control tab, check that the File System Status and Registry Status are both shown as 'Synchronized', and then click Shutdown .
  4. At this point, select the option 'Exit Neverfail Heartbeat but leave the protected applications running'. This will leave the application(s) running on the active server as Neverfail Heartbeat exits on both servers.  If you would like to troubleshoot the server with Heartbeat and the protected application(s) offline, you should continue to step 5, and later the instructions below to restore default Heartbeat startup settings. If not please skip the next step and continue to step 6.
  5. Set the 'NFServerR2' service to manual, and restart the server. This will prevent Neverfail Heartbeat, and the protected applications, from starting as the server boots. Continue to step 6.
  6. Restart both the Primary and Secondary servers. If you followed step 5 above, continue to Section 2, if not continue to step 7 below.

    Note: On Windows Server 2008, if any applications are running, you will be prompted to shutdown the application before shutting down or restarting Windows Server 2008.
  7. The servers will restart, reconnect, and perform a Full System Check. This may take some time to complete depending on the amount of protected data and bandwidth available. If this does not happen, you may need to contact your Neverfail Support representative for further instructions.

To restore the default Heartbeat startup settings:

Note: All protected applications will still be unavailable at this point. Troubleshooting can now be initiated with Neverfail Heartbeat and the protected applications offline. Once finished follow the steps below to restore default settings.

  1. Check that the server role on the Primary (active) server is correctly set. Note: To do this, the Neverfail Heartbeat service must not be running.
  2. Right-click the 'Neverfail Heartbeat' system tray icon and select 'Server Configuration' wizard.
  3. From the Machine tab, check that the server is set to 'active'. If not, this should be changed to 'active'. This should already be the case if the server was active before stopping Neverfail Heartbeat. However, if the service failed to stop cleanly, it may be set to passive.
  4. Click Finish .
  5. Check that the server role on the Secondary (passive) server is correctly set. Note: To do this, the Neverfail Heartbeat service must not be running.
  6. Right-click the 'Neverfail Heartbeat' system tray icon and select 'Server Configuration' wizard.
  7. From the Machine tab, check the server is set to passive. If not this should be changed to passive. This should already be the case if the server was passive before stopping Neverfail Heartbeat.
  8. Click Finish .
  9. On the Primary (active) server, start Neverfail Heartbeat. Right-click the 'Neverfail' system tray icon and select 'Start Neverfail Heartbeat'. Ensure that the application services have started on the Primary (active) server. The services that are protected by Neverfail Heartbeat are listed in the START.BAT file in the Neverfail Heartbeat directory \neverfail\r2\scripts.
  10. On the Secondary (passive) server, start Neverfail Heartbeat. Right-click the 'Neverfail' system tray icon and select 'Start Neverfail Heartbeat'. Note: Application services should NOT start on this server, as it is passive, and not servicing client requests. Ensure that all protected services are stopped. The Services that are protected by Neverfail Heartbeat are listed in the START.BAT file in the Neverfail Heartbeat directory \neverfail\r2\scripts.
  11. Check using the Windows Services Management Console that the 'NFServerR2' service is set to 'Automatic' and 'Started' on both servers. If the service is not set to 'Automatic' set this now.
  12. Login to the server pair, and check that the servers have connected and started replication.
  13. Launch the Neverfail Heartbeat Management Client, by right-clicking the 'Neverfail' system tray icon and selecting 'Manage Server', or by selecting the same option from Start > All Programs > Neverfail .
  14. Login at the prompt. Select the server pair you wish to manage and click Open .
  15. On the System > Status & Control tab, check that the File System Status and Registry Status are both replicating and the direction is from Primary (active) server to the Secondary (passive) server. The Registry Status should quickly display as 'Synchronized'. The File System Status may take much longer depending on the amount of protected data.
  16. Logout of the Neverfail Management console by selecting Close and following the on-screen prompts.
  17. The server pair has now been restored to its default startup settings, and should be replicating normally. If this does not happen, you may need to contact your Neverfail Support representative for further instructions.


Applies To

All Versions


Related Information

None

KBID-444

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.