Cobalt Raq550 Failover & Recovery Brought to you by Internet Workflow Systems, LLC

WARNING: A Failover condition should not be initiated lightly. This system is not designed to be cycled repeatedly. Minor problems to the system should be troubleshot in a traditional fashion. Only a sudden catastrophic failure of the system should be considered for Failover. For this reason, automatic monitoring of system for failover condition is discouraged and not part of this procedure. Failover conditions should always be performed manually

This procedure is designed to walk through the process of switching the Failover Server to take over as the new Primary server and how to then place the failed server into service as the new Failover server.

The following picture represents the front view of the cobalt server:

Failover

Upon a serious problem with the Primary server, the following should be done to place the Failover server into service.

1. Shutdown the Primary Server
   If the machine is still running, shut it down by pressing the power button (2) or
   by typing shutdown -h now at the command line.
2. Run the failover program on the Failover server.
   1. Telnet or SSH into the Raq550 that is your Failover server.
   2. Super Use to the root user
      su - root
   3. Run the failover script
      failover

Placing New or Repaired machine as new Failover

1. Make sure any hardware problems with failed machine have been resolved
2. Make previous Failover machine (now in service) the new Primary machine
   1. Telnet or SSH into the Raq550 server.
   2. Super Use to the root user
      su - root
   3. Remove the etc symbolic link
      rm /etc
   4. Rename /etc.backup directory
      /etc.backup /etc
3. Perform OS Restore Procedure on New Failover Server
   If this is not a new machine, perform the OS Restore procedure as outlined in the Cobalt Raq550 User Documentation
4. Configure as Failover Server per Creating a Hot Spare Server for the Cobalt Raq550.