Managing the WINS Server Database

The WINS database under Windows NT Server 4.0 uses the performance-enhanced Exchange Server Storage engine version 4.0.

There is no built-in limit to the number of records that a WINS server can replicate or store. The size of the database is dependent upon the number of WINS clients on the network. The WINS database grows over time as a result of clients starting and stopping on the network.

The size of the WINS database is not directly proportional to the number of active client entries. Over time, as some WINS client entries become obsolete, and are deleted, there remains some unused space.

To recover the unused space, the WINS database is compacted. Under Windows NT Server 4.0, WINS server database compaction occurs as an automatic background process during idle time after a database update.

Because the WINS server database compaction occurs while the database is being used, you do not need to stop the WINS server to compact the database.

Note

Under Windows NT Server 3.51 or earlier, you must manually compact the WINS server database. See the topic "Compacting the WINS Server Database" in the section "Troubleshooting the WINS Server Database" later in this chapter. In most cases there is no need to manually compact the WINS server database under Windows NT Server 4.0. However, if you decide to do so, use this same procedure.

The following database files are stored in the \%systemroot%\System32\Wins directory.

Table 8.11 Microsoft WINS Server Database Files

File

Description

J50.log and J50#####.log

A log of all transactions done with the database. This file is used by WINS to recover data if necessary.

J50.chk

A checkpoint file.

Wins.mdb

The WINS server database file which contains two tables:

· IP address-Owner ID mapping table

· Name-to-IP-address mapping table

Winstmp.mdb

A temporary file that is created by the WINS server service. This file is used by the database as a swap file during index maintenance operations and may remain in the %systemroot%\System32\Wins directory after a crash.


Important

The J50.log, J50#####.log, Wins.mdb, and Winstmp.mdb files should not be removed or tampered with in any manner.

WINS Manager provides the tools you need to maintain, view, back up, and restore the WINS server database. For example, you use the WINS Manager to back up the WINS server database files, and this administrative task should be done when you back up other files on the WINS server.

Backing Up the Database

WINS Manager provides backup tools so that you can back up the WINS database. After you specify a backup directory for the database, WINS performs complete database backups every three hours, by installation default.

For specific instructions on how to back up and restore the WINS database, see the Help topic "Backing Up and Restoring the Database" in WINS Manager Help.

You should also periodically back up the Registry entries for the WINS server.

Scavenging the Database

Scavenging the WINS server database is an administrative task related to backing up the database. Like any database, the WINS server database of address mappings needs to be periodically cleaned and backed up.

The local WINS server database should periodically be cleared of released entries and old entries that were registered at another WINS server and replicated to the local WINS server, but for some reason did not get removed from the local WINS database when the entries were removed from the remote WINS server database.

This process, called scavenging, is done automatically over intervals defined by the relationship between the Renewal and Extinct intervals defined in the Configuration dialog box. You can also clean the database manually.

The following table describes the results of scavenging the WINS database.

Table 8.12 Scavenging the WINS Database

State before scavenging

State after scavenging

Owned active names for which the Renewal interval has expired

Marked released

Owned released name for which the Extinct interval has expired

Marked extinct

Owned extinct names for which the Extinct timeout has expired

Deleted

Replicas of extinct names for which the Extinct timeout has expired

Deleted

Replicas of active names for which the Verify interval has expired

Revalidated

Replicas of extinct or deleted names

Deleted