4.1.0 HP Polyserve Matrix Server Release Notes (T5392-96068, October 2010)

DescriptionNumber
Avoid forcing Virtual CIFS Servers to new primaries
HP PolyServe Software for Windows File Serving supports subdirectory Virtual File Shares (VFS).
Starting a subdirectory VFS may trigger the creation of thousands of shares. This can take some
time, even on fast nodes. It is not uncommon for this operation to take several minutes in large
configurations. During this time, the Virtual CIFS Server (VCS) is not completely up, and some of
the shares are unavailable for client connections. Virtual File Shares 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 CIFS Server's
configuration be careful not to force the VCS to a new primary. That is, a node newly designated
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, make them backups
(this is the default). Avoid using AUTOFAILBACK 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 one 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.
13557
Cannot remove share that is a DFS root target
If you have a CIFS share that is also a DFS root target, the DFS service must be stopped before
the share can be removed. Occasionally it is necessary to remove shares managed by HP PolyServe
Software for Windows File Serving, such as at shutdown time. If HP PolyServe Software for Windows
File Serving is unable to stop the DFS service, it will not be able to remove such shares and they
will remain after the product has stopped.
Until you implement a workaround, this problem can randomly impact availability for some clients.
Workarounds. Restart the product (although the share remains, the product will function correctly);
or manually remove the share after the product has stopped (either use DFS configuration tools to
remove the share, or stop DFS, remove the share, and then restart DFS).
To avoid this problem, do not use a share managed by HP PolyServe Software for Windows File
Serving as a DFS root target. Instead, use NTFS for DFS root targets and use PSFS for DFS link
targets.
14064
monitor_agent log file can grow excessively
The monitor_agent.log file can grow to approximately 10 MB before it is rotated. When the
file is rotated, the previous five copies are saved. The current and saved log files can total
approximately 60 MB.
Workaround. To limit the size of the log file and the saved copies, you can change the rotation
threshold of the monitor_agent.log file. For example, to set the size of the file to 1 MB (6 MB
total), add the following line to the end of the Matrix Server pstrace.ini file.
monitor_agent.log 1000
The file is in the following location, where C: is the drive where Matrix Server is installed:
C:\Program Files\PolyServe\MatrixServer\conf\pstrace.ini
14083
Virtual CIFS shares are not available after Windows Server 2003 Service Pack 1 is installed
This situation affects only the matrix node that is hosting the Virtual CIFS Server. Normal client
activity is not affected. This is a known Microsoft Windows issue. Refer to the following Microsoft
Knowledge Base article for more information.
http://support.microsoft.com/kb/926642
16049
HP PolyServe Matrix Server 4.1.0 release notes 23