Enterprise Vault™ Installing and Configuring

To convert an existing Enterprise Vault server to a server with Windows Server Failover Clustering support

1. Ensure that the following items are all on highly available shared storage devices:

   • Indexing service data

   • Shopping service data

   • Vault store partitions

   • PST holding folders

   • SMTP holding folder *

   • Centera staging areas

   * The SMTP holding folder is only required if the Enterprise Vault SMTP service is configured as a cluster service in the Enterprise Vault cluster.

   If the items are not on highly available shared storage devices, correct the locations in the Enterprise Vault Directory database and then move the associated data to the new locations.

2. Use Failover Cluster Manager to ensure that a suitable cluster service you prepared earlier is online on the Enterprise Vault server node.
3. In Windows, start the Enterprise Vault Convert to Cluster wizard.
4. When the first page of the wizard appears, click Next to continue.
5. The wizard makes a number of checks to determine the suitability of the installation for conversion to a cluster. It then displays a warning reminder that, when the wizard has successfully completed, you must update the DNS alias or Hosts file entry that is currently pointing at the physical node, so that it points at the cluster server name.
6. The wizard then displays a list of the current file locations for the Enterprise Vault services and partitions. You must confirm that these locations are all on highly available shared storage devices before continuing. Either select the check box to confirm high-availability, and click Next to continue, or click Cancel to exit from the wizard and move the required data to highly available locations before running the wizard again.
7. If the wizard detects that there are messages in the Enterprise Vault MSMQ queues, it displays a page indicating the name of each queue and the number of messages on it. The wizard cannot move these messages to the clustered message queues due to permissions constraints. We recommend you cancel from the wizard and leave the services running in a non-clustered environment until Enterprise Vault has cleared the message queues. You can then re-run the Convert to Cluster wizard. If you continue without doing this, the messages remain on the node-specific queues and are not processed. If you want to continue without clearing the queues, select the Continue converting configuration to a cluster check box and click Next.
8. The wizard lists the cluster services that are currently online on this node. Select the required cluster service, and then click Next.
9. The wizard creates the necessary resources, updates the Enterprise Vault services to manual startup, and updates the Directory database tables to remove the local computer name from the computer entry table and the message queue names. The final wizard page displays a list of the actions the wizard has performed, and the results. Click Finish to exit the wizard.
10. If you have not already done so, manually update the DNS alias to point at the cluster server name rather than the local node name.
11. Bring the cluster server resources online using Failover Cluster Manager.