CV Failover and Network Proxies

@Patrik , will these clients be able to resolve the listed hostnames on their own?  This setting should take care of that for you, though I’ll get a second opinion.

Edit: confirmed with a colleague, the above answer is correct.

Chose “Use Existing Configuration”

Choose this option to use to avoid creating of the topology for repointing clients after failover but one mandatory topology is always created for communication between the 2 CS.

Note: A default topology, “Firewall Topology created for failover clients”, is created for communication between the production and standby CommServe hosts using port 8408. This default topology routes requests between the CommServe and the SQL instances and is created irrespective of the option selected for communication. 

https://documentation.commvault.com/commvault/v11_sp20/article?p=102850.htm

Thanks guys, 

I have two Commserves and the include second instances for SQL LivSync and also to be used for Proxies for clients to reach the active Commserve. But I changed the Network setting to “Use exisiting...”

Seems to work fine for clients to connect directly to instance001 on the active CS after failover. So no need for proxies for client-connections as in the past. The default needed NetTopologies are still there as described needed for the SQL LiveSync. 

I will roll-out some more clients next week and do CV Failover again to further verify.

@Patrik, let @Leo E and I know how it goes!

Hey @Patrik , hope all is well!!  Following up to see how things are going with @Leo E ‘s suggestions.