Learn how to optimize the amount of disk space used by Symantec Endpoint Protection Manager (SEPM).
By default, Symantec Endpoint Protection (SEP) clients are configured to download content updates from their SEPM. These content updates are stored both in the SEPM database, and on disk in the SEPM install directory. The SEPM stores a full version the latest revision of each content type, and point-to-point deltas for past revisions of content. This minimizes the amount of disk space used in both the SEPM database and the SEPM install directory when storing multiple revisions of content.
Take care to balance the need for lower disk space usage with the possible bandwidth usage increases. If a client requests a delta content update the SEPM can't provide, it will be directed to download the full content update package instead, which significantly increases the network bandwidth used by content updates.
To optimize the amount of data stored in the SEPM database, see Manage log data in Endpoint Protection Manager.
Note: These settings will only affect the disk space usage of on the SEPM computer if the SEPM uses the embedded database, or a Microsoft SQL database installed to the same computer. SEPMs using remote SQL databases do not store reporting data locally.
During the installation or upgrade of the SEPM, client install packages are inserted into the SEPM database. Previous versions of the client install packages are not removed during this process. Once all computers in the environment have been migrated to a higher build, the client install packages for older builds can be safely deleted from the SEPM console to sve disk space in the SEPM database.
Note: If a client install package is assigned to any client groups, you must removed the package from the group(s) before you can delete the package.