|
This section lists new features, changes, improvements and bug fixes that have been implemented since the release of version 2.7.00 of the product.
Changes and Improvements
| • | It is now possible to set any instance limit to 0 for disabling a component. |
| • | Two new states were added to the TSMDomainState parameter, both alarms are triggered through TSMDomainStatus by default: |
| ▪ | Inactive domains are monitored by setting TSMDomainState to “Inactive” |
| ▪ | If no jobs were started as per the next backup start time, TSMDomainState will be set to “Not Started”. |
| • | Faster KM failover in clustered TSM environment. The server discovery interval is reduced to 40 seconds (formerly 5 minutes), which speeds up detecting server level changes as well as clustered TSM server failover. |
| • | The KM Status report now provides collector/discovery collection time information as well as additional performance details. This report is stored under PATROL_HOME/lib/TSM/km_status.txt on all managed nodes. |
Fixed Issues
| • | When configuring the KM from BPPM CMA, the debug logs were kept locked on Windows managed nodes even after the debug was turned off. The debug logs can now be removed without an Agent restart. |
| • | The exclude expression filters in BPPM CMA configuration GUI did not take effect without include filters. This is now corrected to operate independently. |
| • | When upgrading the KM from version 2.6.x to version 2.7.x, some of the instance level KM configuration data stored in the PATROL configuration were not upgraded. |
| • | Tape libraries were not correctly discovered and their summary parameters were not set properly. |
| • | Parameters of inactive and completed jobs were updated during each job collection cycle, if their job end time was not reported. This is now corrected to be ignored as soon as they change to an inactive state, like “Missed”. |
|
