Wanda,

OK.  Based on the first seven tapes out of 75, it appears that TSM asks
for source tapes in order that they were FIRST WRITTEN, from old to new.
Since there is no queryable field that reports first write date, if tapes
are used in batches, as these were, then the LAST write date is a suitable
substitute and will at least identify the order of the batches.

In other words, in my case each batch of tapes consists of about four
tapes.  I know the order of the batches, but I don't necessarily know the
order within each batch.  So as long as I check in complete batches, I
ensure that the export will process all files from that batch without ever
asking for a tape from outside the library.

The tape currently being read is from the June 2001 batch.  All of the
tapes from that batch are already checked into the library.
If I check in all four tapes from the July 2001 batch, TSM will be able to
continue when it finishes with June, even though I don't know which July
tape will be loaded first.

Note that I opened a PMR on this yesterday and IBM couldn't tell me the
answer either!

Random indeed.

Tab Trepagnier
TSM Administrator
Laitram LLC







"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/24/2003 01:38 PM
Please respond to "ADSM: Dist Stor Manager"


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


I can't answer your actual question, and that's an ugly problem.
If you find the right answer, let me know!

My workaround:

Leave the tapes out of the library.
Start the EXPORT.  On my SCSI library, with the tapes checked out, I get
the
"cartridge blahblah required for use, checkin within 60 minutes" message.

One solution is to just change your MOUNTWAIT time to 1440 (24 hrs) for
the
devclass, so the mount will sit and wait until you get in to morrow
morning.


But to do what you actually asked for:

CANCEL the EXPORT.
Mark that tape as DESTROYED.
Start the EXPORT again.
On my 4.2 system, an EXPORT skips the destroyed tape and calls for the 2nd
tape.
Repeat 20 times.

Mark all the tapes back to READONLY and check them all in.

Wanda



-----Original Message-----
From: Tab Trepagnier [mailto:Tab.Trepagnier AT LAITRAM DOT COM]
Sent: Wednesday, July 23, 2003 4:24 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Export order


TSM 5.1.7.0 Server on AIX 4.3.3
Admin client 5.1.6.0 both on Win32 and AIX
Client data originally written by IRIX client 3.1.0.7

I am preparing to export permanent archives from an old IRIX node to DLT.
The source data is spread across 75 DLTs in a primary storage pool.  Those
tapes contain the contents of one filespace, but were written across a
four year period.  All tapes are out of the library - they're in a box in
my office.

I will only be able to load the source library with about 20 tapes at a
time.

A preview export is not practical because poor archived directory handling
by old ADSM versions and ADSM clients that followed circular links have
generated *billions* of objects in that filespace.  I discovered that last
week when I ran Expire Inventory with Skipdir=NO.  I killed the process
after 3 days during which it had examined 1/2 Billion objects for this one
node/filespace alone, deleting approx 1 in 1500.

What I need is the expected sequence that TSM will load the source tapes
to obtain files for export.

Is it by last written date?  If yes, then new to old, or old to new?
Is it by volume name?
Is it by quantity of data?  If yes, high to low, or low to high?

Etc.

In other words, I need to be able to load about 20 tapes in the source
library confident that they will supply all required data overnight so I
can load the correct next set the following day, until all 75 tapes have
been processed.

Thanks.

Tab Trepagnier
TSM Administrator
Laitram LLC