Creating clustered file shares (CIFS and NFS)
Note:
For HTTP and FTP clustering setup and file sharing, refer to the information
at the following URL:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q248025
The creation of file shares on a cluster involves dependencies on a physical disk, a
static IP address, and a network name. These dependencies allow resources that
are defined to the same disk group to move as a group. The dependencies also
assure necessary access for the given resource.
Note:
You must configure Server for NFS before NFS file sharing can be used.
See “Enabling Server for NFS” on page 52 for details.
Figure 5 illustrates the file share dependencies. Descriptions of the diagram
components follow the figure.
Physical disk
The base resource in which to store user data. It is not dependent on any
other resources except the physical disk that it defines. The disk resource
must also have the same drive letters on both nodes so that the definitions
of resources that depend on it do not change if the resource is moved to
the other node.
Static IP address
A virtual address that binds onto an existing IP address on one of the
cluster’s public networks. This IP address provides access for clients and is
not dependent on a particular node, instead a subnet that both nodes can
access. Because this address is not the physical adapter’s permanent
address, it can bind and unbind to its paired adapter on the same network
on the other node in the cluster. You can create multiple IP addresses using
the Cluster Administrator on the same physical network. A unique static IP
address is required for each virtual server.
Note:
The cluster IP address should not be used for file shares. That
address is reserved to connect to and manage the cluster through
the network that it is defined on.
Network name
An alternate computer name for an existing named computer. It is physically
dependent on an IP address of one of the public networks. When a disk
group contains an IP address resource and a network name, it is a virtual
File share
Physical disk
Network name
(Virtual server name)
IP
(Physical LAN connection)
Figure 5. File share dependencies
50
NAS Gateway 300 User’s Reference
Summary of Contents for G27
Page 1: ...TotalStorage NAS Gateway 300 Model G27 User s Reference GA27 4321 00 ...
Page 8: ...viii NAS Gateway 300 User s Reference ...
Page 10: ...x NAS Gateway 300 User s Reference ...
Page 14: ...xiv NAS Gateway 300 User s Reference ...
Page 26: ...12 NAS Gateway 300 User s Reference ...
Page 40: ...26 NAS Gateway 300 User s Reference ...
Page 46: ...32 NAS Gateway 300 User s Reference ...
Page 68: ...54 NAS Gateway 300 User s Reference ...
Page 134: ...120 NAS Gateway 300 User s Reference ...
Page 136: ...122 NAS Gateway 300 User s Reference ...
Page 168: ...154 NAS Gateway 300 User s Reference ...
Page 182: ...168 NAS Gateway 300 User s Reference ...
Page 199: ......
Page 200: ... Printed in U S A GA27 4321 00 ...