I mean "media wait" not "session wait" in my previous message. What's even
weirder is that setting maxprocess=2 kicks off 2 "Backup Storage Pool"
processes which each both create new virtual volumes. It just doesn't make
any sense to me that on the remote TSM system, it still asks for the same
volume for both of these sessions. I seriously doubt that the same volume
on the remote system could be in 2 different virtual volumes on the local
system which sounds even more like a bug to me.
John




                      John C Dury
                                               To:       ADSM-L
                      04/02/2003 10:24         cc:
                      AM                       Subject:  Re: problem with 
backup stgpool and maxprocess=2





I currently have my migprocess=3 which works fine and mounts 3 tapes when
migrating data from my primary disk pool. When I run the "backup stgpool
primarytapepool offsitedrpool maxprocess=2" command, TSM on the remote site
immediately requests the mounting of the same tape twice. Of course only
one of the sessions gets the tape and then the other session goes into
"session wait". This sure sounds like a bug to me or maybe I have something
configured wrong. I was hoping that TSM on the remote site would mount 2
separate scratches and then include them both in the same virtual volume.
Otherwise the "maxprocess=2" is pretty much useless if it's always going to
fight itself over the same tapes.
John


 If you use migproc=2 when you dump your diskpool then that will write two=  
two tapes, which
 will then get used in parallel by backup stg.

 Steve.

 >>> matt AT UKY DOT EDU 02/04/2003 8:04:10 >>>
 At 10:28 AM -0500 4/1/03, John C Dury wrote:
 >When I changed MAXPROCESS=3D2, it kicked off 2 "Backup Storage Pool"
 >processes which is what I expected but on the secondary system, the 2
 >sessions are both asking for the same volume to be mounted so only one is
 >actually writing data and the other is just waiting for the tape from the
 >active process.

 I had the same problem, and reported it to TSM support.  Their answer
 was basically "That's just the way it works".

 >Obviously this isn't going to help get the data from my
 >production system to my backup system any faster.

 I think it does help some.  My understanding (which could be wrong)
 is that mostly you get lucky and it mounts two input tapes and two
 output tapes, but occasionally you get both processes trying to read
 the same input tape.
 --