Video Screencast Help

Reducing Database Size

Created: 14 Feb 2013 | 9 comments

We are prepping for migration from SEP 11 to SEP 12 and are working on cutting down the size of the external SQL database. Currently it has grown to over 60GB and about 45GB of that looks like reputation data. I would love to purge some data out to get it to a more manageable size. What can I do to reduce it and is there any tools to purge data? I am thinking of turning off the application upload but I don't know if that will remove anything. Some of this goes back years and may not be of any use. What other tips for not collecting tons of additional info or cleaning it up? Our logging requirements are 7 months (6 months + current month) and that has already been set.

 

My experience with SEP so you can answer at the right level: Pretend like I just started managing our SEP environment 3 weeks ago and took the SEP 12 basic admin class last week and have little experience on this product. Actually...don't pretend because that is true.

Comments 9 CommentsJump to latest comment

.Brian's picture

Do you send your SEPM data to a syslog?

How many content revisions are you currently keeping?

Managing log data in the Symantec Endpoint Protection Manager (SEPM)

Article:TECH153987  |  Created: 2011-02-22  |  Updated: 2012-08-26  |  Article URL http://www.symantec.com/docs/TECH153987

 

Changing the log settings to reduce the size of the database.

Article:TECH105238  |  Created: 2008-01-27  |  Updated: 2010-11-02  |  Article URL http://www.symantec.com/docs/TECH105238

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

PFUNK2803's picture

Log settings look fishy. 1000000 logs from the client? Also every application is being sent to db...so if I turn this off does it delete that data? Also do I need to keep every infection event...seems like the guy who set this up went a little crazy.

Attached screenshots!

gensettings.PNG db.PNG contentrevs.PNG logsettings.PNG
.Brian's picture

Wow! those are definitely set on the generous side. I guess it all depends on what your company policy is.

Do you really need to keep trac of every app that the clients run? If not, uncheck it

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Ashish-Sharma's picture

How to shrink the embedded database for the SEPM using the Dbunload tool

 

Article:TECH104278 | Created: 2008-01-26 | Updated: 2012-05-23 | Article URL http://www.symantec.com/docs/TECH104278

 

Disk Space Management procedures for the Symantec Endpoint Protection Manager

http://www.symantec.com/docs/TECH96214

Configuring the number of content revisions kept by the SEP client 11.x (cachentriesex)

http://www.symantec.com/business/support/index?pag...

Maintaining the database

http://www.symantec.com/docs/HOWTO55337

Changing the log settings to reduce the size of the database.

http://www.symantec.com/docs/TECH105238

Thanks In Advance

Ashish Sharma

 

 

.Brian's picture

i believe dbunload is only for embedded, not sql

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

PFUNK2803's picture

So we have done a ton of work and removed a few GB from the database...however we are still in the 58GB range. I want to get rid of the application scanning data which is around 45GB. The only solution we have seen so far is to truncate the DB for the SEM_APPLICATION and the COMPUTER_APPLICATION tables. Either that or bring down the DB and rename the tables and create new ones with no data. Anyone have experience with getting rid of these? Anyone actually ever able to remove this data?

PFUNK2803's picture

Not embedded this is for SQL. 99.99% of all solutions on the forums and tech articles refer to the embedded database which is built around SEP and all the tools and settings refer to the embedded database. .01% of all solutions refer to the SQL database and have no information on reducing the size of the appliation scanning tables.

Note: 80% of all statistics posted on forums are made up by the poster. This happens 63% of the time while 90% of the readers realize this.

Rafeeq's picture

How many clients you have in your network? check the xls file , lets see if thats normal or way more than the limit

https://www-secure.symantec.com/connect/downloads/...