If you experience problems when you configure FSA clustering, try the following:

• Verify that you have installed and configured the FSA services on each node to which the cluster group can fail over.

• Ensure that the ClusSvc service (for Microsoft server clusters) or Had service (for Veritas Cluster Server) is configured and running on the file server.

• Check the log files. The FSA Cluster Configuration wizard stores details of the changes that it has made in the file FSACluster.log, which is located in the \Utilities\FSA Cluster subfolder of the Enterprise Vault program folder (typically C:\Program Files\Enterprise Vault).

  The wizard creates additional log files on the individual cluster nodes when you configure a group for FSA services high availability. These log files are called FSA-MSCSType.log or FSA-VCSType.log, depending on whether you are using Microsoft server clusters or Veritas Cluster Server, and they are stored in the FSA Agent installation folder.

  The following registry value determines the level of logging:

  HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\FSA\LogLevel
  

  LogLevel can have a value in the range 0 through 5, where 0 or 1 records critical messages only, whereas 5 records debug and diagnostic messages.

• Run DTrace on the FSA Cluster Configuration wizard.

  If the DTrace view command does not include FSAClusterWizard in the list of processes that are available to monitor, register the wizard with DTrace as follows:

  • Enter the following command from DTrace:

    set FSAClusterWizard.exe

  • Then register the name when DTrace prompts you.

  For more information on DTrace, see the Utilities manual.