Skip to main content
commvault.com commvault.com
Answer

how to disassociate the plan from default subclient for primary SQL

  • August 14, 2025
  • 6 replies
  • 74 views
downhill
Byte
Forum|alt.badge.img+10

After setting up livesync for the CS’s, someone inadvertently set a plan for the “empty”
 default SC which is auto created when that new primary SQL client is created. Since the plan cannot be deselected from the default SC nor can the schedule be disabled obviously, the thing fails every day and if we disable the activity on it that also is flagged for various checks, so, it’s rather annoying. How can we forceably detach a plan from it and keep it silent with no SP assigned to it like it should be?

thanks

Best answer by Ledoesp

Can you go to the plan associated to the default subclient for SQL, select the associated entities and edit the association for the default subclient for SQL and assign to None?

6 replies

J
Vaulter
Forum|alt.badge.img+12
  • JavierVaulter
  • Vaulter
  • August 15, 2025

If you navigate to the subclient properties within the Command Center, you should should be able to remove the plan assignment from there.

downhill
Byte
Forum|alt.badge.img+10
  • downhill
  • Author
  • Byte
  • August 15, 2025

Not an option else I would have done that. It appears to me because it is created as part of the LiveSync DB logs, etc, that once a plan is assigned cannot be removed. I have 2 other CommCells which have this same default SC but we never associated a plan with it so cannot prove this is built in, maybe a security feature, but other default SC’s for typical fileserver plans obviously let you remove a plan, thus why I’m asking here before opening a ticket. There should be some way IMO to unlock this and keep it from trying. Or do I need to just filter everything and let it backup “nothing”?

L
Vaulter
Forum|alt.badge.img+15
  • LedoespVaulter
  • Vaulter
  • Answer
  • August 18, 2025

Can you go to the plan associated to the default subclient for SQL, select the associated entities and edit the association for the default subclient for SQL and assign to None?

downhill
Byte
Forum|alt.badge.img+10
  • downhill
  • Author
  • Byte
  • August 18, 2025

I couldn’t disassociate just the default SC - it only showed the server and after disassociating it, that broke the auto SQL transaction log backups with a Error code: [30:503]. It’s frustrating to say the least.

downhill
Byte
Forum|alt.badge.img+10
  • downhill
  • Author
  • Byte
  • August 18, 2025

And now LiveSync is busted, the DR policy is no longer associated with the failover log shipping SC. Clearly that was the wrong thing to do. 

downhill
Byte
Forum|alt.badge.img+10
  • downhill
  • Author
  • Byte
  • August 18, 2025

Ok - so disabling livesync and re-enabling got the DR policy re-associated with the SQL failover log shipping and now the default SC is unassigned. Sorry for the excess posts and I surely won’t try that again. thanks guys

Terms & ConditionsCookie settingsAccessibility statement