3.6.1 HP PolyServe Matrix Server Administration Guide (T5392-96018, August 2008)

Chapter 4: Matrix Administration 20
• If servers from multiple matrices can access the SAN via a shared FC
fabric, avoid importing the same disk into more than one matrix.
Filesystem corruption can occur when different matrices attempt to
share the same filesystem.
• Do not delete disk partitions on LUNs accessed by Matrix Server. The
Windows operating system renumbers partitions when a lower-
numbered partition is deleted. Matrix Server uses the partition
number when it is identifying membership partitions and dynamic
volumes. Changes to the partition numbers will causes failures, as
Matrix Server cannot locate the correct data.
• Changing the hardware configuration, such as adding or replacing
switch modules, is not supported while Matrix Server is running. This
restriction applies only to FibreChannel switches that are under the
control of Matrix Server.
• 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
• Matrix Server uses NT credentials to authenticate users attempting to
access data on PSFS filesystems.
• If you are using HP PolyServe Software for Microsoft SQL Server, a
DNS entry must exist for each Virtual SQL Server/IP address. The
entry must include an A record and a [PTR] record for forward and
reverse lookup. Windows authentication may fail if these records do
not exist.
Active Directory
Matrix Server requires that Active Directory be configured. You should
be aware of the following:
• With Windows 2003, all Matrix Server nodes must be members of an
Active Directory domain. This is necessary for filesystem security.