Managing Policy Broker Replication

Policy Broker Replication | Web Protection Solutions | v8.4, v8.5.x | 29-Apr-2022

Policy Broker is responsible for managing access to both policy data (including clients, filters, and exceptions) and global settings for web protection solutions.

You have the option to deploy Policy Broker in either a standalone or replicated configuration.

In a standalone configuration, there is one Policy Broker for the entire deployment.

In a replicated configuration, there is one primary Policy Broker, to which configuration and policy changes are saved, and one or more replica instances, each with their own read-only copy of the configuration and policy data.

The primary Policy Broker and all replica instances must reside on a Windows or Linux server. When you enable replication, Policy Broker cannot reside on an appliance.

If one Policy Broker instance becomes unavailable, components can connect to another instance, allowing database downloads, policy enforcement, and reporting to continue without interruption.

In geographically distributed deployments, having components retrieve information from a local Policy Broker may improve performance.


	Important A replicated environment requires bidirectional communication on port 6432 between the primary Policy Broker and each of its replicas. Make sure that your firewalls are configured to allow this communication.