I've been informed that this is by design and the intended behavior. That very well may be the case, and if it is, then I think the documentation and the syntax of the option in the Veeam interface should be written differently (but that's just my opinion).
Reply from tech support:
Since you have several backup jobs linked to this tape job it will wait for each individual backup job to be finished. So if one finishes it will still copy over. It will not wait for every linked job to finish with that timeout.
I guess I don't understand the use of this function then. I've read through the documentation on this and don't see anything in there that would lead me to believe that to be the case. From your response, it seems like this is the intended behavior. However, based on my interpretation of the feature, it sounds like this is a bug and not by design. If it is by design, then my personal opinion is that this is documented in a manner that is not very accurate and confusing.
The Veeam interface and documentation state this:
If 'some' linked backup 'jobs' are still running, wait for up to: XXX
Please note the emphasized 'some' and 'jobs'. I read this to mean literally, that if SOME (or any?) linked job is still running when this tape backup job starts, wait for the specified time. The fact that jobs (more than one job) is specifically used along with the use of SOME as related to linked backup jobs, suggests to me at least, that this should be waiting for all the jobs to complete and not just starting when any one of them is done.
Is this something that can be run past the development team to validate?
Reply from tech support
I checked with our other engineers to validate that it is currently working as designed.
I'm open to other suggestions and can look at the as new files appear option. Ideally, I'd like to NOT start backing up to tape until all the backups are complete as to avoid the load on the Veeam servers local disk. And I wasn't really sure how that option handled the tape media sets. I recently changed my media sets to create the tape daily instead of the original create new media every backup session. I did this because of two reasons:
1. being that my understanding of the wait on linked jobs was apparently incorrect and thus when I ran the job again to get the missed files it would create another media set and not use the existing media. The 2nd run would put the files on an 'incremental' media set instead of our 'full' media set. It also didn't maximize the use of the tapes and generally required another tape than if it had put everything together.
2. another reason was some weird failures I was getting when backing up to tape. When I would run the job again to get the missed files, I would run into the same situation as above. So as long as I ran the job again in a timely manner, the single incremental tape would have all the data on it and not require another tape.
I'm open to other suggestions on how to handle this situation - yes, I could do powershell but don't really like that as an option. In a nutshell, what i was hoping to do with the wait for linked jobs option, is.. well.. wait for the backup to disk jobs to complete before starting to backup to tape. The incrementals are always complete by the time the job kicks off, but the full backups take awhile and the time it takes to backup varies quite a bit, which is why the wait for linked backup jobs seemed like a perfect option for my use case (and apparently the OP of this thread).