PolyServe® Matrix Server Release Notes PolyServe® Matrix Server 3.4.
Copyright © 2004-2007 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents PolyServe Matrix Server New Features in Matrix Server 3.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Implementation Changes in Matrix Server 3.4.0 . . . . . . . . . . . . . . . . . . . . 2 Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Upgrade for HP Secure Path Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Maximum Length for Disk UIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PolyServe Matrix Server New Features in Matrix Server 3.4.0 Matrix Server 3.4.0 includes the following new features: • Disk quotas on volumes containing PSFS filesystems. See the PolyServe Matrix Server Administration Guide for information about enabling and managing quotas. • Hardware snapshots of PSFS filesystems that are located on HP EVA arrays. • Shadow copies of shared folders.
PolyServe Matrix Server Release Notes 2 • The Matrix Server Connect window now allows you to create a bookmark when you connect to a server. The bookmark is stored in the .matrixrc file and can include the user name and optionally the password. Server bookmarks can be synchronized automatically if desired. When you connect to a server, this feature automatically creates or deletes bookmarks to match the list of servers in the matrix to which the server belongs. If you currently have a .
PolyServe Matrix Server Release Notes 3 – A new volume cannot include subdevices having partition numbers above 31. Existing volumes cannot be extended to include the higher-numbered partitions. – You will not be able to take a hardware snapshot of partitions with numbers above 31. – A single Alert will be issued if any disks or volumes in the matrix contain unsupported partitions. The Alert will remain until the disks with unsupported partitions are deported.
PolyServe Matrix Server Release Notes 4 Documentation Updates Upgrade for HP Secure Path Users If you are upgrading from Matrix Server 2.7.2 to the 3.4.0 release, we recommend that you migrate HP StorageWorks Secure Path to DSM. Before making this change, be sure to consult with HP regarding their storage support for HP DSM. Maximum Length for Disk UIDs The maximum length for a Matrix Server disk UID is 128 characters.
PolyServe Matrix Server Release Notes 5 • 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. (See “Filesystem Semantics” for more information.) • Open by File ID. • Opportunistic locking. PSFS supports coherency of client-cached data over a single CIFS server and over multiple CIFS servers sharing the same filesystem. • Paging I/O. • Removable devices. • Reparse points.
PolyServe Matrix Server Release Notes 6 • Automatic generation of DOS 8.3 filename entries for “long” filenames. Name tunneling is also not supported. • Hard links. • NTFS change journal. As a consequence, file replication services (FRS) cannot be used. Content indexing is also affected. The content indexing service uses the NTFS change journal to determine when to update the indices. In the PSFS filesystem, updates to the indices are done less frequently. • Object IDs. • Online defragmentation.
PolyServe Matrix Server Release Notes 7 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. • The time that a file was last accessed is not updated after a successful read operation, even on the local node.
PolyServe Matrix Server Release Notes 8 traverse access checking to protect sensitive data that is encoded in the names of files or directories. Instead, the user should place sensitive data in files and should rely on file security descriptors to deny access to the filesʹ contents by unauthorized users. Windows Utilities and Services The following Windows utilities differ in operation on NTFS and PSFS filesystems: • Disk checks.
PolyServe Matrix Server Release Notes 9 Matrix Server The following issues affect Matrix Server 3.4.0. Bug 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.
PolyServe Matrix Server Release Notes Bug Description 4360 Management Console does not support admin passwords ending in the characters “??” 10 If the admin password is changed to a string that ends with the characters “??”, the PolyServe Management Console will not allow a login using that password to succeed. The symptom is that the Management Console will repeatedly prompt for the password. Workaround. Do not use a password that ends with “??”.
PolyServe Matrix Server Release Notes Bug Description 5807 Legato NetWorker volume shadow copy not supported 11 Matrix Server does not currently support the manner in which Legato NetWorker 7.1.1 uses volume shadow copies. We recommend that you configure NetWorker so that it will not use shadow copies. One way to do this is to choose Options > Save Options in the NetWorker client, and then type VSS:*=off in the options box.
PolyServe Matrix Server Release Notes Bug 12 Description 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.
PolyServe Matrix Server Release Notes 13 Bug Description 7591 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.
PolyServe Matrix Server Release Notes Bug Description 8335 URL in HTTP service monitor can cause virtual host to fail 14 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.
PolyServe Matrix Server Release Notes 15 Bug Description 12050 Matrix may not start when fencing method is changed If the fencing method is changed and all servers in the matrix were not shut down cleanly, the matrix may not be able to start successfully. To check for this condition and correct it if necessary, first run the mpdump command with no options. mpdump Membership Partition Host Registry (Version 3): Host ID: 10.10.180.5 fencestatus=0 fencetype=0 Fence ID:21:00:00:e0:8b:0c:12:1f::10.10.11.
PolyServe Matrix Server Release Notes Bug Description 12239 File Server Resource Manager cannot be used 16 The File Server Resource Manager provided with Windows 2003 R2 is not compatible with PSFS volumes and cannot be used to manage them. 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.
PolyServe Matrix Server Release Notes Bug Description 13284 mx quota --defaultQuotaType command is case-sensitive 17 The argument for the mx quota --defaultQuotaType command must be specified in lower-case letters. A Java exception occurs if upper-case letters are used.
PolyServe Matrix Server Release Notes Bug Description 13988 vssadmin cannot be used with snapshots 18 When snapshots are created through the PolyServe Management Console or the mx snapshot command, they are created via the HP EVA array interface without the involvement of VSS (Microsoftʹs Volume Shadowcopy Service).
PolyServe Matrix Server Release Notes Bug Description 14219 lanman IRPStackSize Is Too Small 19 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 to the 3.4.0 release, which uses an additional IRP stack.
PolyServe Matrix Server Release Notes 20 Matrix Database Solution Pack for SQL Server The following issues affect the Matrix Database Solution Pack for SQL Server. Bug 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. Consequently, it is possible to create duplicate NetBIOS names on the network. This will cause the Virtual SQL Server to fail when it is started.
PolyServe Matrix Server Release Notes Bug Description 4432 Management Console shows inconsistent information 21 The list of available servers on the Add SQL 2000 Virtual Server window may identify some servers by their DNS names and other servers by their IP addresses. This occurs because either reverse lookup is not set up or it is still resolving the names.
PolyServe Matrix Server Release Notes Bug Description 7785 Possible issue with adding a SQL instance to a Virtual SQL Server 22 Under certain conditions, an attempt to add a SQL instance to a Virtual SQL Server can fail with messages such as the following: Error: 17883, Severity:1, State: 0 The Scheduler 0 appears to be hung. 17113 : initconfig: Error 32 (The process cannot access the file because it is being used by another process.) opening ‘\master.mdf’ for configuration information.
PolyServe Matrix Server Release Notes Bug 23 Description 6. Download the setspn.exe utility from Microsoft and install it. 7. Create a registry SPN for SQL Server in active directory using the setspn command: 8. setspn -A MSSQLSvc/Host:port serviceaccount For example: C:\setspn>setspn -A MSSQLSvc/vsql2.px.ps.com 40006 Administrator Registering ServicePrincipalNames for CN=Administrator,CN=Users,DC=px,DC=ps,DC=com MSSQLSvc/vsql2.px.ps.
PolyServe Matrix Server Release Notes Bug Description 13175 Virtual SQL instance can use only one TCP port 24 Although SQL Server supports configuring more than one TCP port for a SQL instance, MxDB for SQL Server requires that a virtual SQL instance be configured with only one TCP port. 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.
PolyServe Matrix Server Release Notes Bug Description 13965 An attempt to delete a SQL Server 2005 instance may fail 25 An attempt to delete a SQL Server 2005 instance from a Virtual SQL Server may fail because of an erroneous timeout. A retry should succeed.
PolyServe Matrix Server Release Notes Bug 26 Description 14904, Error occurs when moving Virtual SQL Server to operation 16141 mode When you attempt to move a Virtual SQL Server from maintenance mode to operation mode, an error may prevent the operation from completing. Workaround. Press the Run button to continue the operation. (You may need to press the button a second time.) The operation should complete successfully with no adverse effects.
PolyServe Matrix Server Release Notes Bug Description 16276 Backup instance monitor can remain disabled 27 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.
PolyServe Matrix Server Release Notes 28 Matrix File Serving Solution Pack for CIFS The following issues affect the operation of the Matrix File Serving Solution Pack for CIFS. Bug 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.
PolyServe Matrix Server Release Notes Bug 29 Description The problem does not appear when the enable/disable commands are used in a controlled manual failback after the OS has finished booting. A subsequent failure of the active node will result in a correct failback without exhibiting the problem if the target node is already up and running in a stable state and is not in the process of booting.
PolyServe Matrix Server Release Notes Bug Description 13557 Avoid forcing Virtual CIFS Servers to new primaries 30 MxFS for CIFS 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.
PolyServe Matrix Server Release Notes 31 Bug Description 14064 MxFS for CIFS 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 MxFS for CIFS, such as at shutdown time. If MxFS for CIFS 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.
PolyServe Matrix Server Release Notes 32 Environment Issues The following environment issues affect the operation of Matrix Server. Bug Description 5571 Emulex HBAnyware fails to install Matrix Server requires that the HBAnyware package be installed on systems with Emulex HBAs. The HBAnyware installation sometimes fails on Windows 2003 systems. If you experience this problem, reboot the system and then retry the installation.
PolyServe Matrix Server Release Notes 33 Contacting PolyServe Please contact us if you encounter any installation, configuration, or usage issues with Matrix Server, or if you have any comments or suggestions. Contact information and the latest product information and documentation are available on the PolyServe Web site: http://www.polyserve.com Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
