How to Change the Length of Time That a Resource Remains Pending Before Failing Using Cluster Administrator

  • Article

 

By default, Cluster Service allows a resource to be in a pending state (online pending or offline pending) for only 180 seconds (3 minutes) before Cluster Service terminates the resource, and the resource enters a failed state.

Because of the way that the Exchange store writes log files to an Exchange database, the Exchange store for which you might want to increase the Pending timeout period. Increasing the pending time-out period allows the store more time to shut down correctly. This procedure outlines how to change the length of time that a resource remains pending before failing.

Before You Begin

Before you start managing your Exchange cluster, you may want to review what constitutes an Exchange Virtual Server and its associated Exchange resources. You may also want to become more familiar with Cluster Administrator—the primary tool used to configure and manage clusters.

Note

Before performing the cluster administration tasks outlined in this chapter, you must be familiar with the clustering concepts described in "Checklist: Preparation for installing a cluster" in the Microsoft Windows Server™ 2003 Enterprise Edition Online Help and in the Windows Server 2003 Technical Reference.

Also, make sure that you are familiar with "Using Server Clustering" in Planning an Exchange Server 2003 Messaging System and with "Deploying Exchange 2003 in a Cluster" in the Exchange Server 2003 Deployment Guide.

Procedure

To change the length of time that a resource remains pending before failing

  1. In Cluster Administrator, in the console tree, click the Exchange Virtual Server that contains the resource that you want to configure.

  2. In the details pane, right-click the resource that you want to configure, and then click Properties.

  3. On the Advanced tab in the resource's Properties dialog box, type a value in seconds for Pending timeout.