At 11:57 AM +1000 4/2/03, Steve Harris wrote:
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.
Apparently not always true. We have our disk pool defined with
migproc=2. Disk pool does get dumped to multiple
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
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
I am trying to speed up the time required to backup our primary tape
stgpool to our secondary site by changing the number of process allowed.
When I changed MAXPROCESS=2, it kicked off 2 Backup Storage Pool
processes which is what I expected but on the secondary system, the 2
sessions are both
do you have enough scrach tape assigned to the tape pool?
-Original Message-
From: John C Dury [mailto:[EMAIL PROTECTED]
Sent: Tue 4/1/2003 10:28 AM
To: [EMAIL PROTECTED]
Cc:
Subject: problem with backup stgpool and maxprocess=2
At 10:28 AM -0500 4/1/03, John C Dury wrote:
When I changed MAXPROCESS=2, 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
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.
[EMAIL PROTECTED] 02/04/2003 8:04:10
At 10:28 AM -0500 4/1/03, John C Dury wrote:
When I changed MAXPROCESS=2, it kicked off 2 Backup Storage Pool
