Ah ok, if you're running both monthly and weekly backups of different types, this actually gets even easier. Here's what you'd do:
- Schedule your weekly Incremental backups to run on the 1st through 4th Mondays at the desired time of day.
- Schedule your monthly Full backup to run on the Last Monday at the same time of day as above.
In this scenario, for months with four Mondays, the Incremental and Full will be scheduled to run at the same time on the same day, and Reflect itself is designed to handle this. For cases where different backup types are requested at the same time and all requested backups come from the same definition file, Reflect only runs the "highest order" backup -- so a Full would override a Diff, which would override an Incremental. It does this because this type of scheduling conflict is pretty common in backup strategies, e.g. daily Incrementals, weekly Differentials, and monthly Fulls.
If you actually WANT to get one of each backup on these types of days, then if you want the second backup to be quick and small, the Incremental would have to occur AFTER the Full. In your scenario above, the Incremental is scheduled first, which doesn't result in either backup being quick or small, because the Incremental will be a normal size, and the Full will always be the same size regardless of what backups happened right before it. By comparison, if you scheduled the Full first and the Incremental shortly thereafter, then the Incremental would indeed be quick and small because it would only have to capture changes that occurred since the last Full. But again, I think the best overall strategy is to design your schedule so that only one backup occurs on those days, and in that setup it will always be the Full, which presumably is what you'd want.
