Configuring Failover and Failback Support

When an individual application or user resource (also known as a cluster resource) fails on a cluster node, Cluster Service will detect the application failure and try to restart the application on the cluster node. If the restart attempt reaches a preset threshold, Cluster Service brings the running application offline, moves the application and its resources to another cluster node, and restarts the application on the other cluster node(s). This process of automatically moving resources from a failed cluster node to other healthy cluster node(s) is called failover.

When the system administrator repairs and restarts the failed cluster node, the oppo- site process occurs. After the original cluster node has been restarted and rejoins the cluster, the Cluster Service will bring the running application and its resources offline, move them from the failover cluster node to the original cluster node, and then restart the application. This process of returning the resources back to their original cluster node is called failback.

You can configure failback to occur at any given time, or not at all. However, be sure to configure the failback time during your offpeak hours to minimize the effect on users, as they may see a delay in service until the resources come back online.

In order to failover and failback running applications, cluster resources are placed together in a group so the Cluster Service can move the cluster resources as a com- bined unit. For example, an application such as Internet Information Server (IIS) requires a virtual disk, IP address, and a network name resource. IIS also requires a resource called “IIS Server Instance.” The IIS services and the IIS Server Instance resource can be placed in its own group and labeled, “IIS Group” for identification. Since the IIS Group (the resource group) contains all of the resources for the applica- tion (IIS), Cluster Service can bring all of the necessary components online in their proper order to ensure that failover and/or failback procedures transfers all of the user resources as transparently as possible.

The following section provides information on failover support for 4-node clustering, and provides tables for each failover option that includes a preferred cluster node list for cluster group failover or failback that will help you implement your failover configuration.

Failover Support Through Four-Node Clustering

One of the key features of Datacenter Server is that it supports a 2-node, 3-node, and 4-node failover clustering solution. The PowerEdge FE100/FL100 Datacenter Server systems provide the 2-node to 4-node failover cluster solution and is designed to pro- vide higher levels of availability through improved service offering and additional cluster functionality.

When a failover situation occurs, the Cluster Service will take the resources offline and (by default) move them to the next cluster node number. For example, if cluster node 1 fails, Cluster Service will move the resources to the next cluster node number, which is cluster node 2. This default type of failover is called “Cascading failover.” After the malfunctioning cluster node is repaired and failback is enabled, Cluster Ser- vice will failback the resources using the same procedures as failover.

6-18 User’s Guide

Page 58
Image 58
Dell FE100, FL100 manual Configuring Failover and Failback Support, Failover Support Through Four-Node Clustering

FL100, FE100 specifications

The Dell FE100, FL100, FL200, and FE200 are part of Dell's lineup of advanced networking switches designed to cater to the increasing demand for efficient data handling in enterprise environments. These switches combine powerful performance with a range of features that ensure scalability, reliability, and ease of management.

The Dell FE100 is a compact yet robust switch that caters primarily to small and medium-sized businesses. It provides gigabit connectivity with multiple ports for enhanced network performance. The FE100 is equipped with layer 2 capabilities, which offer essential features such as VLAN support, port mirroring, and link aggregation, ensuring seamless data flow across the network.

In contrast, the Dell FL100 stands out with its advanced layer 3 functionality. This switch is designed for more complex enterprise environments where routing capabilities are necessary. The FL100 supports static and dynamic routing protocols, which enhance network efficiency and traffic management. Furthermore, its Quality of Service (QoS) features enable prioritization of critical applications, optimizing network resources.

Moving up the lineup, the Dell FL200 offers increased port density and enhanced performance metrics. It caters to high-traffic networks with features such as enhanced security protocols and advanced traffic management capabilities. The FL200 integrates seamlessly into larger network infrastructures and is designed to support advanced IPv6 routing, ensuring future-proofing in an evolving technological landscape.

Finally, the Dell FE200 switch is a high-performance, enterprise-grade solution suited for environments that demand maximum throughput and minimal latency. It offers dual-speed capability, supporting both 10GbE and 1GbE connections. The FE200 is characterized by its high level of robustness and redundancy features, including dual power supplies, which safeguard against potential downtime. The switch also provides comprehensive management tools, enabling network administrators to monitor and configure the network seamlessly.

In conclusion, the Dell FE100, FL100, FL200, and FE200 switches represent a versatile and powerful range of networking devices tailored to meet various business needs. With a blend of advanced features, scalability options, and exceptional performance characteristics, these switches are invaluable assets for organizations aiming to optimize their network infrastructure. Whether for small setups or large enterprises, Dell's networking solutions provide reliability and efficiency in today’s fast-paced digital landscape.