I know I'm missing something simple here ... I have a number of jobs that 
are clone jobs. So I have a tape library with 4 drives, all of which are 
defined as devices for a media pool that is a "backup clone" pool.

I've noticed that it seems that each backup clone job will wait until 
there is a free tape drive, before writing. For example: I have JOB 1, 2, 
3, 4, 5 - all are clone jobs, defined to use AFTD disk devices. Assuming 
that all finish writing to the AFTD devices at approximately the same 
time, JOB 1,2,3,4 will each use one of the 4 tape drives to write to, and 
JOB 5 will wait until a running job finishes, before writing to the tape. 
This is *not* the case with my other library, which has 4 drives, all 
defined as part of a media pool that is *not* a backup pool. Consequently, 
all 5 of those jobs will write to the 4 tape drives at once - i.e., one of 
those jobs will be servicing 2 groups at once.

What setting am I missing, in order for my backup clone tape drives to 
service multiple sessions/jobs at once? I have "Max Parallelism" set on 
the library to 4. Where else would I look? Or can a device that is in a 
"backup clone" media pool not be used by multiple sessions/groups at one 
time?

Thanks

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER