Kaseya Community

Database is growing rapidly!

  • Recently our database started getting very large. We'd changed things to retain logs for 90 days for servers, and we think that's part of what created the growth, coupled with the fact that lots of our client's servers were getting Event ID: 1041 and Event ID: 1023. (Hence my recent requests for scripts... Thanks by the way!)

    So now that the error messages and alerts are under control, we decided to look into the database size. It's still growing. It's growing about .6GB every day!!

    We changed the log retention to 60 days, hoping it would cut down on some of the old info, but it doesn't seem to have made much of a difference in size or rate of growth.

    Where should we be looking for things that will make the database grow like this, and how large is TOO large for a single server with 1300 end points...?

    Thanks in advance for any advice!


    Legacy Forum Name: Database is growing rapidly!,
    Legacy Posted By Username: Matt.Conlon
  • My first thought would be syslog. Are you caturing any syslog data?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: boudj
  • Yes, but we always had been.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Matt.Conlon
  • The archiving function may not be working. We had this happen to us and had to get Ksupport to fix it.

    You can check the following tables in the Kaeya database
    monitorCounterLog????????
    monitorProcessLog????????
    monitorServiceLog????????
    monitorSnmpObjectGet????????
    ntEventLog????????

    if ???????? is older than what your archive age is set to then log a support request with Ksupport.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: eddy@dgs.com.au
  • Check into what Eddy said. But also, keep an eye on syslog. It can suddenly go crazy and grow like bananas!

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: boudj
  • FYI we had a similar issue recently and even after you remove/archive the data the DB itself has to be shrunk manually in SQL with Kaseya offline.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: jilderton