How to free up disk space on a Symantec Endpoint Protection Manager server
|Article:TECH163063|||||Created: 2011-06-23|||||Updated: 2014-01-02|||||Article URL http://www.symantec.com/docs/TECH163063|
The Symantec Endpoint Protection Manager (SEPM) server is running out of disk space.
1) Reduce the amount of logs stored in the database
Logs are one source of the database's large size. They can be configured on the following screen of the SEPM console:
Admin > Servers > (Local Site) > Edit Site Properties > Log Settings
It is possible to set the max number of log entries and max number of days. A log expires when either of the conditions are hit. So if you set Control Log Limit to 5,000 entries / 30 days. Then the logs will expire if there are more than 5000, or if they are 30+ days old. The most efficient method is to set the number of entries to all 9's, and keep them for as few an amount of days as needed. For example 99999 and 7 days
2) Increase the DB maintenance
It is possible to set the DB maintenance to run more often in the SEPM console at:
Admin > Servers > (Local Site) > Edit Site Properties > Database
3) Remove old client packages
Another option is to remove old client packages from the database. Note, although this saves room in the DB, it can incur additional bandwidth in case a client auto-upgrade task is performed.
When the "Auto-Upgrade" feature is used, (located under Clients > Install Packages, or by using "Upgrade Groups with Package under Admin > Install Packages), if the server has both the clients old packages, plus the clients new package, it can create a delta file that is much smaller than the original package. It then sends this delta file to all the clients instead of the original package. But if the old client packages are deleted from the database, this delta can not be created and the whole package is sent down, which means lots of network traffic, depending on how many clients have to be upgraded.
If there are not many clients much older than the newest deployed SEP release in the network, then it's safe to delete these old packages. If one is still planning to upgrade old clients, he may need to keep them stored in the SEPM database for a while.
To remove the old packages, open Admin > Install Packages > Client Install Packages.
Note:it is not possible to remove the latest packages, only older packages.
4) Reduce Content and Removing unzipped packages
It is possible to reduce the number of content revisions the sever keeps. This reduces the database size, but it will also reduce SEPM servers ability to make content deltas (similar to the client package deltas mentioned earlier, but content deltas are generally more important because they are used multiple times a day). This setting can be found under Admin > Servers > (Local Site) > Edit Site Properties > LiveUpdate > Disk Space Management for Downloads
It is strongly advised against setting this number any lower than 3. But if this number is set to 10 or higher, it might be required to lower it to reduce the database size.
What this number indicates is the number of AV definitions, IPS definitions, etc that are stored in the database. The greater this number is, the higher the chances are that the server will be able to create content deltas, especially if a client has been offline for long time. Usually three AntiVirus Content revisions are released per day, hence this setting should be set to at least "3".
It is recommended to retain a number of revisions higher than 10 so that any computers that disconnected on Friday night can still get a delta file on Monday morning.
The "Store client packages unzipped to provide better network performance for upgrades" option.
This option is right next to the content number. Disabling this option will reduce the diskspace SEPM uses, but it also disabled all deltas! So it is recommended that you do NOT disable this option.
Article URL http://www.symantec.com/docs/TECH163063