Specifications

Use server clusters for disaster recovery
If you require zero downtime if a hardware failure occurs you can cluster your ePolicy Orchestrator and
SQL servers. But, this requires additional hardware and increases the cost of implementation.
You might chose to only cluster the SQL Servers, which is a more common option, and SQL should
have zero downtime. If the McAfee ePO server fails due to hardware failure you can reinstall its
operating system, which only takes a few hours, and point the McAfee ePO server to your SQL
database. As long as the SQL server is clustered there is minimal value gained if you cluster the
McAfee ePO server. McAfee does not recommend clustering the McAfee ePO server because of the
increased hardware investment and it increases the complexity of the ePolicy Orchestrator
implementation. But it does work.
The full restore procedures are described in the KnowledgeBase article KB66616.
Use cold and hot spares on one physical site
If your large production environment requires minimal downtime you can use a cold or hot spare
McAfee ePO server. The spare server is running a clean installation of ePolicy Orchestrator and pointing
to your SQL database.
If you only have one physical site, you cluster your SQL server, and then if your McAfee ePO server
fails you can simply change the IP address of the spare McAfee ePO server to the IP address of the
failed McAfee ePO server. This is completely transparent to all of the agents and provides the least
downtime in a disaster situation.
You must have a good SQL database backup for this to work.
The full restore procedures are described in the KnowledgeBase article KB66616.
Use cold and hot spares on two physical sites
If you want total disaster recovery use two physical sites with a primary site and a secondary site.
Your primary site should have a clustered SQL Server and a single McAfee ePO server. The secondary
site should have a hot or cold spare McAfee ePO server and an SQL database. You can use SQL
replication or SQL Log Shipping to copy the ePolicy Orchestrator database from the primary site to the
secondary site's SQL server on a nightly or weekly basis during non business hours. Then you need to
make sure your secondary McAfee ePO server is pointing to your secondary SQL server. See the
Microsoft article Types of Replication Overview for details.
14
Disaster recovery
Use server clusters for disaster recovery
108
McAfee
®
ePolicy Orchestrator
®
4.0 and 4.5 Best Practices Guide