• Article

Default file size for cluster.log should be raised to 32

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether the ClusterLogSize parameter has been set:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\

If the Exchange Server Analyzer finds the value for ClusterLogSize is not present, or the value for ClusterLogSize is equal to or less than 8, a warning is displayed. On a busy cluster, the cluster.log file wraps around so quickly that entries may be lost when you troubleshoot fail-over situations under the following conditions:

  • Troubleshooting requires a detailed review of the cluster log file.

  • The cluster is managing many resources.

Therefore, when troubleshooting requires use of the cluster.log file, create the ClusterLogSize parameter, if not already present, and increase the default size to at least 32, 64, or 96.

Important

This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.

To create the ClusterLogSize parameter and set its value

  1. Open a registry editor, such as Regedit.exe or Regedit32.exe.

  2. Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment.

  3. In the left pane, click Environment.

  4. On the Edit menu, point to New and then click DWORD Value.

  5. Type ClusterLogSize, and then press ENTER to name the new registry entry.

  6. Right-click ClusterLogSize, and then click Modify.

  7. Modify the ClusterLogSize Value data to the new log file size. For example, modify the ClusterLogSize value to 32, 64, or 96, and then press ENTER.

  8. Quit Registry Editor

To modify the default size of the cluster.log file

  1. Open a registry editor, such as Regedit.exe or Regedt32.exe.

  2. Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment.

  3. Right-click ClusterLogSize, and then click Modify.

  4. Modify the ClusterLogSize Value data to the new log file size. For example, modify the ClusterLogSize value to 32, 64, or 96, and then press ENTER.

  5. Quit Registry Editor.

Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows registry" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

For more information about cluster logging in Microsoft Cluster Server, see the Microsoft Knowledge Base article 168801, "How to Turn on Cluster Logging in Microsoft Cluster Server" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=168801)