>> On Fri, 10 Feb 2006 09:23:35 -0500, Richard Mochnaczewski <[EMAIL
>> PROTECTED]> said:
> Thanks for the info. What's even stranger is I can launch the same
> type of process using another storage pool ( backup stgpool prd_disk
> prd_dr maxpr=4 ) and it WILL use 4 tape drives and multithread ?
On other thing I noticed : There are no drives in use at all when I launch the
command, so why not launch the four threads if there is no tape drive
contention ?
Rich
-Original Message-
From: Richard Mochnaczewski
Sent: Friday, February 10, 2006 9:24 AM
To: 'ADSM: Dist Stor Manager'
Su
I'll guess what may be happening here.
The TSM server runs the 'backup storagepool' and 'migrate' commands on
a "per node" basis. Meaning that if you set it to 4 sessions, TSM will look at
the storage pool, pick the node with the most data and start to duplicate that
data, it w
Hi Richard,
Thanks for the info. What's even stranger is I can launch the same type of
process using another storage pool ( backup stgpool prd_disk prd_dr maxpr=4 )
and it WILL use 4 tape drives and multithread ?!?!?!?
Rich
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAI
On Feb 10, 2006, at 8:53 AM, Richard Mochnaczewski wrote:
Why does it always default to one process instead of multiple
sessions as I initiate ?
A question that keeps coming up... Some prevailing factors:
The operation is node-oriented, which limits the actual number of
operating processes; a