We have an old NSM setup for legacy kit. The mdb and mdb.log files keep growing and filling the disk. What can we do to maintain the mdb and the log?
I'm moving this question to the NSM sub-group of UIM.
Try deleting the unused objects (if there are any) in MDB and see if it works?
How would I do that?
Logging into 2d map (if available)?
There isn't much in the 2dmap, and what is there, is all set to unmanaged.
This NSM server is mainly used for servicedesk integration and runs the CA Alert Manegement System (AMS). It may be this that's filling the DB.
It sounds like your data_engine is failing in the maitenance processes.
this is usually due to indexes being too fragmented.
What is your back end SQL server type and version?
What is your data_engine version?
This will help us determine what is the next couse of action.
You can check out these KB articles.. They have been relevent for this type of issue for a long time.
Verifying that data_engine is deleting old raw and - CA Knowledge
Query to See the Most Current QOS in the DataBase - CA Knowledge
What does the alarm "You have exceeded your QoS li - CA Knowledge
How does data_engine maintenance and retention wor - CA Knowledge
This post is about NSM 3.1, not Nimsoft. So we don't have a data_engine.
Very sorry for the confusion!!!
In general when the visibility and category selected is CA Unified Infrastructure Management the responses will be from the perspective of UIM. To have people who are part of the NSM category view this select CA NSM.
Noted, I thought however, that NSM still fell under the Infrastructure Management product area.
Retrieving data ...