Symantec 10521146 - Network Security 7120 Administration Manual page 279

Security does not synchronize incidents and events. Each node maintains this
information separately.
Automatic synchronization
Synchronization occurs automatically at a random interval so that the nodes in
a cluster do not expect updates at the same time. When you edit the master node
or the network topology, your changes are automatically synchronized across
all nodes in the cluster. Because automatic synchronization occurs randomly,
rather than immediately, you may want to initiate an immediate
synchronization using Force Database Sync.
See "Forcing nodes to synchronize"
Reapplying policy assignments after setting cluster master
This section describes setting protection policies to an interface and applying
them to multiple interfaces.
In a cluster, the master node stores the definitions of protection policies that
you apply to slave nodes. If the master node fails or is demoted by setting a new
cluster master, the link is broken between applied policies and their definitions.
Slave nodes sometimes then appear to have viable policies applied that in reality
are disabled. Prevent losing policies through failure by backing up the master
node. Prevent losing policies when demoting by reapplying policy definitions to
the new master node.
Note: SuperUsers can reapply policies to an interface; Administrators,
StandardUsers, and RestrictedUsers cannot. See
page 319 for more about permissions.
See "Backing up and restoring"
See "Setting policies to interfaces"
Forcing synchronization
All software and appliance nodes synchronize with the master node. The
Network Security console provides a way to trigger synchronization by
restarting or rebooting slave nodes, or by forcing.
To force databases to synchronize at any time
In the Network Security console, click Admin > Force Database Sync, and
◆
click OK.
on page 83.
"User groups reference"
on page 297.
on page 115.
Advanced configuration
Managing node clusters
on
279