This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
TrueSight Capacity Optimization Capacity Optimization
This Solution does explain settings to use in the Moviri SCOM Extractor when recovering data to close data gaps.
ETL is not performing well in recovery mode.
The SCOM ETL is constantly collecting data, this Solution explain how to close a gap and recover data, when the ETL was not able to connect for some time to the SCOM database and has some data gaps.
In the SCOM ETL open the Run Config go to SCOM - Settings it is recommended to create a new Run config for the Recovery Job, modify the following settings:
- Default last counter (YYYY-MM-DD HH24:MI:SS, -x for x days back) (*) , the default is -1
- Recovery mode active , the default is No
- Since (YYYY-MM-DD HH24:MI:SS), only displayed when Recover Mode is Yes
- To (YYYY-MM-DD HH24:MI:SS), only Displayed when Recovery Mode is Yes.
The default last counter should be set to the Date and Time when the recovery of the data should happen, the Since and To fields cover the range from the start to the end.
The SCOM environment could be very large and it could be possible that a recovery of 24 hours is to much in a single batch, this may lead into a out of exception when the ETL runs, or the ETL may run a long time.
If a large SCOM database environment is used, reduce the time frame to recover data to 12 our even to 6 hours and don't use a full day. You may need to run multiple jobs to close the gap of data if this is for a longer period of time.