Veritas Volume Manager KM for PATROL

Release Notes v2.4.00

Home  Previous  Next

What's new

Full compatibility with BMC ProactiveNet Central Monitoring Administration, a feature supported by BMC ProactiveNet Performance Management version 9.0.00.
Veritas Volume Manager KM for PATROL now supports Veritas Storage Foundation v6.x.
Veritas Volume Manager KM for PATROL now supports Microsoft Cluster.
In order to easily identify which step the initial discovery is processing, the setup icon now reflects the successive phases:
Upgrading (PATROL Classic Console only)
Loading (Commands)
Initializing (KM paths. Missing path is now specified in the System Output Window)
Discovering (Monitored application)
Cleaning (Temp files)
Validating (Application paths)

Changes and Improvements

The global performance of Veritas Volume Manager KM for PATROL has been improved.
All collectors are now automatically refreshed as soon as the KM configuration and the initial discovery are complete.
The default number of instances of Application Classes has been removed. This information must be defined by the user. When set to 0, the monitoring of a specific Application Class is not performed.
The default log scan limit was increased to 500 KBytes.
The KM-related messages that are sent to the System Output Window (SOW) are also logged to the VVM.log file available under <PATROL_HOME>/log.
When one or more required paths are missing, the setup instance label will now indicate which paths are missing. A message will also be displayed in the System Output Window.
The VVMRemoveTempFiles parameter was removed.
All previous pconfig variables available under /VVM are now split to /VVM and /Runtime/VVM while upgrading the KM.
The polling interval can now be modified for the server discovery to detect server changes and cluster fail over faster.
The time during which the debug information is logged can now be set by the user.
The KM Status report now provides collector/discovery collection time information as well as additional performance details.

Fixed Issues

With some Windows platforms the Debug KM Command was prompting for an OS login to turn the debug on.
The VVMDaemonState parameter was set to "Not Running" when the PATROL Agent could not fork processes, which resulted in invalid alarms on the VVMDaemonStatus parameter.
A problem occurring when the KM triggers certain events would lead to the PATROL Agent to crash without displaying any error message.
The KM was not properly managing the online thinrclm shared status for VVMDiskdeviceStatus parameter leading to triggering erroneous warning. The online thinrclm shared status is now properly recognized as an online state.