HP StorageWorks Clustered File System 3.2.1 Windows Storage Server Edition Administration Guide (February 2006)

Chapter 3: Cluster Administration 16
– Disable or re-enable a network interface via the Device Manager.
– Update network drivers.
– Hot-swapping of PCI cards.
• If servers from multiple clusters can access the SAN via a shared FC
fabric, avoid importing the same disk into more than one cluster.
Filesystem corruption can occur when different clusters attempt to
share the same filesystem.
• Windows authentication is required for access to data on PSFS
filesystems, but not for cluster administration via the HP CFS
Management Console. (The console does not provide access to
filesystem data.)
• When configuring security on PSFS filesystems, use domain users and
groups instead of local users and groups. Security cannot be enforced
unless all nodes participate in the same domain AND domain users
and groups are used exclusively in the filesystem ACLs.
Using Active Directory with HP Clustered File
System
When configuring Active Directory and HP Clustered File System, you
should be aware of the following requirements:
• All HP Clustered File System nodes must be members of an Active
Directory domain. This is necessary for filesystem security.
• Active Directory user and groups should be used in filesystem ACLs
and SQL Server service accounts and roles. Do not use local users and
groups for these purposes because they are meaningless to other
nodes in the cluster.
• HP Clustered File System nodes should not be used as domain
controllers because the two services will compete for resources,
resulting in decreased performance.
• The DNS servers used by Active Directory and HP Clustered File
System should not reside on HP Clustered File System nodes. Placing
the DNS servers on HP Clustered File System nodes creates a race
condition that prevents HP Clustered File System from starting.