If you are on NetBackup 7.6 or above you will be fine.
In earlier versions they would fail with a missed backup window but after NBU 7.6 they are fine
With earlier versions you can tick the "Run after runday" box on the schedule to get around it
Tunix, we are backing up file servers with tens of TB to tape. Some backup jobs take like 30h (800GB, optimising this is my next step but I asked Veritas and this probably is because we are backing up tons of small files at 3MB/s, and they couldn't give me any advice on how to optimise this)
So those jobs block the drive (I multiplex 3 jobs to tape at the moment) for quite a long time, believe me, full backups of this server in particular will take 40-50 hours easily.
If I leave small execution windows my jobs will fail with error code 196, hence the big execution window.
---
Mark, glad to hear they will run just fine. I'll keep an eye anyway. Do you state they will be ok based on experience or is there any documentation confirming this?
Also, my case is similar to what you describe. I have a robot assigned exclusively to this server, and it has 3 jobs with multiple data streams hence NBU creates a child job for each item in the backup selection. This is how I want it to behave as it allows me to restart specific jobs if they fail, not the whole thing.
