Maintaining the database
|Article:HOWTO55337|||||Created: 2011-06-29|||||Updated: 2011-12-16|||||Article URL http://www.symantec.com/docs/HOWTO55337|
After you install Symantec Endpoint Protection Manager, the management server starts to slow down after a few weeks or a few months. To improve the management server performance, you may need to reduce the database storage space and schedule various database maintenance tasks.
Table: Database management tasks
Schedule regular database backups
You should schedule regular database backups in case the database gets corrupted.
Optionally, to prevent an automatic sweep of the database until after a backup occurs, you can manually sweep data from the database.
Schedule database maintenance tasks
You can speed up the interaction time between the management server and the database by scheduling database maintenance tasks. You can schedule the management server to perform the following maintenance tasks immediately or for when users are not on the client computers.
Periodically check the database file size
If you use the Microsoft SQL Server database rather than the embedded database, make sure that the database does not reach the maximum file size.
Calculate the database storage space that you need
Before you can decide how to reduce the amount of storage space, calculate the total amount of disk space that you need.
The database storage is based on the following factors:
For more information on how to calculate the hard disk space you would need, see the Symantec white paper, Sizing and Scalability Recommendations for Symantec Endpoint Protection.
Reduce the volume of log data
The database receives and stores a constant flow of entries into its log files. You must manage the data that is stored in the database so that the stored data does not consume all the available disk space. Too much data can cause the computer on which the database runs to crash.
You can reduce the volume of log data by performing the following tasks:
Export log data to another server
For security purposes, you might need to retain the number of log records for a longer period of time. To keep the client log data volume low, you can export the log data to another server.
Create client installation packages with only the protection that you need
The more protection features that you install with the client, the more space that the client information takes in the database. Create the client installation package with only the appropriate level of protection the client computer needs. The more groups you add, the more space the client information takes in the database.
Use the Group Update Provider to download content
If you have low bandwidth or more than 100 client computers, use the Group Update Provider to download content. For example, 2,000 clients using a Group Update Provider is the equivalent to using four to five management servers to download content.
To reduce disk space and database size, you can reduce the number of content revisions that are kept on the server.
Restore the database
You can recover a corrupted database by restoring the database on the same computer on which it was installed originally. You can install the database on a different computer.
The information in the database is stored in tables, also called a database schema. You might need the schema for specialized reporting. For more information, see the Symantec Endpoint Protection Manager Database Schema Reference from the Symantec Endpoint Protection documentation site.
Article URL http://www.symantec.com/docs/HOWTO55337