How to Replace a Windows 2003 Server

Follow

Summary

This Knowledgebase article provides the step-by-step procedure necessary to replace a Windows 2003 server.


More Information

Initial Assumptions

  • The Operating System is installed on the C:\ drive.
  • Neverfail is installed on the C:\ drive.
  • Neverfail is installed in a LAN environment.
  • The Secondary server will be replaced.
  • The replacement server meets the documented prerequisites for Neverfail installation (for example, ACPI compliance with the other servers)

    NOTE: See the Neverfail Heartbeat Installation Guide for more information about hardware requirements for Secondary and Tertiary servers.

Before You Begin

  1. Read this entire article before performing any steps.
  2. Identify the server that needs to be replaced. The identity of this server is referred to as TO_BE_REPLACED throughout in this document.
  3. Identify the Active server. The identity of this server is referred to as TO_BE_BACKEDUP throughout this document.
  4. Open the Neverfail Heartbeat Management Client, click Data and select the Configuration tab. Make a note (in a file or on a piece of paper) of all replication filters.

Procedure

On the Active Server:

    1. Shutdown Neverfail Heartbeat.
    2. Set the Neverfail Server R2 service to Manual using the Windows Service Control Manager.
    3. Write down the identity of this server.
    4. Open the Neverfail Heartbeat Configure Server wizard.
      1. Select the Machine tab.
      2. Change the Physical Hardware Identity of the server scheduled for replacement to TO_BE_REPLACED (defined above).

        WARNING ! Do not change the Server Identity in any situation other than this.

      3. Change the Current Role to Passive .

        Note: This step applies only for Neverfail Heartbeat v5.5.1 and Prior
      4. Click Finish .
    5. Perform a complete search of the C:\ drive for *.DMP and delete all existing .DMP files. Empty these files from the Recycle bin as well.
    6. Run NTBackup .
      1. Select the entire C:\ drive and any other directories on a different drive that include program files of the protected application(s).
      2. Clear (deselect) any directories that are already part of the replication set.
      3. Select System State .
      4. Select a local location for the backup file.
      5. After the backup is complete, run the Neverfail Heartbeat Configure Server wizard again.
      6. Select the Machine tab.
      7. Change Physical Hardware Identity to TO_BE_BACKEDUP (defined above).
      8. Change the Current Role to Active .
      9. Click Finish .
    7. In the task bar, right-click the Neverfail Heartbeat Server icon and select Start Neverfail Heartbeat .
    8. Log into the Neverfail Heartbeat Management Client. Select the option to Stop replication but leave the Protected Application running .
    9. Set the Neverfail Server R2 service to Automatic using the Windows Service Control Manager.

On the New Server (the Replacement):

  1. Copy the backup file from the Active server.
  2. Disconnect the Principal (Public) and Channel cables from the server.
  3. Run NTBackup .
    1. Navigate to Tools > Options .
    2. Select the Restore tab.
    3. Select Always replace files on my computer and click Apply .
    4. Select the Restore and Manage Media tab.
    5. Right-click File in the left hand pane and select Catalog File .
    6. Browse to and select the backup file that was copied from the Active server.
    7. Expand the tree under the cataloged file and select all the backed up data (such as C:\ drive, System state).
    8. Click Start Restore . A warning message is displayed. Click OK to dismiss the warning.
    9. Click OK to start the restore.
    10. Restart the server after the restore process is complete.
  4. Allow Plug and Play continue and restart the server if prompted.
  5. In the Properties window of each network card, verify that the IP address settings are correct and the Neverfail Heartbeat Packet Filter is enabled for the Principal (Public) network connection and disabled for all channel connections.
  6. On the Machine tab of the Neverfail Heartbeat Configure Server wizard, verify that the Identity and Active Server are configured correctly.
  7. On the Public tab of the Neverfail Heartbeat Configure Server wizard, verify that the Public IP is correct.
  8. Use the 'route print' command to check that all WAN routes are correctly configured.

    NOTE: It may be necessary to re-authenticate Windows
  9. When replacing a Primary server and using Neverfail Heartbeat v5.5.[n] or earlier, follow these steps:
    ( These steps do not apply to Neverfail Heartbeat V6.0 and more recent. )
    1. Follow the instructions in Knowledgebase Article #1255 How to request a license key for Neverfail Heartbeat using SCOPE Data Collector Service V4.1 and later to obtain a new license key.
    2. Select the License tab in the Configure Server wizard and replace the old license with the new one.
    3. Click Finish .
  10. Connect the Principal (Public) and Channel network cables.
  11. In the task bar, right click the Neverfail Heartbeat Server icon and start Neverfail Heartbeat.
  12. Log into the Neverfail Heartbeat Management Client and start replication.
  13. Set Neverfail Server R2 service to Automatic using the Windows Service Control Manager.

Applies To

All Versions


Related Information

Knowledgebase Article #1816 How to Replace a Windows 2000 Server

Knowledgebase Article #1774 How to Replace a Windows 2008 Server

KBID-851

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.