How to replace windows 2003 Server in the event of failure

Posted on 4:25 PM by Bharathvn

How to replace a Windows 2003 Server in the Event of a Failure

Purpose

This article provides steps to replace a server in the event of a failure.

Resolution

Note: Read the entire process prior to attempting this procedure.

Initial Assumptions
  • The Operating System is installed on the C drive.
  • vCenter Server Heartbeat is installed on the C drive.
  • vCenter Server Heartbeat is installed in a LAN environment.
  • The Secondary server will be replaced.
  • The replacement server meets the documented prerequisites for vCenter Server Heartbeat installation (for example, ACPI compliant with the remaining server). For more information, see Prerequisites in the vCenter Server Heartbeat Reference Guide.
Before You Begin
  • Determine the identity of the server that needs to be replaced. If the server's identity is Primary, refer to the Replacing Primary Server section of this article.
  • Open the vCenter Server Heartbeat Console and go to the Filters section. Note in a file or on a piece of paper all of the replication filters.
  • Read the entire contents of this article.
Procedure
On the Primary Server:
  1. Shutdown vCenter Server Heartbeat and stop all protected applications when asked.
  2. Set Neverfail Server R2 to Manual using the Windows Service Control Manager.
  3. Open vCenter Server Heartbeat Configure Server wizard.
    1. Go to the Machine tab.
    2. Change the Physical Hardware Identity to Secondary.
    3. Change the Current Role to Passive.
    4. Click Finish.

  4. Search the C:\ drive for *.dmp and delete all existing .dmp files. Ensure that they are emptied from the Recycle bin.
  5. Run NTBackup.
    1. Select the entire C:\ drive and any other directories on a different drive that include program files of the protected application.
    2. Deselect any directories that are already part of the replication set.
    3. Click System State.
    4. Select a local location for the backup file.
    5. When this has finished, re-run the vCenter Server Heartbeat Configure Server wizard.
    6. Go to the Machine tab.
    7. Change the Physical Hardware Identity to Primary.
    8. Change the Current Role to Active.
    9. Click Finish.

  6. In the task bar, right-click on the vCenter Server Heartbeat Server icon and choose Start vCenter Server Heartbeat.
  7. Log into the vCenter Server Heartbeat Console. Select stop replication but leave the Protected Application running.
  8. Set Neverfail Server R2 to Automatic using the Windows Service Control Manager.
Replacing the Secondary Server
On the New Secondary Server:
  1. Copy the backup file from the Primary server.
  2. Unplug the principal (public) and channel cables from the server.
  3. Run NTBackup.
    1. Go to Tools > Options.
    2. Click the Restore tab.
    3. Select Always replace files on my computer and choose Apply.
    4. Click the Restore and Manage Media tab.
    5. Right-click File and choose Catalog File.
    6. Browse to the location and select the backup file that was copied from the Primary server.
    7. Expand the tree under the catalogued file and select all the backed up data (for example, C drive, System state).
    8. Click Start Restore and Ok to the warning message that follows.
    9. Click Ok to start the restore.
    10. Reboot the server after the restore process is complete.

  4. Let Plug and Play continue and reboot the server if asked to reboot.
  5. Check that the network cards IP settings are correct and ensure that the vCenter Server Heartbeat packet filter is enabled for the principal (public) connection and disabled for all channel connections.

    Note: It may be necessary to re-authenticate Windows.

  6. Plug in the principal (public) and channel network cables.
  7. Start replication.
  8. Set Neverfail Server R2 to Automatic using the Windows Service Control Manager.
Replacing the Primary Server
On the Secondary server:
  1. Start the Configure Server wizard.
  2. Click the Machine tab and change the Physical Hardware Identity of the server from Secondary to Primary.

    Warning: Do not perform this change in any other situation.

  3. Follow the procedure in Replacing the Secondary server described above.

    Note: In this case you will have your previously Secondary server running as the Primary server in the new pair.