Loading...

Knowledge Center


ePolicy Orchestrator Sustaining Statement (SBC1410101) - ePO and SQL AlwaysOn feature
Technical Articles ID:   KB83860
Last Modified:  10/17/2019
Rated:


Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Summary

This document is a response to a request involving ePO releases and support for the SQL AlwaysOn feature. McAfee analysis of the issue has concluded that this feature functions without issue as long as it is set up properly.

Description
  • The AlwaysOn Availability Groups feature is a high availability and disaster-recovery solution that provides an enterprise alternative to database mirroring.
  • Introduced in SQL Server 2012, AlwaysOn Availability Groups maximize the availability of a set of user databases for an enterprise.
  • An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together.
  • An availability group supports both of the following:
    • A set of read or write primary databases
    • One to eight sets of corresponding secondary databases

Research and Conclusions
  • ePO works with the SQL function AlwaysOn.
  • There is no difference if the database is running on an AlwaysOn Failover Cluster Instance or Windows Server Failover Cluster. For more information, see KB74034.
  • AlwaysOn is a function of SQL, not ePO, and any issues would be in the proper setup of the AlwaysOn function.
  • But, there is a limitation to what ePO supports failover cluster nodes on the same subnet.
  • A multi-subnet failover cluster configuration does not work with ePO.
  • There are two ways to configure an SQL Server failover cluster as described in the following excerpt from the Microsoft article. For details, click here:
Depending on how the nodes are clustered, the SQL Server failover cluster is configured in the following ways:
  • Nodes on different subnet
    The IP address resource dependency is set to OR. This configuration is called an SQL Server multi-subnet failover cluster configuration. For more information, see SQL Server Multi-Subnet Clustering (SQL Server).

     
  • Nodes on the same subnet or the same set of subnets
    The IP address resource dependency is set to AND for these types of configurations:
IMPORTANT: The first option above is not supported and does not work with ePO. But, the second option is supported by ePO.

NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.

Rate this document

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.