Instruction Manual
Table Of Contents
- HP ProLiant SB460c SAN Gateway Storage Server
- Table of Contents
- About this guide
- 1 Storage management overview
- 2 File server management
- File services features in Windows Storage Server 2003 R2
- File services management
- Volume shadow copies
- Folder and share management
- File Server Resource Manager
- Other Windows disk and data management tools
- Additional information and references for file services
- 3 Print services
- 4 Microsoft Services for Network File System (MSNFS)
- MSNFS Features
- MSNFS use scenarios
- MSNFS components
- Administering MSNFS
- Server for NFS
- User Name Mapping
- Microsoft Services for NFS troubleshooting
- Microsoft Services for NFS command-line tools
- Optimizing Server for NFS performance
- Print services for UNIX
- MSNFS components
- 5 Other network file and print services
- 6 Enterprise storage servers
- 7 Cluster administration
- Cluster overview
- Cluster terms and components
- Cluster concepts
- Cluster planning
- Preparing for cluster installation
- Cluster installation
- Configuring cluster service software
- Cluster groups and resources, including file shares
- Print services in a cluster
- Advanced cluster administration procedures
- Additional information and references for cluster services
- 8 Troubleshooting, servicing, and maintenance
- 9 System recovery
- A Regulatory compliance and safety
- Index
7 Cluster administration
NOTE:
Not all HP ProLiant Storage Servers can be clustered. See the HP ProLiant Storage Server QuickSpecs to
determine if your storage server can be clustered. Windows Storage Server 2003 Release 2 clusters can
include up to eight nodes.
One important feature of the HP ProLiant Storage Server clusterable models is that they can operate
as a single node or as a cluster. This chapter discusses cluster installation and cluster management
issues.
Cluster overview
Up to eight server nodes can be connected to each other and deployed as a no single point of failure
(NSPOF) cluster. Utilizing a private network allows communication amongst themselves in order to
track the state of each cluster node. Each node sends out periodic messages to the other nodes; these
messages are called heartbeats. If a node stops sending heartbeats, the cluster service fails over any
resources that the node owns to another node. For example, if the node that owns the Quorum disk
is shut down for any reason, its heartbeat stops. The other nodes detect the lack of the heartbeat and
another node takes over ownership of the Quorum disk and the cluster.
Clustering servers greatly enhances the availability of file serving by enabling file shares to fail over
to additional storage servers if problems arise. Clients see only a brief interruption of service as the
file share resource transitions from one server node to the other.
HP ProLiant SB460c SAN Gateway Storage Server 89