The support organization would like review errors in the trace.log for the Dashboard Server for up to a week ago but the logs are only available for about three days worth. What could be changed within IBM Tivoli Business Service Manager V6.1 (TBSM) Logs and Trace to fix this issue?
The trace Jog file on the IBM Tivoli Business Service Manager V6.1 (TBSM) Dashboard Server has been taking a huge amount of write time for the hard drive. What could be changed to free up more write time for the TBSM components?
In IBM Tivoli Business Service Manager V6.1 (TBSM) fail-over implementation, when configuring a secondary TBSM Data Server, which Netcool/OMNIbus should be configured to be used as its Event Source?