I made a poor assumption that the jobs we had today would just be managable once we moved to V13. All back end magic to get from standalone to managed.
Given we have jobs in place today, and I've updated the plug-in on all the VMs housing our SQL servers, what's the guidance from here to move from standalone to managed? The user guide isn't overly helpful in getting from A to B. More just, this is how you install fresh.
Can I manage these jobs at all?
Do we lose our jobs or need to reconfigure them?
Our are old backups still valid?
Since the plug-in is already installed is the best way to utilize the Veeam deployment kit? We have AD, but we don't have an admin account designated for connecting this way (and I don't prefer this unless we can utilize a gMSA account anyway).
1) No, you cannot manage backup jobs that were created in standalone mode.
2) No, you will not lose these jobs, and you don't need to reconfigure them. However, I recommend making sure that your backup scripts or SQL Server Agent jobs on the SQL Server side are disabled to avoid any scheduling conflicts between the existing jobs and the backup policies you’ll create on the VBR side when you switch to managed mode.
3) Yes, of course, your old backups are still valid.
4) When operating in managed mode, you create a Protection Group, and VBR will connect to the VM to deploy a certificate that will be used for future authentication attempts.
Best wishing to you as well!
And thank you for the response, this is very helpful.
It would be nice to have some scenarios in the user guide for differentiating these so that it's more clear, or is there anywhere else I can find a deeper dive that may answer these questions?
I think the only remaining questions I have as follow ups. Are:
With regards to #2, can standalone jobs still run if needed, obviously as long as they don't overlap with the managed jobs? I'm assuming the Plug-In is the same, so I would assume this to be the case. I haven't gotten far enough with it at this point to know whether I can do automated restores centrally. Even if we didn't use the managed jobs, I could still use the protection group to maintain the plug-in deployment.
Protection groups are related more to plug-in deployment and management. I'm assuming best practice is that unless there's a need to differentiate, you just create a Protection Group that's dedicated to all your SQL servers for example . There's generally no reason to dedicate a protection group to each SQL Cluster or each machine based on how I understand protection groups working.
