Since the TSM server is running on the node you want to restore on, why not just let the server serve the backupset to its own client?
[EMAIL PROTECTED] /home/tconway>runtsm q backupset flatus IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 4, Level 0.2 (c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved. Session established with server TSM: AIX-RS/6000 Server Version 5, Release 4, Level 2.0 Server date/time: 09/18/2008 09:06:55 Last access: 09/18/2008 09:00:00 ANS8000I Server command: 'q backupset flatus' Node Name Backup Set Name Data Type Date/Time Retention Device Description Has Table Period Class Name of Conten- ts (TOC)? --------------- --------------- --------------- -------------------- --------- ---------- --------------- ---------- FLATUS ADHOC.229578405 File 09/15/2008 10:30:01 365 SINGLESTR- No Description Yes EAM ANS8002I Highest return code was 0. [EMAIL PROTECTED] /home/tconway>dsmc q backupset IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface Client Version 5, Release 4, Level 0.2 Client date/time: 09/18/2008 09:07:06 (c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved. Node Name: FLATUS Session established with server TSM: AIX-RS/6000 Server Version 5, Release 4, Level 2.0 Data compression forced on by the server Server date/time: 09/18/2008 09:07:06 Last access: 09/18/2008 09:06:33 Backup Set Name Generation Date Retention Description ------------------------------ ------------------- ---------- ----------- 1 ADHOC.229578405 09/15/2008 10:30:01 365 No Description [EMAIL PROTECTED] /home/tconway> -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: Friday, September 12, 2008 1:31 PM To: [email protected] Subject: Re: [ADSM-L] Restore backupset -----Sam Sheppard wrote: ----- >We have a Solaris server on which we generated a backupset from the >backups created from the Solaris client on the same box. The backupset >was created on 3592 tape in a 3494 library. > >When attempting to restore the backupset from -loc=tape we specify > >RESTORE BACKUPSET "/dev/rmt/1st" -loc=tape > >and we receive the following message: > >ANS1933E Error accessing file or device '/dev/rmt/1st' > >Is it possible to restore a backupset from a device in a 3494 or must >it be a standalone drive? Would this possibly work if the TSM server >on the box was shutdown? We have done this kind of restore using a 3590 tape drive, a 3494 library, and TSM client software running under mainframe Linux. We used the mtlib command to mount the appropriate tape before executing the 'restore backupset' command. Our restore was in fact done with the TSM server down. However, we have used IBM utilities to update the microcode on TSM tape drives while TSM was running. Before running the utility on a tape drive we would update the TSM defininitions for the drive and its path to 'online=no'. When the utility was done we put the drive and path online to TSM again. I suspect that varying a drive and path offline to TSM would be sufficient to make the drive available for server- less 'restore backupset' commands.
