HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 4: Cluster Administration 20
may result in filesystem corruption. For example, the connection must
not be moved from one switch port to another, and a new
FibreChannel connection for the server must not be established while
HP Clustered File System is running on the server.
• 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.
• Do not delete disk partitions on LUNs accessed by HP Clustered File
System. The Windows operating system renumbers partitions when a
lower-numbered partition is deleted. HP Clustered File System uses
the partition number when it is identifying membership partitions
and dynamic volumes. Changes to the partition numbers will causes
failures, as HP Clustered File System cannot locate the correct data.
• Changing the hardware configuration, such as adding or replacing
switch modules, is not supported while HP Clustered File System is
running. This restriction applies only to FibreChannel switches that
are under the control of HP Clustered File System.
• 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.
Windows Authentication
• HP Clustered File System uses NT credentials to authenticate users
attempting to access data on PSFS filesystems.
Active Directory
HP Clustered File System requires that Active Directory be configured.
You should be aware of the following:
• With Windows 2003, all HP Clustered File System nodes must be
members of an Active Directory domain. This is necessary for
filesystem security.