Group: Forum Members
If all of those schedules are on the same job sending backups to the same destination, then that doesn't make sense at all. Running all of those schedules on the same job would likely make a mess in terms of the retention policy too, since you'd have multiple schedules all contributing to the same backup sets, but the retention policy would evaluate the "aggregate" backups available at the destination rather than operating on a per-schedule basis. If you need a complex schedule, then you should just create one from scratch rather than relying on a template. But I can't think of any good use case for using multiple templates like that.