Comparison of resiliency solutions for appliances

To learn about how to choose the right solution for your deployment, and to see how these solutions answer the needs of a typical deployment, read the following topics:

The following table compares the High Availability Pairing and Failover Clustering solutions:

Solution	High Availability Pairing	Failover Clustering
Node configuration model	Active/Standby	All Appliances are active
Allows distribution across geographic locations	No	Yes
Failover detection mechanism	Active and Standby nodes are regularly monitored to detect their operational state.	Enterprise Manager monitors the Appliance through port 13000.
Failover triggers	Active Appliance outage: power off, reboot, etc. *** Service down does NOT trigger failover	Appliance outage at the TCP stack level *** Service down does NOT trigger failover
Failover triggers Forescout service restart	Yes. Affects overall failover time (until Standby becomes Active)	No
Total failover time	Time varies (due to Forescout service start).	Configured Failover Detection Time (default and minimum of 3 minutes) plus up to 30 additional seconds.
Continuity for all endpoint types?	Yes	Endpoint, switch and wireless device visibility assessment and enforcement are supported. See Continuity of Endpoint, Switch and Wireless Device Visibility, Information and Enforcement. For endpoints and features that are not currently supported, see Features Not Currently Supported.
Network requirements	Requires redundant pair of interconnecting cables to sync the 2 Appliances.	Yes. See Network Deployment Requirements.
Requires dedicated setup and configuration during Appliance installation	Yes	No
Requires available capacity from active Appliance/s	No	Yes. See Distribution of Workload upon Failover.
Allows using a combination of physical and virtual Appliances	No	Yes
Allows using Appliances with different models	No	Yes