Previous Topic: Manually Recover a Failed Server - Move IP AddressNext Topic: Manually Recover a Failed Server - Move IP and Switch Computer Name


Manually Recover a Failed Server - Switch Computer Name

To manually recover a failed server when the Switch Computer Name redirection method is used
  1. Boot the Master server without a network connection, to avoid duplicate network names.

    The Is Alive check from the Replica to the Master recognizes resource failure, and makes the original Replica the active server.

  2. Rename the Master server to <NewServerName>-RHA, and move it to a temporary workgroup.

    For example, if the server is called "Server1", rename it to "Server1-RHA".

  3. You are required to reboot this machine.

    After the reboot completes, the following error appears: At least one Service could not be started. Ignore this message, which it is normal under these circumstances, because the Engine usually runs in a domain account.

  4. Connect to the network.
  5. Rejoin the domain, ensuring that you use the -RHA name assigned in step 2.
  6. Reboot the machine.
  7. If the HA scenario is not already running, start the scenario from the Manager by clicking the Run button on the Standard toolbar.

    If you selected the Run Reverse Replication Scenario after Switchover option, the scenario runs in backward mode, from the original Replica to the original Master. The original Master now acts as the standby server.

  8. Wait for the synchronization to complete.
  9. To return the active role to the Master server, perform a manual switchover by clicking the Perform Switchover button on the Standard toolbar.

    Note: We recommend that you perform the manual switchover outside of normal business hours.