Name your backupsets intelligently when you create them. For instance, create a batch file that passes the nodename and datestamp as arguments to create backupsets with names such as FILESERVER1.01242005.
Please note: be careful when you delete old volume history entries. Do not delete the backupset entries, and you'll be able to use QUERY BACKUPSETS to find what nodes have backupsets created. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 >-----Original Message----- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Aftab Choudhry >Sent: Tuesday, January 25, 2005 3:46 PM >To: [email protected] >Subject: Tape VOlumes belonging to BAckupset > >Dear All, > >Currently I am creating backupsets for different nodes, to >send them offsite. I have created schedules for each nodes on >TSM and the only way for me to identify which tapes belong to >BackupSet, to find out volumes from table 'LIBVOLUMES' which >have last_use = backupset. >how do I find out, which backupset volume belongs to which node? >Does anyone have any such implementation? Create backupsets, >send them offsite and keep track of volumes etc. > >Best Regards, > >Aftab >
