HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

Issue
9564
12758
13557
Description
Creating Vir tual File Server with ALL_SERVERS option can cause confusion
When creating Virtual File Servers with the ALL_SERVERS command-line option,
youshouldbeaware of thefollowing:
• When a Virtual File Server is created with the command-line ALL_SERVERS
option, any servers added to the cluster at a later time will automatically be
added to the Virtual File Server.
• The HP Management Console does not p rovide a way to identify Virtual File
Servers created with the ALL_SERVERS option.
• Servers added to a Virtual File Server with the ALL_SERVERS option cannot be
removed from the configuration via the Management Console. Instead, you will
need
to use the mx vfs update command and specify the individual servers that
aretobeincludedinthe configuration. For example, the following command
removes node3 from a 4-node Virtual File Server.
mx vfs update myVFS node1 node2 node4
Nodes crash
after
rebooting
When FS Option for Windows is installed, nodes sometimes crash immediately
afterrebooting. Thisisaknown Microsoft Windowsproblem. Ifyou are
experienc
ing crashes after rebooting servers, contact Microsoft and ask for the
hotfixdescribed in KnowledgeBasearticle 908249. Hotfixes are available for
both
32-bit and 64-bit systems.
Avoid forcing Virtual CIFS Servers to new primaries
FS Option for Windows supports subdirectory Virtual File Shares (VFS). Starting
asubdirectoryVFS maytriggerthe creation of thousands of shares. This can
take some time,evenonfastnodes. Itisnot uncommonfor this operationto take
several minutes in large configurations. Duri ng this time, the Virtual CIFS Server
(VCS) is not completely up, a nd some of the shares are unavailable for client
connections. Virtual File Sh ares on Virtual CIFS Server backup nodes create these
shares in advance to avoid unavailability on failover.
To avoid temporary unavailability of subdirectory shares, when changing the
Virtual CIF S Server’s confi guration be careful not to force the VCS to a new
primary. That is, a node newly d esignated as the VCS primary, but which before
the
configuration change did not have the VCS present.
Instead, when selecting new primaries, select from the existing backup nodes (which
already have the Virtual File Share up). When adding new nodes to the Virtual
CIFS Server,makethembackups (thisisthe default). Avoid usingAUTOFAILBACK
on
VCSs with more than one Virtual File Share (NOAUTOFAILBACK is the default
for VCS creation).
For the maximum flexibility and fine-grained failure handling, have only on e
Virtual File Share per Virtual CIFS Server if possible. This will not always be
possible, as in some consolidation scenarios where legacy server/share names
must be preserved.
22