Hi Dario,

In order to provide full fail over functionality you need to connect everything with the Commserve Instance 002 installations (the SQL clients you mentioned) on both the active and passive Commserve's.
These installations will automatically redirect the connecting client/vsa/etc towards the active Commserve.

You could setup a network topology where all clients are introduced with routes to both commserve their instance 001 installations, but this negates the automation and prevention of connection errors which this manual solution will introduce.

It is a relative small change to alter the network topologies to get everything automated and fail safe for the future, not knowing what development will introduce in the future what might conflict with your manual configuration.

Hi Dario,

 I see where you’re seeing that “requirement”:

https://documentation.commvault.com/11.24/essential/106081_planning_for_commserve_livesync_setup.html

 To answer your question, it’s possible to bypass this as a proxy is not required. It’s for one of the two possible connectivity options.

Hi Jos,

thks,

So I should change the communication between the clients and the commserve active and standby.If I understand correctly when I install livesync-DR it automatically creates the 002 instance for me, but how at what level do I make the change using the proxy instead of tunneling?

Dario

Hi Dario,

The installation for livesync will automatically create the necessary config, this config ensures all clients will become member of the needed groups automatically.

The only things you need to check after the config is:

- is the failover working, and

- can the clients backup after failover.

If all is working you can disable the current "old" network topology and perform a giveback and check again if backups work.

P.s. the clients will connect to the instance002 using TCP 8408 instead of the default TCP 8403

Hi @Jos Meijer ,

A couple more questions:- For disable the current "old" network topology where do I go to do that?- Can the migration of the current production to Livesync DR be done hot?

Thks

Dario

Hi Dario,

It depends, a network topology can be centrally configured at the Network Topologies section:

Or there can be a config on Client Group level, Client group properties - Network - Network Route Configuration.

Or there can be a config on Client level, Client properties - Network - Network Route Configuration.

During the installation the existing Commserve will be added with an additional instance (Instance002) this does not have the requirement to stop services on Instance001. As far as I know the services of Instance001 won’t be stopped and production can be kept active when performing a LiveSync installation afterwards.

FYI, After the installation you will have these new network topologies:

All clients will be automatically placed in this Network Topology / Client Group config (if you enable LiveSync with default settings):

Hi Jos,

I have for client group this configuration :

is it enough to uncheck "Configure Network Route Settings"?

Thks

If outgoing routes also only defines the Commserve then yes, if multiple routes are defined you want to edit the routes and not disable the whole config for this Client Group.

As a reminder, before disabling this make sure the communication is working by checking cvping to active and passive Commserve Instance002 hostname/ip and perform a backup.

Additionally you should be able to see additional firewall lines for clients regarding the instance002 in the fwconfig.txt file located in <Client cv install location\Base check the cvd.log and cvfwd.log as well <cv install location\Logs to see if there are connection errors and tunnel connections have been successfully created.

Hi Jos,

in Outgoing Routes i didn't define anything, so it should be enough to uncheck the configuration.

Ok for reminder.

Yes this would be enough based on the provided information