Our target is satisfactory restore time.  It has been our experience
that if one has adequate set up for restore the backups run just fine.
In our shop, adequate restore time requires collocation.  That said, in
my shop one must also take into account workplace politics.  If that is
not the case at your place of employment, good for you!

That begs the question of why a collocated session can not have
multiple backup threads.  In my ideal design of things, if a collocated
backup uses multiple sessions/threads, then it uses multiple tapes
instead of having one session wait until the 1st is done with a single
tape.

David

>>> acit AT ATTGLOBAL DOT NET 06/13/03 12:57AM >>>
What is your *exact* target - collocation, IBM/Tivoli happiness or
faster
backups/restores. Have in mind that even IBMers are human beings and
can
err. Sometimes disabling collocation might give *improvements*
(usually
does not)

Zlatko Krastev
IT Consultant






David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12.06.2003 15:29
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: MediaW


IBM/TSM reps spent a lot of capital and management spent a lot of
money
to get us to an environment where we COULD collocate.  There's no
going
back now.

David

>>> acit AT ATTGLOBAL DOT NET 06/12/03 03:21AM >>>
David,

why not to create another primary pool and direct that node in such
"own"
pool (or shared with few similar requirements nodes). Setting
collocation
off will have little or no impact on your restores. In fact allowing
backups to parallelize, you will set the ground for parallel restores.

Zlatko Krastev
IT Consultant






David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11.06.2003 17:56
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: MediaW


Thanks Geoff.  We'd much rather have the session wait during backups
than during restore so we'll leave collocation on and ignore the
MediaW.

David

>>> geoff.raymer AT EDS DOT COM 06/11/03 10:32AM >>>
David,

We have had these same types of problems when collocation is set to
yes.
Try turning it off and running your backup again, I bet you will see
it
pick
up more drives.

Geoff

-----Original Message-----
From: David E Ehresman [mailto:deehre01 AT LOUISVILLE DOT EDU]
Sent: Wednesday, June 11, 2003 9:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: MediaW


Collocation is set YES.  Can collocation not go to multiple tapes?

>>> geoff.raymer AT EDS DOT COM 06/10/03 03:44PM >>>
David,

Have you verified that collocation is set to NO on the tape storage
pool
that this client is backing up to.

Geoff Raymer
EDS - Tulsa BUR and Leveraged Storage
MS 326
4000 N. Mingo Road
Tulsa, OK  74116-5020

* phone: +01-918-292-4364
* cell: +01-918-629-1819
* mailto:geoff.raymer AT eds DOT com
www.eds.com



-----Original Message-----
From: David E Ehresman [mailto:deehre01 AT LOUISVILLE DOT EDU]
Sent: Tuesday, June 10, 2003 2:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: MediaW


I have a client node that backs up over the lan to tape.  When I do a
Q
SESS during a backup, there are 3-4 sessions running.  One session has
a
tape mounted but one of the others remains in MediaW.  The node has
Maximum Mount Points Allowed: 2 defined.  The device class has Mount
Limit: DRIVES defined.  There are empty tape drives available.  Any
ideas why a tape is not being mounted?

TSM server is TSM 5.1.6.3 running on AIX 5.1 64 bit mode.  Client is
TSM 5.1.5.11 running on Aix 5.1 32 bit mode.

David Ehresman