We have a few databases which are manipulated each night, typically with a restore operation involved... (don't ask me why)... this results in errors when our snapcenter scheduled hourly log backups is run... 2 or 3 hours in a row (as this restore operation is happening)....
Sadly the SnapCenter schedule is very simple at best, so you can only set when this hourly schedule should run within the hour, and not from say 01:00 to 22:00
SnapCenter creates either a SQL Server schedule or a Windows scheduler entry. Both of which can be altered to fit our needs... but the chance of this being changed as we make a change in the SnapCenter resource configuration is high...
Are there other ways we can fix this, and/or does anyone know if changed are on the way with future SnapCenter versions?
#Scheduling nightmare...
valid zinc
tawny shadow
As an alternative, perhaps the resource backup can be put into maintenance (as in paused) as a step in the restore procedure?