This is just one tip for the next time, if it happens again. I hope don't. Any way, you can create more than one device config and volume history in dsmserv.opt. And after a DB backup you can execute the backup of devconfig and volhistory without informing the file. When you don't inform the TSM Server does a backup on those files that are defined on dsmserv.opt.
Regards, Anderson ----- Original Message ----- From: "Luke Dahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 23, 2003 6:13 PM Subject: Server Down - Urgent Request > Hi All, > Server level: 5.1.5.1 > Server OS: Solaris 2.8 > Direct attached to a 3494 with SCSI attached 3590 Drives > > Issue: We unfortunately lost two disks on a RAID 5 array that contained > the database, recovery log, and primary diskpools. Compounding the > problem the volhist.bak and devconfig.bak files were stored on the same > disk array (we had a nightly script in place to copy to an AFS location > but it had been disabled due to maintenance previously). So, my > question is, how can I determine which tape volume my database backup > from yesterday is on? Is there a way using the interface on the 3494? > Any other thoughts or suggestions? I'm currently configuring the > storage array for use and will need to execute a restore db command > fairly soon. Many thanks in advance - I never thought I could have two > simultaneous disk failures in a RAID 5 array as well as our DR script > disabled at the same time... > > Luke Dahl > NASA-Jet Propulsion Laboratory > 818-645-5684
