Our environment:
============

Server:
ADSM  V3.1.1.5
IBM R40
3494 Tape Library with 2*3590 drives

Client:
HPUX
ADSM V3.1.0.0

We have set up filespace collocation on one of our storage pools. This
storage pool only has one client with about 11 filesystems on it. There
are about 20 tapes available for this filesystem and each filesystem is
less than 1 GB. This means that each filesystem occupies one tape.

We attempted a full restore for this client by running multiple restore
sessions (11 sessions).  Since we only have two tape drives, this means
that the server can only handle two restores at one time while the
other sessions remain in "Media Wait" states.

What we found was that ADSM keeps switching between these 11 sessions.
It does two restore sessions, stops,  does a restore for another
session, stops, goes to another, comes back to the first session and so
on. Furthermore, it seems that it chooses the sessions at random. As
you can expect, the restore generated a LOT of tape mounts as each
filesystem uses an individual tape. This means that it keeps coming
back to the same tape whenever it chooses a session which it has
serviced previously.

My question is why does it not finish off one session first, after all,
as mentioned, each filesystem being restored is on an individual tape.
Is there a parameter that determines the amount of time spent each
session or is this a bug?

Thanks in advance.

Shafiee.
ADSM Support,
Brunei Shell Petroleum.