• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

How to determine the volume a specific file version lives on?


1. Is it possible to determine which tape volume a particular version of a backup lives? For example, when I run something like this in dsmc on the client:

q backup /var/cache/man/index.db -fromdate=2020-02-19 -detail

I see the usual output, but nothing to clue me in on how to decipher which tape this would be on. I do see a 'Volume ID' reported, but I've not been able to find any information on how to reference that with an actual volume name. Maybe that's in some table?

Is there any kind of unique identifier that TSM uses that can be queried? The only thing I've been able to figure out is how to use a select statement (dsmadmc) to see a list of the volumes containing the file space for a given node, but not the actual volume that contains the particular version.

2. Also, does anyone know what the inode# is when using '-detail' with `q backup`? It never matches the inode number that the OS reports (`ls -lid filename`) for that file or directory. Is this some kind of internal TSM thing that doesn't apply?


I ran a search ("volume id") on the site, and I found this:


It looks like shcart's response from June 12, 2013 is the key wherein you perform a three-step method:

1. Run a select statement on the backups table specifying the node_name, filespace_name, hl_name and ll_name

2. Using the object_id value reported in 1 above, you then run: show bfo object_id

3. Using the super-bitfile value returned from 2 above, you then run: show bfo Super-bitfile

This reports both the the PRIMARY and COPY volume names at the bottom of the output along with some other information, including the Volume ID.

I also found some other posts where others have mentioned this technique. This is all new to me. Information overload [sigh ...].

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 19.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 57 62.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 10.9%
  • Other (please comement)

    Votes: 7 7.6%

Forum statistics

Latest member