Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
Contents of the 3.6.1 release
This release provided compatibility with HP PolyServe Matrix Server 3.6.1 and included the following
new features:
• High availability support for Microsoft Distributed Transaction Coordinator (MS DTC).
• High availability support for Microsoft SQL Server 2005 Analysis Services (SSAS).
See the HP PolyServe Software for Microsoft SQL Server Installation and Administration Guide for
information about configuring MS DTC and SSAS for failover.
The following implementation changes have also been made in this release:
• The log files for HP PolyServe Software for Microsoft SQL Server are now rotated when a file
reaches 10 MB.
• The Multi-Node Installer and Multi-Node Upgrade Wizard no longer validate the user credentials
supplied for an installation. Instead, the credentials are passed to the operating system and under-
lying services for validation.
• A new ––force option is available for the mx vsql move command. The option causes the
move to complete even if the operation encounters an error.
• The mx vsqlinstance status command now reports whether Virtual SQL instances are in
operational or maintenance mode.
The following issues were corrected in this release:
• Defect 11350. If the Update Virtual SQL Server dialog was opened and the user clicked OK
without making any changes, the Virtual SQL Server was updated.
• Defect 14126. The label for the Virtual SQL Server resource was incorrect on the Edit Filter dialog,
which is used to filter the Applications tab. This label has been changed to “SQL.”
• Defect 15728. The search option did not work when adding a new SQL user from the node on
which the Virtual SQL instance was active.
• Defect 16256. The Applications tab did not indicate whether MS DTC was enabled on a Virtual
SQL Server.
• Defect 16308. The installer did not verify that a virtualized SQL instance was in maintain mode
before installing a service pack or hotfix.
• Defect 16370. The -–operational and --maintenance flags provided with the mx vsql
status command did not work.
• Defect 16571. A log message from the Multi-Node Installer caused Matrix Server to fail when the
log was viewed through the Matrix Server "View Log" command.
• Defect 18012. The PolyServe Management Console dialogs used to configure Instance Aliasing
did not validate instance and server names.
• Defect 18081. A Virtual SQL instance did not start and a probe error reported that the instance
was already running.
• Defect 18823. When the Instance Aliasing file contained an invalid record, the error message
that was generated did not include the invalid record.
• Defect 18834. When multiple ports were assigned to a SQL instance, Instance Aliasing did not
construct the browser string correctly.
• Defect 19103. Instance Aliasing did not prevent the creation of duplicate legacy IP addresses
associated with different “real” IP addresses.
• Defect 19194. The Multi-Node Installer did not sort the list servers available for an installation.
• Defect 19196. When the autostart option was selected for Analysis Services or Reporting Services
in the Multi-Node Installer, the corresponding account was not automatically selected.
4
...