Backing up a WINS database on a Windows 2000, Windows Server 2003, or Windows Server 2008 cluster

The typical procedures for backing up the Windows Internet Naming Service (WINS) database are not available when you configure WINS to run as a resource on the following operating system setups:

• A Windows 2000-based server or a Windows Server 2003-based server that is running the Microsoft Cluster service
• A Windows Server 2008 server that has the Failover Clustering feature

In this scenario, the Back Up Database command is not available (grayed out) on the Action menu in the Microsoft Management Console (MMC) or in the properties for the WINS server.

If WINS is installed and is running on a stand-alone server, the database is stored in the %SystemRoot%\System32\Wins folder. In this scenario, follow these steps to back up the WINS database:

1. Open the WINS Microsoft Management Console (MMC) snap-in.
2. Click WINS.
3. Right-click WINS, and then click Back Up Database.

The %SystemRoot%\System32\Wins folder is typically used as the required backup destination. After the database backup is complete, a subfolder, Wins_bak, is created under the WINS folder. Another subfolder, New, contains copies of the Wins.mdb file, the Wins.pat file, and the most recent jet database log file. The jet database log file has the following file name format: J5XXXXX.log. The files in the New folder can be used to restore the WINS database, if it is required.

Because the Back Up Database command is not available when WINS runs on a cluster, use one of the following methods to back up the WINS database.

Method 1

Configure WINS to back up the database during server shutdown. To do this, follow these steps:

Windows 2000 and Windows Server 2003

1. Open the WINS Microsoft Management Console (MMC) snap-in.
2. Click WINS.
3. Right-click WINS, and then click Properties.
4. On the General tab, click to select the Back up database during server shutdown check box.
5. Verify that the specified path is the path that you want.
   Note The default path is \Winnt\System32\Wins on the share drive.

Windows Server 2008

1. Open the Failover Cluster Management snap-in.
2. Under Services and Applications, select the group that contains the WINS service.
3. In the Actions pane, click Manage WINS.
   Note A new snap-in opens.
4. Right-click WINS, and then click Properties.
5. On the General tab, click to select the Back up database during server shutdown check box.
6. Verify that the specified path is the path that you want.
   Note The default path <drive:>\wins\backup\ on the share drive.

When the group that contains the WINS Service resource is moved, or if it is failed over to another node, the WINS service on the losing node is taken offline (stopped). The WINS service is then brought online (started) on the gaining node. The WINS database is backed up every time that this action occurs.

Method 2

Manually back up the folder that contains the WINS database. To do this, follow these steps.

Windows 2000 and Windows Server 2003

Back up the WINS folder on the external drive by using Ntbackup or a third-party backup product. In addition, you must run Windows Server Backup on the node that owns the group that contains the WINS resource.

Notes

• The WINS Service resource can remain online during this process.
• When You Configure the backup, you must clear the Enable System recovery check box to avoid receiving an error such as the following Application log entry.
  
  

  Log Name:      Application
  Source:        SPP
  Date:          <Date>
  Event ID:      16387
  Task Category: None
  Level:         Error
  Keywords:      Classic
  User:          N/A
  Computer:      <ComputerName>
  Description:
  Shadow copy creation failed because of error reported by ASR Writer. More 
  info: Automated System Recovery failed the shadow copy, because a selected 
  critical volume is located on a cluster shared disk. This is an unsupported 
  configuration. (0x80042405).
  
  MSONLY start
  Reference Windows SE # 249790 for updates related to Event 16387 generated 
  in Windows Server 2008 when critical volume is located on a cluster shared disk.
  MSONLY end