Skip to main content
Answer

Dedicated storage policy for LiveSync on Linux?

  • February 3, 2025
  • 2 replies
  • 57 views

downhill
Byte
Forum|alt.badge.img+10

Sorry but the circular looping and vagueness of this topic has be a bit baffled as to the instruction on this page which says “ Create a dedicated, non deduplicated storage policy for the LiveSync operation. Create the storage policy using a MediaAgent available in the standby site. “. Then on this page “ A Commvault created default server plan for CommServe LiveSync uses a non-deduplication storage and a worm copy. To use a server plan other than the default, ensure that you are using a non-deduplication storage. “

Well, I have installed the second instance on the primary and both instances on the standby but where does this “dedicated” SP come into play?

What if I don’t have an MA in the “standby site” as the goal is to just have the failover capability for the CS, not actual DR needing a dedicated MA?

If I already have a non-deduped SP which could be used for LiveSync - can that be used or does it have to be dedicated? I mean if reusing an SP is OK then why would the docs say you need to “create the SP”?

And if by “dedicated” can I re-use the existing “CS DR” SP which is not deduplicated?

I don’t recall the Windows setup for this being quite this confusing win !=nix, got it. The steps in my case (11.32) didn’t match the screenshots on the BoL which also seems odd. Many were the same, I had some screens which didn’t appear in the BoL and others which caused great pause trying to understand “where am I missing Waldo”.

thanks!

Best answer by Pradeep

Hi ​@downhill ,

We can either proceed with the existing non-deduplicated policy or recommend using the Commserve DR policy, which is the default policy created during the installation process. This policy is particularly useful for Live Sync T-Log shipping.

https://documentation.commvault.com/11.20/modifying_storage_policy_for_sql_livesync_operations.html

2 replies

Forum|alt.badge.img+12
  • Vaulter
  • Answer
  • February 7, 2025

Hi ​@downhill ,

We can either proceed with the existing non-deduplicated policy or recommend using the Commserve DR policy, which is the default policy created during the installation process. This policy is particularly useful for Live Sync T-Log shipping.

https://documentation.commvault.com/11.20/modifying_storage_policy_for_sql_livesync_operations.html


downhill
Byte
Forum|alt.badge.img+10
  • Author
  • Byte
  • February 7, 2025

That is how I know them to be done in the past. My point is the page for the Linux LiveSync seems to be a bit overkill and doesn’t make note of that fact - that most likely you already have a policy which can be used, but, I suppose not always. In any case there doesn’t look to be the old feedback links for BoL and not sure how to get those pages clarified. One can waste a substantial amount of time for that prerequisite step. 

thanks