Fantastic thanks for the prompt response.
On that note, is it safe to rename the SQL jobs or will this affect SnapCenter in any way?
The reason I ask is that we create out backup jobs via the PowerShell cmdlets and using this method there is no option to name the SQL Job so the jobs are created with the name format "SnapCenter_RG<resource group ID>_policy<policy ID" (e.g. SnapCenter_RG10_Policy16), so it's difficult to see which backup job is doing what job.
I notice in the code that the SQL Job runs there is a "schedulename" parameter which is the same as the SQL job name, I wouldn't want to cause any issues by renaming the SQL jobs.