ESETRADB database over 1.4GB

Discussion in 'Other ESET Home Products' started by JoeyJoeJoe, Jun 15, 2010.

Thread Status:
Not open for further replies.
  1. JoeyJoeJoe

    JoeyJoeJoe Registered Member

    Joined:
    Oct 22, 2009
    Posts:
    63
    Our installation base for ESET is around 250 clients.

    The ESETRADB.mdf file is about 1.4GB and growing.

    Is that typical? It seems incredibly large for such a small ESET deployment.

    I'm curious about how large other ESET databases are.

    Thanks,
    JJJ
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Mine is 30MB for 634 clients. These are my retention settings:

    nod32.png

    e: I also set it so only the last 25 client events are logged in the advanced settings, since I really don't care when a client updates or sends statistical info. That's probably the culprit.
     
  3. JoeyJoeJoe

    JoeyJoeJoe Registered Member

    Joined:
    Oct 22, 2009
    Posts:
    63
    That's basically my server settings as well. I took a look at the tables in ESETRADB and found FirewallLog alone had over 980MB alone reserved.

    Going to cut back my logs to 7 days and run cleanup against the DB.
     
  4. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Check my edit. It's likely the client events that are doing it.

    For reference, I have about 19k entries logged in the event log section.
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    If it's firewall logs that keep growing, I'd strongly recommend remedying the cause of the problem on the problematic client(s) so that the clients don't produce too many errors in the log.
     
Thread Status:
Not open for further replies.