You need to run the "restore vol <volnum> preview=yes" command. When that process completes you may have to search the activity logs, but you'll find the volumes the process needs for restore that way.
It will say something to the affect "<volnum> required for volume restore" (if you run the dsmadmc in consolemode as I do, you'll see them scroll by). I forget the exact error code to look for but it will be an ANR####I message. Record those and manually call them back from offsite. When you get them check them in as private, and then update each volume to "readonly". Update vol <volnum> access=readonly Then rerun your restore process without the preview option. See Ya' Howard > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Mcnutt, Larry E. > Sent: Tuesday, August 19, 2008 4:22 PM > To: [email protected] > Subject: [ADSM-L] Recalling drmedia volumes to restore a damaged > volume. > > TSM 5.4.3.0 > AIX 5.3 > > > Hello list, > > I have a damaged primary storage pool volume. Fortunately, the data is > on copy pool volumes. I found a nicely detailed procedure for handling > the restoral of the data from mail-archive. > http://www.mail-archive.com/adsm- > [EMAIL PROTECTED]/msg25446/adsm_restore_a > _tape_volume.doc > > The part that I do not see how to do "cleanly" is recalling the > specific > volumes from offsite using "move drmedia" commands. I know I can > manually add the volumes to the "vaultretrieve" list and remove them > from the "vault" inventory report. But that doesn't feel right. Am I > missing something? > > Thanks, > Larry McNutt > > ----------------------------------------- > This message and any attachments are intended for the individual or > entity named above. If you are not the intended recipient, please > do not forward, copy, print, use or disclose this communication to > others; also please notify the sender by replying to this message, > and then delete it from your system. The Timken Company / The > Timken Corporation
