Siemens Unix V4.0 - Manual (Page 211)

Implementing WINS Planning for WINS Server Implementation
Product Manual U7613-J-Z815-6-76
©
S
iem
e
n s N
ix
dor
f
In
fo
rm
at
io
n
s s y s te
m
e A
G
1
9 9 5
P
fad
: D:
\O
7 613
e6
\u
761
3e
.k
10
10.2.2 Planning for WINS Server Replication Across Wide Area Networks
The frequency of WINS database replication between WINS servers is a major planning
issue. The WINS database should be replicated frequently enough that the down-time of
any WINS server will not affect the reliability of the mapping information in the database of
other WINS servers.
However, when planning WINS database replication frequency, you do not want the
frequency to interfere with network throughput. This could occur if replication frequency is
set to a small time interval.
Consider the network topology when planning for replication frequency. For example, if your
network has multiple hubs connected by relatively slow wide-area-network (WAN) links,
you can configure WINS database replication between WINS servers on the slow links to
occur less frequently than replication on the local area network or on fast WAN links. This
reduces traffic across the slow link and reduces contention between replication traffic and
WINS client name queries.
For example, WINS servers at a central local-area-network site may be configured to
replicate every 15 minutes, while database replication between WINS servers in different
WAN hubs might be scheduled for every 30 minutes, and replication between WINS servers
on different continents might be scheduled to replicate twice a day. The following figure
illustrates this example of variation in replication frequency.
Example of an Enterprise-Wide Configuration for WINS Server Replication
15 minutes
12 hours
30 minutes
North America
Australia