
•
All nodes must be on the same subnet.
Cluster groups and resources, including
fi
le shares
The Cluster Administrator tool provides complete online help for all cluster administration activities.
Cluster resources include administrative types of resources as well as
fi
le shares. The following paragraphs
include overview and planning issues for cluster groups, cluster resources, and clustered
fi
le shares.
Creating and managing these resources and groups must be managed through Cluster Administrator.
Cluster group overview
A default cluster group is automatically created when the cluster is
fi
rst created. This default cluster group
contains an Internet Protocol (IP) Address resource, a Network Name resource, and the Quorum disk
resource. When the new cluster is created, the (IP) address and the cluster name that were speci
fi
ed
during setup are set up as the IP address and network name of this default cluster group.
CAUTION:
Do not delete or rename the Cluster Group or IP Address. Doing so results in losing the cluster and
requires reinstallation of the cluster.
When creating groups, the administrator's
fi
rst priority is to gain an understanding of how to manage the
groups and their resources. Administrators may choose to create a resource group and a virtual server for
each node that will contain all resources owned by that node, or the administrator may choose to create
a resource group and virtual server for each physical disk resource. Additionally, the administrator should
try to balance the load of the groups and their resources on the cluster between the nodes.
Node-based cluster groups
Creating only one resource group and one virtual server for each node facilitates group and resource
administration. This setup allows administrators to include all
fi
le share resources under one group.
Clients access all of the resources owned by one node through a virtual server name.
In node-based cluster groups, each group has its own network name and IP address. The administrator
decides on which node to place each physical disk resource. This con
fi
guration provides a very coarse
level of granularity. All resources within a group must remain on the same node. Only two IP addresses
and network names are required. This con
fi
guration creates less overhead for resource and network
administration. A possible disadvantage of this approach is that the resource groups can potentially
grow large when many
fi
le shares are created.
Load balancing
The creation of separate cluster groups for each virtual server provides more
fl
exibility in balancing the
processing load on the cluster between the two nodes. Each cluster group can be assigned to a cluster
node with the preferred owner parameter. For example, if there are two cluster groups, the cluster could
be set up to have the
fi
rst cluster group owned by Node A and the second cluster group owned by Node
B. This allows the network load to be handled by both devices simultaneously. If only one cluster group
exists, it can only be owned by one node and the other node would not serve any network traf
fi
c.
File share resource planning issues
CIFS and NFS are cluster-aware protocols that support the Active/Active cluster model, allowing resources
to be distributed and processed on both nodes at the same time. For example, some NFS
fi
le share
resources can be assigned to a group owned by a virtual server for Node A and additional NFS
fi
le
share resources can be assigned to a group owned by a virtual server for Node B.
Con
fi
guring the
fi
le shares as cluster resources provides for high availability of
fi
le shares. Because the
resources are placed into groups, ownership of the
fi
les can easily move from one node to the other,
HP ProLiant Storage Server
109
Summary of Contents for DL320s - ProLiant 9TB SATA Storage Server NAS
Page 14: ...14 About this guide ...
Page 28: ...28 Installing and configuring the server ...
Page 36: ...36 Storage management overview ...
Page 68: ...68 File server management ...
Page 74: ...74 Print services ...
Page 96: ...96 Enterprise storage servers ...
Page 120: ...120 Troubleshooting servicing and maintenance ...
Page 122: ...122 System recovery ...