Clustering Enterprise Vault in a 2+1 "any-to-any" configuration

This second option for a 2+1 operation mode involves configuring the Enterprise Vault virtual servers EVSERVER1 and EVSERVER2 to run on any of the three nodes. This has the advantage that, for example, if NODEA fails and EVSERVER1 fails over to NODEC, you can bring NODEA back online to act as the failover node for EVSERVER1 and EVSERVER2.

Figure: 2+1 "any-to-any" configuration

2+1 "any-to-any" configuration

You can extend the setup process for an N+M configuration with any number of primary and failover nodes, up to the total of 8 clustered nodes supported by Microsoft server clusters.

To cluster Enterprise Vault in a 2+1 "any-to-any" configuration

  1. Prepare for clustering as follows:

    • Add three nodes to the cluster (NODEA, NODEB, NODEC).

    • Create two resource groups (EVSERVER1, EVSERVER2), and add the prerequisite resources to each group.

    • Configure the groups and resources so that the following nodes are the preferred owners, in the order shown:

      EVSERVER1

      NODEA, NODEC, NODEB

      EVSERVER2

      NODEB, NODEC, NODEA

  2. Follow steps 2 to 5 of the 2+1 configuration without "any-to-any" support.

  3. Test the cluster to confirm that if an active node fails, the virtual server fails over to the appropriate node.

  4. For example, if you have configured the preferred owners of the resource groups as suggested in step 1:

    • Confirm that if NODEA fails, EVSERVER1 fails over successfully to NODEC.

    • Then bring NODEA back online as the spare node and confirm that if NODEB fails, EVSERVER2 fails over to NODEA.

More Information

Clustering Enterprise Vault in a 2+1 configuration without "any-to-any" support

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.