Backup And Restore Epolicy Orchestrator Databases; Changing Sql Server Information - McAfee EPOLICY ORCHESTRATOR 4.5 Product Manual

Appendix: Maintaining ePolicy Orchestrator Databases

Backup and restore ePolicy Orchestrator databases

Backup and restore ePolicy Orchestrator databases
McAfee recommends that you back up ePolicy Orchestrator databases regularly to protect your
data and guard against hardware and software failure. If you ever need to reinstall the server,
you might need to restore from a backup.
How often you back up depends on how much of your data you are willing to risk. Some possible
approaches include:
• Back up your database at least once a week.
• If you have made many changes to your deployment, you might want to back up daily.
• To mitigate bandwidth demands during regular business hours, you might schedule automated
nightly backups.
• To further balance the load, you might perform incremental daily or nightly backups, and a
full weekly backup each week.
Save the backup copy to a different server than the one hosting your live database. If your
database server crashes, you don't want to lose your backup too.
Performing regular backups provides the ability to restore your database if that should ever
become necessary because of software or hardware failure, or because of an upgrade to server
or database server hardware.
For information on backing up and restoring your SQL database, see:
• Microsoft documentation for the management tool appropriate for the database you are
using.
• McAfee KnowledgeBase article KB52126.

Changing SQL Server information

Use this task to edit the SQL Server connection configuration details. This is useful to make
changes to the user account information in ePolicy Orchestrator when you make changes to
the SQL Server authentication modes in SQL Server Enterprise Manager or SQL Server
Management Studio. Do this if you need to use a privileged SQL user account for added network
security.
CAUTION: Changing the database settings to point this ePO server to an ePO database that is
not an exact match can cause the removal of product extensions and the loss of all associated
data. McAfee recommends performing this task only to change the configuration of your existing
database.
You can use the web page at
configuration file information that used to be done with the Cfgnaims.exe file.
Things to know about this page:
• Authentication — If the database is up, this page uses normal ePO user authentication and
only a global administrator can access it. If the database is down, a connection is required
from the system running the SQL server.
• The ePO server must be restarted for any configuration changes to take effect.
• As a last resort, you might edit the configuration file by hand (
directory>server\conf\orion\db.properties
then using the config page to re-edit the db config, which stores the encrypted version of
the passphrase.
286 McAfee ePolicy Orchestrator 4.5 Product Guide
https://servername:port/core/config
), putting in the plaintext password, starting the server,
to adjust any database
<ePO installation