4.0.0 HP Polyserve Matrix Server Release Notes (T5392-96051, March 2010)

DescriptionIssue
Built-in NT backup software fails on PSFS volumes when volume shadow copy is enabled
Volume shadow copy is enabled by default in the built-in NT backup software provided with Windows
2003. The PSFS filesystem does not support volume shadow copies. If you want to use the NT backup
software on a PSFS volume, you will need to disable volume shadow copy as described in the NT
backup documentation.
5897
Server’s IP address may change if assigned with DHCP
When DHCP or DHCP reservations are used to assign IP addresses to servers, the IP address can
change when the server is rebooted. The DHCP server may be slow to respond to the reboot, resulting
in the server temporarily using a random automatic IP address until the DHCP address is acquired.
While the server has the temporary address it will not be able to rejoin the matrix, as Matrix Server
expects the server to have the DHCP address.
During this process, the matrix configuration might be destroyed on the rebooted server; however,
the configuration can be restored by importing it from another node in the matrix (or by exporting
the configuration from a good node to the rebooted server).
To avoid this problem, use static IP addresses for the servers that will be in the matrix.
6364
Third-party MPIO software must discover devices
When third-party MPIO software is used, it must discover and present storage devices to the operating
system before Matrix Server is configured or started.
If Matrix Server is started and the third-party MPIO software has not previously discovered the
devices, Matrix Server will make a “best effort” to discover them. In some cases, Matrix Server will
initiate a single reboot.
Matrix Server will not start if it cannot discover the devices. The administrator must then determine
why the MPIO devices have not been discovered and resolve the issue.
7519
Matrix Server Installer does not find saved configuration
When Matrix Server is uninstalled, you can save the matrix configuration. If you then reinstall Matrix
Server in a different location, the Installer will not find the saved configuration. To avoid this problem,
reinstall Matrix Server in its original location. The Installer will then find the saved configuration and
apply it to the new installation of Matrix Server.
If you need to install Matrix Server in a new location, you will need to move the saved configuration
files to the new location before the Matrix Server installation.
7551
Filesystem resize does not work correctly with mount points
The PolyServe Management Console includes an option to extend the size of a filesystem. After a
filesystem is extended, Matrix Server attempts to reassign the drive letters or mount points associated
with the filesystem. Matrix Server reassigns drive letters correctly; however, it fails to reassign mount
points. You will need to recreate the appropriate mount points manually after the extend operation
is complete.
To recreate the mount points, first manually delete the old mount points (the empty directories on the
local NTFS volumes of each node). Next, recreate the empty directories and then use the PolyServe
Management Console to reassign the mount points manually.
7591
Virtual host can cause route change
When a virtual host is instantiated it uses the network mask of the interface upon which it is activated.
This can cause a unexpected route change if the virtual host address was intended for some other
interface on another network or if the virtual host address is mistyped.
For example, the following command adds the 10.10.1.100 address on the 10.11.1.1 interface.
mx vhost add 10.10.1.100 10.11.1.1
If the 10.11.1.1 interface had a netmask of 255.255.0.0, then the traffic for the 10.10/16 subnet
would be directly routed to the 10.11/16 network for this server rather than being routed to a
gateway on the 10.11/16 network.
8290
8