Good day all
I guess this question is two-fold and I’ve not really been able to find a way this can be done using a Plan.
We’re running SQL Plans that backup the DB’s in the traditional Full/Diff/TLOG format.
We have 1 SQL instance that mustn’t have it’s TLOGS backed up. My assumption is that it would need to go into it’s own Plan with TLOG slider switched off?
The second portion to this same instance is that the backups of the various DB’s don’t happen at the same time due to their size?
Is it possible to configure an instance that a DB will not start backing up until the prior one is complete and they keep cascading in this manner.
I understand you could create multiple sub-clients within each instance and assign different schedules. However, this would potentially mean that if a DB finishes sooner than the next one is scheduled to start, there’s an unused portion of the backup window. Conversely if one schedule overruns into the next, then we have 2 jobs running which we’re trying to avoid.
The only way I can think of this is to limit the stream count to 1 on an instance, and the DB’s will then queue up. This would impact performance though, too.
Best answer by Luca MarinoniView original