ARM DB

Hello swg,
that sounds familiar to me.
1. do you log off the ARM clients, config as well? If not, the database increases and does not cleanup.
2. how is your retention setup in ARM?
3. Do you use the ARM website/datawarehouse?
4. check the sizes of your scans, i.e. our DFS scan is about 3,5 GB each night.

These are the main reasons for a growing ARM database.

Regards

Marcus

There were no DB changes in 2019.4 which I understand you observed the growth the first time?

It would be interesting to understand if it is the database or database log files that increase that much?

Also as customer, please don't hesitate to contact Solarwinds support to troubleshoot your environment.

Thanks,

Sven

Hi,

thanks for your help. I optimized archiving etc and also found a double scan after checking the scans another 100 times. Must have missed this one while scrolling down the scan list. 

Would be cool to also be able to use different colors for each kind of scan on top of the specific symbols. 

Going to do some more testings 

Oh and forgot to mention: I was indeed logged in all the time. In the client and in the config

Hi,

We have found our problem. We activated Exchange and File Logga without limits. Anything that could be logged was getting logged and the daily SQL maintanance task is now using too much space causing full disk and this task can't shrink afterwards due to none available space.

We do not want to extend the volume. Insted, we would like to delete entries inside the database.

Now, just a quick question: 

Exchange logga has been deactivated comepletely. File logga has been set up with less logging.

Is it save to delete 'loggaActionsFileRead' etc entries  inside the   PK_timline_events_id table   or would ARM crash? We want to get rid of these.

 Thanks