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
Virtual names and addresses are the only identification used by clients on the network. Because the
names and addresses are virtual, their ownership can transition from one node to the other during a
failover, preserving access to the resources in the cluster group.
A cluster uses at least two network connections on each node:
• The private cluster interconnect or “heartbeat” crossover cable connects to one of the network
ports on each cluster node. In more than two node deployments, a private VLAN on a switch or
hub is required for the cluster interconnect.
• The public client network subnet connects to the remaining network ports on each cluster node.
The cluster node names and virtual server names have IP addresses residing on these subnets.
NOTE:
If the share is to remain available during a failover, each cluster node must be connected to the same
network subnet. It is impossible for a cluster node to serve the data to a network to which it is not connected.
Protocol planning
Not all file sharing protocols can take advantage of clustering. If a protocol does not support clustering,
it will not have a cluster resource and will not failover with any cluster group. In the case of a failover,
a client cannot use the virtual name or virtual IP address to access the share since the protocol cannot
failover with the cluster group. The client must wait until the initial node is brought back online to
access the share.
HP recommends placing cluster aware and non cluster aware protocols on different file shares.
Table 6 Sharing protocol cluster support
Supported on cluster
nodes
Cluster Aware
(supports failover)
Client VariantProtocol
YesYesWindows NTCIFS/SMB
Windows 2000
Windows 95
Windows 98
Windows ME
YesYesUNIXNFS
Linux
YesNoWebHTTP
YesYesManyFTP
YesNoNovellNCP
NoNoAppleAppleTalk
YesYes
Standards-based iSCSI
initiator
iSCSI
HP ProLiant SB460c SAN Gateway Storage Server 95