Came in to find this has happened again this morning, but stopped on one of the endpoint jobs rather than the backup job. (The tape job contains 4 small endpoint jobs + the main backup job).
Once again one of the jobs is sitting at 0% saying "All tape drives are in use. Waiting for a drive to become available..." and a tape is sitting in the drive but I don't know of any way to eject it to a slot (this is an MSL2024) so it can load another tape.
Have now logged as 01808088
I've now noticed that for some reason the job had decided to back up all of the files related to the Endpoint job in question, i.e. both the .vbk and all the .vib files. This isn't much of an issue for me as it's only small anyway but as mentioned above it seemed the same with the full job yesterday (re-backed up a recent chain of full & incremental points). My tape jobs are configured with a "Full" media pool and an "Incremental" media pool, so these symptoms suggest to me that the tape job can sometimes get confused when a job contains BOTH .vbk AND .vib files. And yet I know that if I cancel the job now to "un-stick" it, then retry it, it'll still know that it needs to back up the same combination of files but will just get on with it, swapping tapes as required.
[New Sig: PLEASE get GFS tape support for incrementals!!!]