Table of Contents
Advertisement
Appendix: Maintaining ePolicy Orchestrator databases
Performing daily or weekly database maintenance
Run this utility at least once a week. You can use SQLMAINT.EXE command-prompt utility to
perform routine database maintenance activities. It can be used to run DBCC checks, to dump
a database and its transaction log, to update statistics, and to rebuild indexes.
The simple procedure below does not cover everything you can do with SQLMAINT to maintain
your MSDE database, but rather the minimum you should do on your database each week. See
the Microsoft web site for additional information on SQLMAINT and what it can do for your
database.
Task
1
Type the following at the command prompt (the commands are case sensitive):
SQLMAINT -S <SERVER> -U <USER> -P <PASSWORD> -D <DATABASE> -RebldIdx 5 -RmUnusedSpace 50 10
-UpdOptiStats 15
Where <SERVER> is the name of the server, where <USER> and <PASSWORD> are the
user name and password of the user account, and where <DATABASE> is the name of the
database. The default database name is EPO_<SERVER> where <SERVER> is the name
of the ePolicy Orchestrator server.
2
Press ENTER.
Performing regular maintenance of SQL Server databases
Use SQL Enterprise Manager to perform regular maintenance of your SQL database.
The tasks below do not cover everything you can do to maintain your SQL database in SQL
Enterprise Manager. See your SQL documentation for details on what else you can do to maintain
your database.
Backing up the transaction log is not compatible with simple recovery. If you have multiple
databases with different recovery models, you can create separate database maintenance plans
for each recovery model. In this way you can include a step to backup your transaction logs
only on the databases that do not use the simple recovery mode.
Simple recovery mode is recommended because it prevents the transaction logs from swelling.
In simple recovery, once a checkpoint is complete, the transaction logs for the time before the
checkpoint are dropped from the active database. A checkpoint automatically occurs when the
backup is made. We recommend having a database maintenance plan that performs a backup
of the ePO database, together with "Simple Recovery". In this way, once a backup is successfully
created, the portion of the transaction log in the active database will be dropped as it is no
longer needed since a backup file exists.
Set the recovery model to simple. This is a one-time change to your SQL Server settings, and
it is very important. While MSDE databases install with the simple recovery model by default,
SQL Server installs using a different recovery model that doesn't allow the transaction log to
be cleaned as easily. This can cause the log to swell in size.
NOTE:
If you choose not to use simple recovery, then you need to regularly back up the
transaction log.
See the SQL or MSDE documentation for setting the recovery model to simple.
McAfee ePolicy Orchestrator 4.0.2 Product Guide
215
Advertisement
Table of Contents
