Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com
Answertopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

SUSE Linux Enterprise Server (SLES 10) Installation and Administration
Previous Page Home Next Page

12.2 A Sample Minimum Scenario

The procedures within a two-node cluster when one node fails and the various types of standby systems that can take over as necessary are outlined below (see Figure 12-1).

Figure 12-1 A Simple High Availability Cluster

The two servers (primary and backup) are both connected to a SAN (storage area network). Depending on the mode, this is only accessed by the active node. The servers communicate with each other in such a way that they regularly emit a sign of life (heartbeat). The communication channels (or heartbeat links) are also laid out in a redundant way, so independent channels can be used by means of a variety of network cards and cable channels. If one of the links fails, its backups continue to report correctly that the relevant server is still alive. If there is no sign of life from the main system, the standby system is activated, so it takes over the services of the failed partner and removes it from the network completely (STONITH).

SUSE Linux Enterprise Server (SLES 10) Installation and Administration
Previous Page Home Next Page

 
 
  Published Courtesy of Novell, Inc. Design by Interspire