Description

SQL Server Multi-Subnet Clustering is currently not supported with Enterprise Vault (EV), however, it is possible to implement Multi-Subnet Clustering using a load balancer acting as intermediary between EV and SQL. This allows EV to connect to both the primary and secondary nodes of the cluster which exist in a multi-subnet environment.

This is typically used for Disaster Recovery (DR) scenarios where the secondary node exists in a different datacenter than the primary node, thus having a different IP subnet than the primary node of the cluster.

Set up a load balancer: Configure a load balancer to act as an intermediary between Enterprise Vault and SQL Server. This load balancer should be able to route traffic to both the primary and secondary nodes of the cluster.
Configure Enterprise Vault: In the Enterprise Vault Accelerator Manager website, right-click on the server name and select "Properties". Set the required details for the Discovery Accelerator configuration database. You can specify either the name or IP address of a standalone SQL Server computer, or the virtual network name or IP address of an Always On Availability Group listener or Failover Cluster Instance. If you choose to use a non-default port, make sure to append the port number to the server name or IP address.
Configure the database: In the Accelerator Manager, right-click on the required database and select "Properties". In the SQL Server field, set the required details for the database. Again, you can specify the name or IP address of a standalone SQL Server computer, or the virtual network name or IP address of an Always On Availability Group listener or Failover Cluster Instance. If you choose to use a non-default port, append the port number to the server name or IP address.

Please note that these steps are a workaround and SQL Server Multi-Subnet Clustering is not officially supported by Enterprise Vault. Make sure to regularly check for updates on this article for any changes or updates to the workaround

The details of this workaround are still being gathered. Please check back regularly for updates on this article.