Upgrading an existing Enterprise Vault installation to a VCS cluster

There are two types of Enterprise Vault installation that you can upgrade to a cluster: a single, non-clustered Enterprise Vault server, and a building blocks configuration that contains multiple Enterprise Vault servers. To be eligible for upgrade to a cluster, the Enterprise Vault installation must have the following features:

Enterprise Vault should already be configured in a non-clustered configuration, and it must not already be part of a cluster.
Enterprise Vault servers must be configured using unqualified DNS aliases rather than fully qualified names.
The Enterprise Vault server must have a full set of Indexing, Shopping, Task Controller and Storage services.
In a building blocks environment, an Enterprise Vault server that is hosting services must not be running in failover mode.

To upgrade an existing Enterprise Vault installation to a VCS cluster

Check that your setup meets the requirements for the Enterprise Vault service group.

See Before you configure the VCS service group for Enterprise Vault.
Run the Enterprise Vault Cluster Setup wizard to create an Enterprise Vault service group and add to the group the server that you are going to configure.
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
- EMC Centera staging areas
If they are not, correct the locations in the Enterprise Vault Directory database and then move the associated data to the new locations.
On the Windows Start menu, click All Programs > Enterprise Vault > Convert to Cluster.
Read the introductory information, and then click Next.
When the following page appears, check All locations are highly available storage devices, and then click Next.
If the wizard detects that there are messages in the Enterprise Vault MSMQ queues, choose whether to proceed with the conversion without migrating them to the clustered MSMQ queues.

Wait until the queues have cleared and then rerun the Convert to Cluster wizard. Any messages that are still in the queues are ignored in the new cluster. To accelerate the process of clearing the queues, stop the Task Controller service and ensure that File System Archiving is not performing an archiving run.
When the wizard prompts you to choose a service group in which to create the cluster resources for each Enterprise Vault service, select the group that you created earlier.
Click Next to create the cluster resources, and then review the list of actions that the wizard has carried out.
Click Finish to close the wizard.
Using the DNS snap-in to the Microsoft Management Console (MMC), change the computer name alias to point to the virtual server name rather than the local name.
Use Veritas Cluster Manager to bring the resources in the cluster online.