I think I'm looking at this right, but I wanted to check before I start changing a bunch of schedules.
I have several large file servers, mostly around 20TB each. The backup jobs are reverse incremental, and have backup to tape jobs on an LTO-6 autoloader. Each job does an active full once a month on Saturday (which is a 14 hour job), and incrementals runs through the week (not the weekend). The tape job usually takes 40+ hours. To fit it all in one tape job, up until now I've been doing (for example) the FS-01 job on one weekend, maintaining 7 days of rollbacks, and scheduling the tape job for the following weekend, also Saturday. This didn't work great since sometimes there would be two .vbk files and the autoloader would try to write 40TB to tape, without enough tapes.
So, you can imagine I was excited about the new feature in v9 that only writes the most recent backup chain to tape. I'm thinking there's a better approach to all this, hinging on that feature. I'm thinking I could move the active full jobs to various Fridays, and schedule the linked tape job for the same time. Then, in the schedule options, set the tape job to wait for up to say 1200 minutes - 20 hours will be more than enough. That way, the tape job can automatically start sometime Saturday morning, and have plenty of time to finish over the weekend instead of wrapping up Monday like they're prone to now. This will also mean Veeam won't waste time and fail jobs because it tried to write 40TB+ of .vbk to a pool that doesn't have that kind of space. And as an added bonus, the tape will be the most recent .vbk, not one that was written and added to over the course of a week.
It makes sense in my head. Am I reading this right, or would this layout not work?