Share via

How to Configure Disk Dependencies for a Single Copy Cluster on Windows Server 2003

  • Article

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

This topic describes how to view and configure the appropriate physical disk resource dependencies and failure settings in a single copy cluster that is running on Windows Server 2003. For detailed steps to view and configure the appropriate physical disk resource dependencies for storage groups and databases in a single copy cluster that is running on Windows Server 2008, see How to Configure Disk Dependencies for a Single Copy Cluster on Windows Server 2008.

Before You Begin

To perform this procedure, the cluster must be operational.

To perform the following procedure, the account you use must be delegated the following:

  • Exchange Organization Administrator role for the clustered mailbox server.

For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

Procedure

To use the Cluster.exe to configure physical disk resource dependencies and failure settings

  1. Open a Command Prompt window and run the following command:

    Cluster <ClusterName> res <DatabaseResourceName> /AddDep:<DiskResourceName>

    For example, to make a disk resource named Disk D: a dependency for a Microsoft Exchange Database Instance resource named First Storage Group/Mailbox Database (EXCLUSTER) in a failover cluster named SCCMBX1, run the following command:

    Cluster SCCMBX1 res "First Storage Group/Mailbox Database (EXCLUSTER)" /AddDep:"Disk D:"

    Repeat the above command for each Microsoft Exchange Database Instance resource and its corresponding disk resource.

  2. After the physical disk resource dependencies have been properly configured, the physical disk resource policies must be configured so that a failure of a disk resource does not cause failover of the CMS to another node. This policy can be configured by running the following command for each disk resource in the CMS group:

    Cluster <ClusterName> res <DiskResourceName> /prop RestartAction=1

To use Cluster Administrator to check physical disk configuration settings

  1. Open Cluster Administrator.

  2. Double-click the cluster name.

  3. Double-click the Resources folder.

  4. Right-click the disk resource and select Properties. Select the Advanced tab. Make sure that Affect the group is not selected. Click OK.

To use Cluster Administrator to check database dependencies

  1. Open Cluster Administrator.

  2. Double-click the cluster name.

  3. Double-click the Resources folder.

  4. Right-click the database resource and select Properties. Select the Dependencies tab. Verify the physical disks hosting the database, logs, and system files are listed. Click OK.

    Note

    For a physical disk to be on this list, it must host real data for the database.

    Note

    The same physical disk resource may be referenced by multiple databases.

  5. Continue with this step only if you are using mount points for storage group or database data. Right-click the physical disk resources for each physical disk dependency and select Properties This must be done for each physical disk resource. Select the Dependencies tab. Verify that the physical disk that hosts the mount point is listed as a dependency. Click OK.

To use Cluster Administrator to change database dependencies

  1. Open Cluster Administrator.

  2. Double-click the cluster name.

  3. Double-click the Resources folder.

  4. Right-click the database resource and select Properties. Select the Dependencies tab. Verify that the physical disks hosting the database, logs, and system files are listed.

    Note

    For a physical disk to be on this list, it must host real data for the database.

    Note

    The same physical disk resource may be referenced by multiple databases.

  5. If the information is incorrect, click Modify. Using the arrow buttons, add the correct physical disks and remove the incorrect physical disks. Click OK twice.

  6. Continue with this step only if you are using mount points for storage group or database data. Right-click the physical disk resources for each physical disk dependency and select Properties. This must be done for each physical disk resource. Select the Dependencies tab. Verify that the physical disk that hosts the mount point is listed as a dependency.

  7. If the information is incorrect, click Modify. Using the arrow buttons, add the correct physical disks and remove the incorrect physical disks. Click OK twice.