Symantec\Symantec Endpoint Protection Manager\Inetpub folder size is 11.5 gb, Can i clean the folder?

Follow the disk management procedure to make the space

Disk Space Management procedures for the Symantec Endpoint Protection Manager

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

Edit

Thread for the similar issue

https://www-secure.symantec.com/connect/forums/large-content-folder-sepm

Symantec Endpoint Protection Manager 12.1 database using a high amount of Hard drive space

https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space

Disk Space Management procedures for the Symantec Endpoint Protection Manager

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

thats the folder where all the definitions are stored by SEPM, the size is based on the number of content revisions you wish to store, by default its 30, you can limit it to 3 or 10 based on your needs, Check this article about how to modifiy it.

to reduce the number of content revision.

check this article

http://www.symantec.com/business/support/index?page=content&id=TECH104845

First off, what's the exact version you're running?

Hi,

Do not delete anything manually if you do so it will re-populate all the data.

How many content revisions are stored in the SEPM?

Recommendation are as per the following to set the number of revision.

• Fewer than 500 Clients : 3 revisions
• Between 500 and 1000: 10 revisions
• More than 1000: 30 revisions

If the folder size keep increasing continiously then there might be some clean up problem with purge definitions.

Repair the SEPM if possible.

Is this normal?

SEPM=SEP11RU7MP2

SEP Client=SEP11RU7MP2(7,000 Managed client)

2 SEPM+MS SQL Server2008 (Not replication Setting)

Content Types to Download=ALL Content

Languages to Download=English/Japanese

Number of content revisions to keep=30

Total Content Size=65.1 GB 

Database Size=25.5 GB 

 [1 SEPM]

[SQL Server Database]

Check these

https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space

You can decrease content revisions

Symantec Endpoint Protection Manager 12.1 database using a high amount of Hard drive space

https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space

Disk Space Management procedures for the Symantec Endpoint Protection Manager

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

I have already checked the article.

For the following reasons, I believe 30 revision is reasonable.

1. There is a managed client of 7,000 units or more
2. There is several percent off-line PC for around one week

The problem is the size of 1 content revisions.

Design mistake of "Delta File"?

All of your client are in local network or in remote location?

I have set the 5 revision and my client count is 4500. Not of any problem is occur.

When any client get online after long time it can update the full defintion.

It use the local network and so no chockup.

See the article when client to download a full definition file

When will a client download a full definition set from a Symantec Endpoint Protection Manager or Group Update Provider?

check the calculator 

https://www-secure.symantec.com/connect/downloads/sql-database-schema-information-and-database-planning

GUP does not use. 

> I have set the 5 revision and my client count is 4500. Not of any problem is occur.

I will study to reduce the number of revisions.

Thanks!
cooldude

For the time being, one single revision takes over 2 GB in the file system (Inetpub\content). One of the reasons is that SEP is saving both compressed and uncompressed versions of every revision. This cannot be changed.

The database only stores compressed revisions.

If you want SEPM to provide as many delta files as possible, you have to store a lot of content revisions.

To reduce space, you can do the following:

1. Reduce the number of revisions, e.g. from 30 to 15 in fushimi's case. Disadvantage: More full downloads. Nonetheless the best solution.
2. Upgrade to SEP 12.1 (good idea anyway). If you have a homogenous environment (only 32-bit or 64-bit operating systems), you can disable 32/64 bit content in 12.1. That saves one half of your content data. 
3. Not recommended (only in huge despair): Reduce the LiveUpdate interval from 4 hours (with this setting Symantec delivers 3 revisions in 24 hours) to daily and reduce number of revisions from 30 to 10 (fushimi's case). So you are still covering 10 days for delta file production. Unfortunately, your security is going downhill because the content is not as up-to-date as it should.

Not possible: Moving the Inetpub\content folder. Tricks with junctions or mount points don't work in the long run because SEPM will stumble at the next update.