Text item: Body.822
I will assume that by 'archiving tapes' you mean that you are using the
copypool feature.

There is no simple ADSM command which will give you what you want.  If you
are collocating your primary tapepool, there is a procedure which can help.

Do a 'q vol stg=<primary_tapepool_name>'.  Capture the output and massage
it into a macro with one line for each volume like 'q content <volser>
count=1'.  Run this macro, it will run for a long time, and capture the
output.  Now scan the output to find the nodename in question.  This will
identify the primary volumes used by the node.

Finally, for each volume, do the command 'restore volume <volser>
preview=yes'.  This will report the volumes which needed to be accessed but
could not be because they were offsite.  Bring them onsite, mark them
'access=readonly' and you can do the restore.

Note that your tapepool must be 'strictly collocated' for this to work all
the time.  This means that the server could always get a new empty tape
when it needed one, and never had to put files for one node on a tape used
by another node.

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.


_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Archiving and tape recall
06-09-1997 04:26 PM

Date: Mon, 09 Jun 1997 16:26:52 -0600
From: "Larimer, Dave" <Dave_Larimer AT kne DOT com>
Subject: Archiving and tape recall
To: ADSM-L AT vm.marist DOT edu

To all ADSMer's;

        I have a question to put forth to the group.  I have a version 2 VM
ADSM server with a 5000+ tape library.  I am archiving tapes and sending
them offsite.  I wish to retrieve and restore all the data from a node.
 The problem is that I don't know what tapes to call back from offsite
storage so that I can have them available for the retrieval process.
Does anyone know of a way to get a list of archived tapes by node, or
what tapes ADSM will call back for the retrieve?   Just to let you know
Q VOLHISTORY NODE=XXXX does not work. It gives me an invalid parameter
"NODE."

Dave Larimer
Technical Specialist
KNEnergy, Inc.
Dave_Larimer AT kne DOT com