Listing volumes required for a restore

[jwade]

I am trying to find a way to list the volumes required to restore a file or filespace.



I do not have the library capacity to have all tapes in the library at the same time,

so there are a few tapes not in. I would like to run a command to list all volumes

required before I try the restore, so I can check in all required volumes before

running the restore, thus minimizing checking the actlog for unavailable volumes and

running to the library to checkin a required tape.



Regards,

John

[CBell]

This should help narrow it down, tape-wise. I'm sure there is a better way, but this command has helped me find tapes that were not necessarily already in the library (like you said). Hope this helps...



select distinct node_name,volume_name from volumeusage where node_name=’YOURNODE’ and stgpool_name=’YOUR_STGPOOL’

[jwade]

Thanks for the hint. If I find a solution I will let you know.



Regards,

John Wade

[jcoff01]

Hello,

You could also try this - QUERY NODEDATA Nodename stg=storgepoolname

[wirb]

Tried that just out of curiosity, doesn't work. I get UNKOWN COMMAND - QUERY NODEDATA.



This is of interest to me because we're going through a big DR project here and while I've been able to get a list of copy pool tapes using q vol * stgp=<stgp name>, I would like a listing of what tapes have which filesystems on them. Hm...something like q occu but one that has actual volume names instead of just the stgp name. And I simply don't have the time to master the SQL involved, a situation I'm sure plenty of others are in. Nothing in Code Relief addresses this. Anyone?



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>Hello,

You could also try this - QUERY NODEDATA Nodename stg=storgepoolname</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>

[tsmadm]

The quickest way I know is to actually run the restore and it will fail because the tapes are not available. In the activity log or in an operator window (dsmadmc -mountmode) the volumes required will be listed.

[robbenleaf]

The Query Nodedata command is new to TSM Server version 5.3.



CBell's Select statement works quite nicely. I just used it to narrow down the volume count of the DR tapes we need to send to our recovery site for a DR test we'll be running this weekend. The DR storage pool is pretty large, but we're only going to be recovering data from one client node after we rebuild the TSM server. The select command reduced the number of tapes to be shipped across the country by 75%.



Thanks, CBell!

[itdrew]

CBell. Thanks for sharing the scripts man. IT will save me some time.



Many thanks.

[wirb]

Here's something I came across after some (very) quick research:



First get a listing of offsite tapes



q vol * stgp=&lt;name of your copy pool>



Then to find a particular node's files on any of the tapes listed,



q cont &lt;volume name> node=&lt;yournode>



It's not quick if you have a lot of tapes, and I haven't looked for a way of querying the whole copy pool and picking out the contents and which volumes they're on, and unfortunately don't have the time to devote to finding out. I do hope this will be of use though, and maybe stimulate someone with much deeper SQL knowledge than I will ever have to post some code that would do this .

[kbock]

This is the script I use to identify which tapes a client has data stored on. Any select statement that attempts to identify which tape a client's particular file is on, would be incredibly DB intensive.



select volumeusage.volume_name, -

volumes.access, -

volumes.error_state, -

volumeusage.stgpool_name -

from volumeusage,volumes -

where volumeusage.node_name=upper('$1') and -

volumeusage.volume_name=volumes.volume_name -

group by volumeusage.volume_name, -

volumeusage.stgpool_name, -

volumes.access, -

volumes.error_state -

order by volume_name



Define a new administrative script and copy this into the body. Then run it and pass the client name as a parameter.

[LED888]

A simpler select statment to find out what tapes contains data for a node.



select volume_name from volumusage where node_name='NODE_NAME' group by volume_name



-Good Luck

Sias

[snydosaurus]

I'm in a similar spot, testing disaster recovery. Same issue here, library too small, tapepool tapes checked out and sitting in a safe, etc. Do any of the select statements below take into account active files only? If I'm restoring a certain node, it's possible 90% of my tapes contain something from a certain node. That's way more tapepool tapes than I have room to mount.