One way to get multi-restore to work is to collocate on filesystems in the
tape pool.  If one collocates to the node then the problem that your
discussed happens.  This is a designation of the pool so all nodes going to
this tape pool will be collocated by filesspace and that can eat a lot of
tapes.  Another way is to logically break up your server into say four
nodes.  Each node has a domain/excludes/includes that limits it to certain
set of filesystems.  As long as the pool that they are going to is
collocated by node, they can go to the same tape pool.  Now during restores
there is no contention for the same tape.

Hope that helps


--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
phillip.ford AT spcorp DOT com





-----Original Message-----
From: MC Matt Cooper (2838) [mailto:Matt.Cooper AT AMGREETINGS DOT COM]
Sent: Thursday, July 17, 2003 8:48 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Multi session backup restore question


Hello all,
        I am trying to work in a multi session backup and be able to use a
multi session restore.  What I have found is that with the
maxresourceutilization set to 8 that my 350GB 8 processor AIX client is
using only 4 data sessions and 4 control sessions.   The data all goes to
the disk pool and then the migration will use only 1 tape drive for this
data.  I then assume a multi session restore is not going to work.

1)      how can I get this backup to use more sessions for data transfer?
2)      Am I correct in believing that the multi-session restore is out
because of the actions of the migration process?  MUST this go direct to
tape to have multi session backup and RESTORE?

Thanks in advance,
Matt


*********************************************************************
This message and any attachments are solely for the intended recipient. If you 
are not the intended recipient, disclosure, copying, use or distribution of the 
information included in this message is prohibited -- Please immediately and 
permanently delete.