McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC, Product Manual

Page: 311 / 328

A
Appendix: Maintaining ePolicy
Orchestrator Databases
Your databases require regular maintenance to promote optimal performance and to protect your data.
Use the Microsoft management tool appropriate for your version of SQL:
SQL Version Management Tool
SQL 2005 SQL Server Enterprise Manager
SQL 2008 SQL Server Management Studio
SQL Express SQL Server Management Studio Express
Depending on your deployment of McAfee ePO software, plan on spending a few hours each week on
regular database backups and maintenance. The tasks discussed in this section should be performed
on a regular basis, either weekly or daily. However, these are not the only maintenance tasks
available. See your SQL documentation for details on what else you can do to maintain your database.
Contents
Perform regular maintenance of SQL Server databases
Backup and restore ePolicy Orchestrator databases
Changing SQL Server information
Perform regular maintenance of SQL Server databases
There are two modes available for maintaining your Microsoft SQL Server (SQL Server) databases:
Simple Recovery Mode and Full Recovery Mode.
When SQL Server backs up the ePolicy Orchestrator server in simple recovery mode, it marks the
backed-up transaction log records as inactive; also known as truncating the log. In this way, new
operations written to the transaction log can reuse that space by overwriting the inactive entries. This
helps prevent the log size from growing.
In full recovery mode, if the transaction log is not periodically backed up, it continues to grow. The
transaction log will grow until it consumes all available disk space. Therefore, it is important to
perform regular transaction log backups when using full recovery mode to keep the size of the
transaction log in check.
In simple recovery mode, SQL Server truncates the transaction log when a check point occurs, and
records are flushed to disk. This frees up space internal to the transaction log file. The transaction log
therefore does not grow in size to any meaningful extent, as long as there is enough space available
for the current open transactions. This means that in simple recovery mode, there is no need to back
up the transaction log, just a regular full backup of the ePolicy Orchestrator database. In the event of
a disaster, you can only recover to the last full backup. All changes that occurred since the last full
backup are lost.
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide 311