LiveSync Commserve for DR/failover and Remote Cache

Hello,

You can try creating a SW folder under the following path:
C:\Program Files\Commvault\ContentStore

Once the folder is created, please try syncing the cache again.

I recommend creating the Software Cache folder under C:\Program Files\Commvault\ContentStore2. This setup allows the folder to function as a remote cache for installations, and you can conveniently configure it from your active CommServe since it will be recognized as a client.

You are correct that ContentStore2 is created for Instance002 on both the Active and Standby servers. Since Instance002 on your Live Sync server reports to the primary CommServe and acts as a client, managing the remote cache becomes straightforward.

Regards,

Bhatia

Sorry for not responding sooner… but there is some confusion on my side

Do I need to create these directories/folders on my primary commserve server, or the livesync/DR /secondary server… or both?

Update: 

• I went ahead and added the “SW” folder to “C:\Program Files\Commvault\ContentStore”, as that’s what we had already configured in the remote caches.  This got a remote cache to sync. Note: I used the Java UI → remove cache → edit to browse and had CommVault make the “SW” folder.
• I asked CommVault's “Arlie” AI to give me some clarity on the differences between “C:\Program Files\Commvault\ContentStore” and “C:\Program Files\Commvault\ContentStore2” and it kinda gave an answer that made sense, but also started some odd circular reasoning (saying “C:\Program Files\Commvault\ContentStore2” was for “instance001”) which I believe it is definitely not. It's for isntance002
• Arlie did point me to some docs: Synchronizing Software Cache on the Standby CommServe Host which indicate “On the standby CommServe server, the remote cache location is the software cache directory of Instance001” AND “After a failover, disable or remove the remote cache from the new active node, and create or enable remote cache on the new passive node.”. This makes some sense as to why I have 2 remote caches, and one is disabled.  it's to have the caches pre-set up to prep for enabling one and disabling the other in the event we have to perform a Commserve “Production” failover to the DR commserve.  This means the remote caches need to be in the same location and not “C:\Program Files\Commvault\ContentStore2”. 
•  I still cannot seem to find out what “C:\Program Files\Commvault\ContentStore2” is for (in a DR/Livesync setup scenario) other than “well! its instance002!”. like, do I need to make this a remote cache as well… on both primary and DR commserves? I’m not really sure why there needs to even be an instance002 set up when building a DR/livesync commserve. but that’s prob not for this thread and just more education I need.