HP PolyServe Matrix Server release notes HP PolyServe Matrix Server 4.0.
Legal and notice information © Copyright 2004, 2010 Hewlett-Packard Development Company, L.P.
Version: HP PolyServe Matrix Server 4.0.0 Description This document describes the HP PolyServe Matrix Server 4.0.0 release. Supersedes HP PolyServe Matrix Server 3.6.1 Enhancements HP PolyServe Matrix Server 4.0.0 includes support for Microsoft Windows Server 2008 Standard, Enterprise, or Datacenter Edition (64-bit) with Service Pack 2 (SP2). It also includes the following new features and implementation changes: • Compatibility support for Hyper-V.
• Case-insensitive naming. • Case-sensitive naming. • Content indexing. PSFS support is the same as the FAT filesystem. (See “Unsupported Features” for more information.) • Directory Change Notification (DCN). PSFS supports both local-node and cross-node Change Notification. • Disk quotas. • 8.3 short file names and name tunneling. • Hidden, readonly, archive bits (and so on). • Memory-mapped files. PSFS support is for the local node only; memory mapped file data is not coherent cluster-wide.
• • • • • • • • Filesystem self-healing. Extended Attributes for the filesystem. Transactional filesystem. Encryption. Compression. USN change journal. BitLocker: no encryption on PSFS filesystems. Cross-file replication (DFS-R). If you restore data from an NTFS filesystem to a PSFS filesystem, you may see warnings such as the following. The warnings indicate that data belonging to an unsupported NTFS feature will be lost during the restore.
• PSFS does not support direct renaming of an unnamed primary stream to Alternate Data Streams (ADS). PSFS does support copying an unnamed primary stream to ADS. • With PSFS, a file cannot be renamed or deleted, either locally or remotely, if any of its Alternate Data Streams (ADS) are still open (with or without SHARE_DELETE). Windows utilities and services The following Windows utilities differ in operation on NTFS and PSFS filesystems: • Disk checks.
Matrix Server Issue 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.
Issue 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.
Issue 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.
Issue 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.
Issue Description 13996 mx fs destroy partially destroys snapshots Do not use the mx fs destroy command to remove a snapshot. If you attempt to delete a snapshot with the mx fs destroy command, the snapshot filesystem will be removed but the snapshot will remain on the array. You will then need to manually remove the snapshot LUNs from the array. (After removing the LUNs, you will see disk import errors on the console for the LUNs that were removed.
Issue Description 17660 Matrix description cannot be reset when Matrix Server is not running The matrix description is set when you initially configure the matrix. If you need to reset the description at a later time, Matrix Server must be running while you make the change. 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.
Issue Description 20040 FILE_ATTRIBUTE_NOT_CONTENT_INDEXED cannot be set on PSFS filesystems via Windows Explorer When viewing files on a PSFS filesystem with Windows Explorer, the Properties dialog does not contain a link to the Advanced Attributes dialog, which contains the FILE_ATTRIBUTE_NOT_CONTENT_INDEXED attribute. Workaround. For Vista/Windows 2008 clients, use the attrib command to set the attribute.
Issue Description Unexpected behavior can occur when a virtual IP address is lower than the system's primary address Matrix Server requires that the system's primary address be the lowest IP address configured on the system. When creating virtual hosts, be sure to assign IP addresses higher than the system's primary address. HP PolyServe Software for Microsoft SQL Server The following issues affect HP PolyServe Software for Microsoft SQL Server.
Issue 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.
Issue 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.
Issue 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.
Issue 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
Issue 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.
Issue 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.
Issue 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.
Issue Description 5344 Disabling a server does not disable Matrix File Shares When a server is disabled, the Matrix File Shares on that server remain active. Workaround. Either disable the Matrix File Shares one-at-a-time, or disable the LanManServer service. 6555 IP address may be set to 0.0.0.
Issue 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 issues The following environment issues affect the operation of Matrix Server. Issue 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.
