I
NTRODUCTORY
S
ECTION
C
HAPTER
3: S
YNCHRONIZING
M
ULTIPLE
U
NITS
M86 S
ECURITY
U
SER
G
UIDE
41
Delays in Synchronization
When a filtering profile is applied to the source server, there
is a slight delay in the time it takes to apply the profile to the
target server. This delay is caused by the amount of time it
takes the source server to process the change, prepare the
update for submission, send the update, and finally to acti-
vate the update on the target server. In practice, this should
only be matter of seconds. In essence, filtering profiles are
shared in near real time with this factor being the only delay.
The delay in activating a library change can take a little
longer than in activating a filtering profile change. This is
due to the fact that the library on the Web Filter is loaded
into the physical memory. When a change is made to the
library, a new library must be loaded into memory with the
changes. So the delay between the library change taking
place is the net of the amount of time it takes the source
server to prepare the update for submission, and then the
amount of time it takes for the update to be sent, received,
and processed by the target server. Once processed, the
new library is loaded into memory and activated, while the
old version of the library is removed from memory. The total
time of this process will vary depending upon custom library
entries, but the entire procedure should take approximately
one minute.