Question

App-Aware VM Backup Schedules

  • 21 February 2021
  • 5 replies
  • 68 views

Badge +1

I have configured an app-aware  (SQL) VM backup and the initial job ran successfully and pushed out the required agent to the VM and subsequently backed up the SQL instance however the schedules initially assigned to VM look to have been applied to SQL subclient which causes the job to fail on next run and every run thereafter as the application is trying to be backed up both as an app-aware VM but also a standalone SQL backup.

Has anyone else had this issue with SQL app-aware backups?


5 replies

Userlevel 1
Badge +3

Hi Tom! I’m having exact same issue (two CommCells, both 11.22). As a workaround I removed SQL associations from plan’s schedule policies in Commcell Console. Let us know your findings from support.

Badge +1

@Chris Hollis,

I raised this with support a few days ago so is actively being worked on, I posted on here in case anyone might have had a similar issue and could possibly advise the fix at the time.

Initial response from support is that it is not expected behaviour. 

Once I have a resolution I will update this post.

Userlevel 3
Badge +3

Thanks for clarifying @Tom Evans 

I think it would be best to see if we can get a copy of your database and review this via a support incident as I don’t believe what you are seeing is expected (it could be...but we’ll confirm officially once we’ve reviewed the setup).

Would you be able to raise a support case and let me know the ticket number? 


We’ll loop back on this thread with our findings afterward for the broader community. 

Badge +1

Hi @Chris Hollis 

Thanks for your reply.

Yep the issue is exactly as you describe in that the SQL Instance has inherited schedules from the plan configured for the VSA backup.

The SQL client is part of 4 groups in total (all default configuration). The hypervisor group, External Clients for Failover, Infrastructure and MediaAgents group.

I've checked schedules for these groups and the only schedule is the Automatically created Install Software schedule.

No smart groups configured in the environment (other than default system created ones).

Thanks
Tom

Userlevel 3
Badge +3

Hi @Tom Evans 

If I’m understanding you right, what you’re saying is that the subclient within the SQL Instance itself has inherited the same scheduler as the VSA Subclient containing the VM?

If so, that does not sound right… I’d only expect to see a T-LOG backup schedule be automatically assigned (at the SQL subclient) which is mentioned here: https://documentation.commvault.com/commvault/v11_sp20/article?p=14283.htm

There is a possibility that the SQL Agent was added to a client group that defines the same scheduler as the VSA subclient. 

Do you have smart groups configured by any chance? 

Please refer to: 

https://documentation.commvault.com/commvault/v11_sp20/article?p=4874.htm & https://documentation.commvault.com/commvault/v11_sp20/article?p=4894.htm
 

Could you please check to see if the SQL client is part of multiple or any other client computer groups? 

 

Reply