Using Multiple Servers
Updated: March 28, 2003
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To provide additional fault tolerance, configure a secondary (or backup) WINS server. Although WINS replication architecture benefits from employing a minimum number of WINS servers, employing a secondary WINS server improves the availability of your design. This solution balances performance and availability against cost and manageability.
When using two WINS servers to provide redundancy and load balancing, configure the replication relationship between these servers as a pull or push partnership. When you use replication, both servers contain the same WINS database information.
When a WINS server is configured as a pull partner, it periodically queries the partner server to determine if any updates are available. Use pull partnerships:
Over lower-speed WAN or congested local area network (LAN) connections.
To reduce replication traffic by consolidating WINS database updates.
To perform WINS database updates at scheduled intervals.
When a WINS server is configured as a push partner, the WINS server notifies the partner server that updates are available for replication. Use push partnerships:
Over LAN or higher-speed WAN connections.
When the network traffic created by frequent WINS replication updates is not a consideration.
To ensure WINS database updates are received as soon as possible.
The availability that is provided by WINS replication is appropriate for solving availability issues at local and remote locations. Adding a WINS server to a remote location ensures WINS availability in the event that a WAN link or router fails. For more information about replication strategies, see "Designing Your WINS Replication Strategy" later in this chapter.