07-04-2012 12:49 AM
or is the same are individual jobs, between each job they lose about 15 min. everytime a new job starts?
07-04-2012 12:54 AM
Chaining jobs does not have any effect on the behaviour of the tape in a tape library. The tape will still unload between jobs.
If you chain the jobs and choose not to wait for them to complete before running the next job, then there will be no job history for that job in the results file. However, you can easily get the job history by running the BEMCLI cmdlet, Get-BEJobHistory after all the jobs are done.
P.S. Do not use caps or big fonts in your posts. This implies you are shouting and is rude.
07-05-2012 09:16 AM
If you are not using SSO, tapes are held in the tape drive for 60 seconds (by default) before being moved aftger the job completes from the drive back to their slot. If another job comes along within the 60 seconds, the tape stays mounted. If not, the tape gets dismounted. This 60 second timer can be changed in BEutility or the registry. Increasing it to 120 or 180 seconds may keep the tape mounted long enough for your next job to start and prevent the dismount/remount slowness.
If you are using SSO, the tape gets moved from the drive to the slot immediately after the job finishes to ensure that other jobs & servers have a fair chance at the shared resources.
If your autoloader is taking 15 minutes to change tapes, you may wish to investigate. Most autoloaders can change tapes in 3-5 minutes.