Bradberry, Kenneth wrote:

Sorry forgot to mention this is an HPUX client running 5.1.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rushforth, Tim
Sent: Tuesday, October 12, 2004 5:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Multi-Session Restore vs. Multi-Session backup.

Yes - for windows clients - see resourceutilization in the client
manual.

-----Original Message-----
From: Bradberry, Kenneth
[mailto:Kenneth_Bradberry AT SUPERIORCONSULTANT DOT COM]
Sent: Tuesday, October 12, 2004 4:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Multi-Session Restore vs. Multi-Session backup.

I understand the multi-session restore concept, can I increase the
number of backup session by increasing the number of sessions that can
be opened for a client?  I have to backup a system across a WAN link and
I want to maximize the bandwidth utilization, multy threaded backups
appears to be one way to do that.  I have about 70GB to transfer via a
22Mb link.  Any ideas would be appreciated.

Thanks,

Ken B.

Ken,

Just turn up resource utilization on the client.  A couple of things to
look out for, make sure that you have enough sessions available
(maxsessions and maxschedssions on the TSM server) and if you are going
directly to tape make sure you have enough mount points to handle all of
the sessions this is set on a per node basis and of course you will need
to have that many drives available.  However if you are going straight
to the diskpool this should not be a problem.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===============================================================================