|
Synchronization
Processes:
Filtering Profile Synchronization Process
In the filtering profile synchronization process, if a filtering
change is made on the source server—whether the update is a
global, IP, LDAP, minimum filtering bypass activation, or user profile
update—the change is applied locally. Once locally applied
on the source server, this update is sent to all target Web Filter units.
Each target server will then immediately apply this filtering change.
The result is that profile updates occur on all Web Filter units in near
real time.
In the event that a target server is unable to communicate with
the source server, the target server will continue to run the last
known configuration it received from the source server. The only
exception to this scenario is that active profiles—such as
LDAP or override accounts—will not run on the target server,
since active profiles are timed out after a specified period of
time. However, all IP based filters—such as the minimum filtering
level, and the global rule that was last received from the source
server—will be applied. When the target server resumes communication
with the source server, it will actively download and apply the
latest running configuration from the source server.
If the target server is rebooted for any reason (loss of power etc.)
upon bootup, the target server will actively download and apply
the current running configuration from the source server. It will
then also receive future changes made on the source server.
Top
Library Synchronization
Process
In the library synchronization process, if a library change is made
on the source server, the change is applied locally. Once locally
applied on the source server, this update will be placed in a queue
for submission to target Web Filters. The source server will then send
the information in the queue to all target servers. Each target
server will receive this information and apply the update.
On the source server, a separate queue exists for each identified
target server. A queue is used as a repository in the event of a
communication failure between the source server and target server.
Information remains in this queue and is submitted to the target
server once communications are re-established. The use of queues
ensures that if a target server is taken offline for a period of
time, when it is brought back online, it will be updated with the
latest changes from the source server.
Related
Topics:
Back
| Top
|
