I don't believe there is a PREVIEW=YES for the client restore command.

Unless the access of the tape the file was on is UNAVAILABLE or DESTROYED it
should have requested the mount. Did you query the server activity log for
around the time you did the restore to see if there were any indications on
why the volume couldn't be mounted?

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Mike Bantz
Sent: Friday, August 06, 2004 4:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Indentifying archived/backed up volume numbers?


Can you try running the restore command with "preview=yes"? That **should**
give you an idea of what volumes the system will request, I believe.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Chris Hund
Sent: Friday, August 06, 2004 12:29 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Indentifying archived/backed up volume numbers?

Hi all,

I have a question related to identifying the tape or volume number that a
file (or set of files) resides on.  If I had to, for example, restore a file
from 08/01 called /home/test.file, I would identify the volume # that file
is on by doing the following:

>From the TSM command line:
tsm> rest "/home/test.file" -fromdate=08/01/2004 -todate=08/01/2004
tsm> -pick -ina

I'd pick my file from the list, and while Tivoli attempted to load the tape
that file is one, I'd do a "q req" from another telnet session to see which
tape # the machine was trying to load.

This process seems to work well some of the time, but occasionally I find
myself getting a message like:
ANS4035W File '/shared/UfsDump_20030723' currently unavailable on server ...
and then the retrieve or restore gets "**Interrupted**" and you can't find
out which tape # the file is on.

I see this same thing whether I'm doing a retrieve or a restore.  So my
question, then:  is there a better way to identify the volume # a file, or
set of files, resides on?  It sure seems like Tivoli would have come up with
a better method than this.  I'm still a Tivoli newbie, so I haven't learned
all the tricks yet.  :)  I figured if there was a better way, someone on
this list would surely know.

Many thanks,
Chris Hund