HP PolyServe Matrix Server 4.1.
Legal and notice information © Copyright 2004, 2010 Hewlett-Packard Development Company, L.P.
Version: HP PolyServe Matrix Server 4.1.0 Description This document describes the HP PolyServe Matrix Server 4.1.0 release. Supersedes HP PolyServe Matrix Server 4.0.0 Enhancements HP PolyServe Matrix Server 4.1.0 provides support for Microsoft Windows Server 2008 R2 Standard or Enterprise Edition (64-bit). Installation instructions See the HP PolyServe Software installation guide for installation instructions. For upgrades from an earlier release, see the HP PolyServe Software upgrade guide.
• Paging I/O. This is reads and writes initiated by the memory manager, in which it asks the filesystem to fetch or store pages of file contents. Some examples are reads from files being executed and reads and writes to files cached by the Windows cache manager. • Removable devices. • Reparse points. PSFS filesystems can be mounted on mount points residing on NTFS filesystems. • Security descriptors. Security updates are immediately and simultaneously applicable to all servers in the cluster.
Warning: Unable to set the short 8.3 name for “V:\test-restore\WINNT\q50.dmp.gz”. Reason: The parameter is incorrect. Filesystem semantics The PSFS filesystem differs semantically from the NTFS filesystem in the following ways: • A file cannot be deleted if it is currently open on another node. • A file cannot be “renamed over” if it is currently open on another node. For example, an attempt to rename filea to fileb will fail if fileb is currently open on another node.
• Windows XP (with SP2 or SP3) 32-bit and 64-bit guest OS • SUSE Linux Enterprise Server 10 (with SP1 or SP2) 32-bit and 64-bit guest OS Windows utilities and services The following Windows utilities differ in operation on NTFS and PSFS filesystems: • Disk checks. In both Windows Explorer and the Disk Management utility, you can right-click a disk volume to see its properties. The Tools tab on the Properties window includes an option to check the disk volume for errors.
Matrix Server Number Description 3636 Network interfaces are marked “Up” and then “Down” repeatedly The status of network interfaces may change between “Up” and “Down” about every five seconds when there is only one server in the matrix and no other IP address is available to ping. This situation can occur when a two-node cluster loses a node or the node is removed from service.
Number Description 5897 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.
Number Description 8335 URL in HTTP service monitor can cause virtual host to fail The URL assigned to an HTTP service monitor should not reference the virtual host with which the HTTP service monitor is associated. If the virtual host is down, the HTTP service monitor will not be able to make a connection to the virtual host address and will also be down. A down service monitor on a virtual host then tends to keep the virtual host from ever being instantiated.
Number Description 12924 Add or Remove Programs appears to hang On startup, Add or Remove Programs enumerates the contents of all top-level directories of mounted volumes. When the root or top-level directories on PSFS filesystems contain large numbers of files, Add or Remove Programs appears to hang during this step. Workaround. Do not overpopulate the root directory and the top-level directories of PSFS filesystems with large numbers of files. Instead, place the files in subdirectories.
Number Description 14219 lanman IRPStackSize is too small After installing applications that use the IRP stack (such as some AntiVirus software), you may see error messages indicating that the value of the lanman IRPStackSize parameter needs to be increased. This problem has also been seen when upgrading Matrix Server from a release earlier than 3.4. (Matrix Server uses an additional IRP stack in release 3.4 and later.
Number Description 18265 Export fails when multiple nodes are specified When the matrix configuration is exported to multiple nodes, the export may fail for a particular node or nodes because the FibreChannel switch is receiving too many requests. The following error is displayed, followed by a Java exception. com.polyserve.mxconfig.StorageException: Cannot get switch information mxsanconf: 99.11.20.241 failed The given host is not responding to ICMP pings.
Number Description 20987 mx check command incorrectly reports that fencing is not configured This situation can occur when mx commands are used to configure the cluster, including the fencing method. The fencing configuration file, fence.conf, is included in the files exported to the other nodes; however, it might not exist on the node where the configuration was created. The mx check command reports the error because it cannot find the fence.conf file. The missing fence.
Number Description 28194 mx quota unsetuser command does not work When the mx quota unsetuser command is issued, the command does not remove quota entries. HP PolyServe Software for Microsoft SQL Server The following considerations affect HP PolyServe Software for Microsoft SQL Server. Number Description 3737 Virtual SQL Server names are not checked against existing NetBIOS names When a Virtual SQL Server is created, its name is not checked against the existing NetBIOS names.
Number Description 11133 SQL instance cannot be joined to domain while the instance is virtualized After a SQL instance is virtualized, it cannot be joined to the domain. Workaround. Complete the following steps: 1. Log into the domain controller. 2. Open “Active directory users and computers.” 3. Ensure that the SQL Server account is configured as follows: a. The “Account is sensitive and cannot be delegated” check box must not be selected. b.
Number Description 13341 Intermittent issue when installing SQL 2005 on 64-bit systems Occasionally, an error has been observed when installing SQL Server 2005 on 64-bit platforms. This error occurs with and without PolyServe Matrix Server. If this error is encountered, we recommend contacting Microsoft Support. The error summary is included below: Product : Microsoft SQL Server 2005 (64-bit) Product Version : 9.00.1399.
Number Description 16276 Backup instance monitor can remain disabled This issue can occur when multiple Virtual SQL Servers use the same backup node and have instances with identical names. When a Virtual SQL Server is moved to maintenance mode, the SQL monitors for the associated instances are disabled. On the backup node, this affects the other Virtual SQL Servers having instances with the same names; their monitors are also disabled.
Number Description 18814 Confusing error message appears when attempting to virtualize a SQL instance with an unsupported service account When an attempt is made to virtualize a SQL instance using the local Administrator account as the service account, the following operating system error appears: A member could not be added to or removed from the local group because the member does not exist HP PolyServe Software for Microsoft SQL Server does not support using local user service accounts for the service
Number Description 19632 SQL Server 2005 instance does not start If the computer name for a node has ever been changed, the SQL 2005 instances installed on that node may not start in the following circumstances: • During virtualization • During failover • After the upgrade to HP PolyServe Software for Microsoft SQL Server 3.8 Workaround. Change the service account group names to match the current name of the node. Next, remove the node from the domain and then rejoin it.
Number Description 22374 Instance does not start when the same port is used for IA and legacy mappings When the same port is used to map a legacy IP address to the IP address for a Virtual SQL Server, the SQL instance will be unable to start while the legacy mapping is active with the same port. This can prevent SQL from starting during Virtual SQL Server failovers and during a machine reboot. 22571 IA service generates log messages after upgrade After an upgrade to the 4.
Number Description 27815 Multi-Node Installer does not support disabling startup mode for SQL Server 2008 service accounts When the Disable option is selected as the startup mode for SQL Server 2008 service accounts, the SQL Server installation fails. Workaround. To disable the startup mode for specific service accounts, edit the following file: C:\Programfiles\PolyServe\MatrixServer\lib\apache\docroot\mni_defaults\ SQL2008_base.
HP PolyServe Software for Windows File Serving The following considerations affect HP PolyServe Software for Windows File Serving. Number Description 4507 File shares with duplicate names are problematic If a Matrix File Share and a Virtual File Share are created with the same name, the automated monitors can become confused about which File Share they are monitoring. This situation can cause unexpected failover behavior or can cause a File Share to point to the wrong resource. Workaround.
Number Description 13557 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.
Environment The following environmental considerations affect the operation of Matrix Server. Number Description 7435 QLogic Switch login can cause Matrix Server failures Matrix Server will not start if you are logged into a QLogic FibreChannel switch and “admin start” is set. If you log into the switch with “admin start” while Matrix Server is running, this switch problem can affect fencing operations and may cause the matrix to hang. Workaround.
