In a clustered environment, the clustering software must have control of the Enterprise Vault services. To allow this, the Enterprise Vault Configuration wizard sets the startup of these services to manual. Do not attempt to change the startup to automatic.
If a service starts or stops outside of the control of the cluster software, the cluster software assumes that this is due to a change in system condition. For example, if a service stops, the cluster software assumes a failure and tries to restart the service or initiate a failover.
You should not attempt to start or stop Enterprise Vault services, except through the cluster software in one of the following ways:
Use Cluster Administrator to bring the associated service resource online or offline.
Use the Windows command-line utility cluster. For the syntax of this command, open a Command Prompt window and enter:
For more details, see the following article on the Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/library/8da99e1e-619f-4deb-acf0-cd8d61ac2ed01033.mspx
To help prevent the starting and stopping of services by other means, Enterprise Vault behaves as follows in a clustered configuration:
The Enterprise Vault Administration Console buttons for starting and stopping services are unavailable.
You cannot start or stop services using the EVService utility. However, you can continue to use EVService to control tasks.
Enterprise Vault blocks attempts to start Enterprise Vault services using the Windows Service Control Manager, and logs an event message. However, Enterprise Vault cannot block the stopping of services using Windows Service Control Manager, so be careful to avoid this.