PolyServe Matrix Server Release Notes PolyServe Matrix Server 3.6.
Copyright © 2004-2008 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.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Implementation Changes in Matrix Server 3.6.0 . . . . . . . . . . . . . . . . . . . . 2 Upgrades to Matrix Server 3.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Supported Filesystem Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Filesystem Implementation Differences . . . . . . . . . . . . . . . . . . . . . . . . . . .
PolyServe Matrix Server New Features in Matrix Server 3.6.0 Matrix Server 3.6.0 includes the following new features. Security features: • Single sign-on. Matrix Server now uses AD single sign-on semantics to authorize users attempting to access the matrix. • Role-Based Security Control. You can create roles, define the operations that are allowed or denied for each role, and add specific user or group accounts to the roles.
PolyServe Matrix Server Release Notes 2 • New Matrix Server SNMP service. This service provides an SNMP extension agent and MIBs for retrieval of all matrix-wide state and status information. PolyServe Management Console features: • New Installed Software viewer that lists all of the PolyServe software currently installed on the system. • Progress task bar that displays progress indications when you initiate a task on the console. Implementation Changes in Matrix Server 3.6.
PolyServe Matrix Server Release Notes 3 • The mxlogger command has been replaced by the mx matrix log command. Upgrades to Matrix Server 3.6.0 It is important to upgrade all nodes in the matrix within a short time frame. We do not recommend running the matrix for an extended period of time with only some of the nodes upgraded to 3.6.0. This release introduces a new configuration data repository and a new logging facility that do not become fully functional until all nodes are upgraded.
PolyServe Matrix Server Release Notes 4 • 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.
PolyServe Matrix Server Release Notes 5 • File encryption and compression. This behavior is consistent with the FAT filesystem. • Automatic generation of DOS 8.3 filename entries for “long” filenames. Name tunneling is also not supported. • Hard links. • System ACLs and filesystem auditing. • NTFS change journal. As a consequence, file replication services (FRS) cannot be used. Content indexing is also affected.
PolyServe Matrix Server Release Notes 6 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 7 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 8 Open Issues and Workarounds The following open issues affect PolyServe Matrix Server, MxDB for SQL Server, including the Migration Utility, and MxFS for CIFS. Matrix Server The following issues affect Matrix Server.
PolyServe Matrix Server Release Notes 9 Bug Description 4301 Filesystem mounts may disappear temporarily while a node is booting While a node in the matrix is booting, the PolyServe Management Console can show filesystem mounts disappearing and then reappearing on other nodes. This is an artifact of the matrix responding to a new node joining the matrix and causes no harm. 5519 SNMP dies on QLogic SANbox2 FC switches In a matrix with a QLogic SANbox2 FibreChannel switch, SNMP can die periodically.
PolyServe Matrix Server Release Notes 10 Bug Description 5838 Reinstalling Matrix Server with an evaluation license requires new configuration A Matrix Server configuration created with an evaluation license cannot be used if Matrix Server is reinstalled with an evaluation license. When uninstalling Matrix Server, do not check the “Keep the existing Matrix Server configuration” option. This option prohibits the use of the evaluation license provided with the Matrix Server distribution.
PolyServe Matrix Server Release Notes Bug Description 7519 Third-party MPIO software must discover devices 11 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.
PolyServe Matrix Server Release Notes Bug 12 Description 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. 8290 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.
PolyServe Matrix Server Release Notes Bug Description 9326 psfscheck incorrectly reports attribute errors 13 When psfscheck is run on a filesystem created on Matrix Server 2.5 or earlier, it may report an error such as the following: Pass 3: Checking semantic tree directory 0 8334 has broken attribute 0x0 You can safely ignore this message. The attribute bit was not set in Matrix Server 2.5 and earlier releases. (If psfscheck is run in a mode other than read-only, it will fix the error.
PolyServe Matrix Server Release Notes 14 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 12924 Add or Remove Programs appears to hang 15 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.
PolyServe Matrix Server Release Notes Bug Description 13411 Synchronized bookmarks do not work with secondary interface 16 If you are unable to connect to the matrix using the primary network interfaces on your servers because of the network infrastructure or a firewall, the “Synchronize Server Bookmarks Automatically” option should be disabled. If it is not disabled, bookmarks that contain addresses on a secondary interface will be replaced with the unreachable primary interface.
PolyServe Matrix Server Release Notes Bug Description 13996 mx fs destroy partially destroys snapshots 17 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.
PolyServe Matrix Server Release Notes Bug Description 15437 Memory-mapped sparse files are not supported 18 Attempts to create a memory-mapped sparse file or to mark an existing memory-mapped file as sparse will fail with a “Status not supported” error. 16442 Roles can allow users to run scripts as LocalSystem A role granting create or modify rights for monitor or notification scripts allows the user to run the scripts as LocalSystem, effectively allowing the user to be a machine local administrator.
PolyServe Matrix Server Release Notes Bug 19 Description Workaround. The preferred workaround is to uninstall Matrix Server (saving the configuration) and then reinstall it. If this is not possible, open Windows Explorer and go to \bin in the Matrix Server installation directory, double-click on mxsnmp_add.reg, and then reboot. 17660 Matrix description cannot be reset when Matrix Server is not running The matrix description is set when you initially configure the matrix.
PolyServe Matrix Server Release Notes Bug Description 18313 MxUpgrade_SQL-3.6.0 upgrade tool must be uninstalled 20 Before MxDB for SQL Server is upgraded to the 3.6.0 release, you will need to install and run the MxUpgrade_SQL-3.6.0 tool to upgrade your Virtual SQL Servers. This tool must be uninstalled after it is used because it conflicts with the user authorization mechanisms used by Matrix Server 3.6.0. If a Virtual SQL Server was not upgraded before the 3.6.
PolyServe Matrix Server Release Notes Bug 21 Description This situation can also occur because interfaces generated their own addresses automatically. These will all be in the 169.254.0.0 (“zeroconf”) IP subnet. If you want to use these interfaces on an Ethernet segment with no DHCP server (say, for the cluster’s private networks), manually assign addresses in private IP subnets (for example, 192.168.0.0) to them and/or disable the extra interfaces.
PolyServe Matrix Server Release Notes Bug Description 19875 Custom community strings are not supported with fabricbased fencing 22 An issue discovered in PolyServe Matrix Server 3.6.0 prevents the use of custom community strings with fabric-based fencing. For new 3.6.0 installations and upgrades to 3.6.0, clusters configured with fabric-based fencing must have both a read/write community string named “private” and a read-only community string named “public”.
PolyServe Matrix Server Release Notes Bug Description 4046 Virtual SQL Server backup instances may appear in Enterprise Manager 23 When the Instance Aliasing feature is not used, MxDB for SQL Server does not keep the backup instances from appearing in the SQL Server Enterprise Manager. These backup SQL Server instances are not active and should not be selected for operations. Be sure to select the active SQL Server instance from within Enterprise Manager.
PolyServe Matrix Server Release Notes 24 Bug 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.
PolyServe Matrix Server Release Notes Bug Description 11359 Registry changes can be lost when a Virtual SQL Server running on a backup node is placed in maintenance mode 25 If a Virtual SQL Server is running on a backup node when it is placed in maintenance mode, the virtual registry used by MxDB for SQL Server will also be on the backup node. Any changes made to the original registry on the primary node will not be updated to the virtual registry and will be lost.
PolyServe Matrix Server Release Notes Bug 26 Description Error String : SQL Server Setup failed to modify security permissions on WMI namespace \\.\root\Microsoft\SqlServer\ServerEvents\I5. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that the WMI namespace exists on the destination drive.
PolyServe Matrix Server Release Notes Bug Description 14925 SQL Server installer may incorrectly report successful installation of hotfix /Service Pack 27 If you attempt to install a 64-bit SQL 2005 hotfix/service pack on a 32-bit SQL instance and the node includes both 32-bit and 64-bit instances, the installer will fail silently and continue to update all 64-bit common components. The hotfix process will return a success status even though the 32-bit database engine is not updated.
PolyServe Matrix Server Release Notes Bug Description 16276 Backup instance monitor can remain disabled 28 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 Bug Description 17160 Undo operation does not remove user data files 29 If an attempt to create a Virtual SQL instance fails, an undo operation is run to undo any tasks that were completed and return the Virtual SQL Server to its original state. However, the undo operation does not remove the user data files that were copied during the attempt to create the Virtual SQL instance. Workaround.
PolyServe Matrix Server Release Notes Bug Description 18766 Forcefully terminating MNI leaves process running 30 When the MNI GUI or CLI is forcefully terminated (for example, with Ctrl-C), the backend process mssql_mni_cgi.exe continues to run. Workaround. Run taskkill /im mssql_mni_cgi.exe on the affected nodes.
PolyServe Matrix Server Release Notes Bug Description 18858 Failed 32-bit upgrade reported as succeeding 31 When an attempt is made to install a 32-bit version of SQL Server 2005 SP1 on a 64-bit instance, the installer can incorrectly report that the installation was successful. Review the SQL Server setup log to confirm that all components are upgraded successfully.
PolyServe Matrix Server Release Notes Bug Description 19304 Node being monitored by Procmon may crash during installation of SQL instance 32 If the SQL Server 2000 installation media is on a PSFS filesystem, a node monitored by Procmon may crash during an installation of a SQL Server instance on the node. Workaround. Use Filemon or Regmon to monitor the node.
PolyServe Matrix Server Release Notes Bug 33 Description Workaround. Open the SQL Instance Aliasing window and click the Advanced button. If “Enable the PolyServe SQL Browser Service” is already checked on the Advanced Setting dialog, uncheck it and click OK, and then click Apply on the SQL Instance Aliasing window. Now reopen the SQL Instance Aliasing window and repeat this step, this time checking the “Enable the PolyServe SQL Browser Service “option.
PolyServe Matrix Server Release Notes Bug Description 19627 Character limitations for installation credentials 34 The following characters are allowed when specifying the user name, password, and domain to be used for a SQL Server installation or upgrade. User name: a-z, 0-9, underscore, space Password: a-z, 0-9, underscore Domain: a-z, 0-9, dash, period, open and close parentheses The maximum number of characters that can be specified for a user name, password, or domain is 30.
PolyServe Matrix Server Release Notes 35 MxFS for CIFS The following issues affect the MxFS 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. This situation can cause unexpected failover behavior or can cause a File Share to point to the wrong resource. Workaround.
PolyServe Matrix Server Release Notes Bug 36 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 37 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 38 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 Bug Description 16049 Virtual CIFS shares are not available after Windows Server 2003 Service Pack 1 is installed 39 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.
PolyServe Matrix Server Release Notes Bug Description 7837 Content Indexing can cause ClusterPulse problems The Content Indexing Service can cause ClusterPulse connections to be dropped. Workaround. Consider discontinuing the Content Indexing Service. Compatibility Information PolyServe is continually expanding its supported hardware and operating system configurations. For the latest information, check the PolyServe Web site: http://www.polyserve.
