Cluster Configuration - Overview

You can configure and manage Windows and Unix Cluster Group clients from the CommCell Console.

Prior to configuring the Cluster Group client, install the required software on all the physical nodes that host the Cluster Group. Then proceed to configure a Cluster Group client for this Cluster Group from the CommCell Console.

To define the data that you want to backup, create a Subclient for this Cluster Group client. Now you can start performing backup and recovery operations and take advantage of the reliability and fault-tolerance provided by the clusters. If an active node fails, the software will seamlessly resume using the next available active node during backup and recovery operations.

Terminology

Refer to the following terminologies often used with respect to Cluster Configuration.

When referring to the physical servers that comprise a Cluster Group, individual computers are referred to as nodes. The physical server may be referred to as "physical computer", "physical node", or  "client computer" depending upon the context in which it is being discussed. Also, the "physical server" can either be "active" or "standby/ passive" based on whether or not it is actively performing an operation within the cluster environment at a particular time.

"Cluster Group ", "Cluster Server", "Cluster Resource Group" and "Virtual Node" - all refer to the hardware and software components within the cluster. These components are managed by the "Cluster Service", the collection of components on each node that perform cluster-specific activity. The Cluster Server is actually not a physical computer but operates as a single, logical unit within the system. Like the physical servers, however, the Cluster Server does have its own Internet Protocol (IP) address and network name.

The "Shared Disk" resource is connected to each physical computer and hosts the common data for CommCell operations, such as data protection and recovery. Information that is only relevant to an individual physical server should be on that physical server's local disk, not on the shared disk.