It sounds like the main thing you'll need is to restore your TSM database. Having a backup of your volhistory and devconfig files would help but if you have a small site you might be able to do it from memory.
If you are using DISK-type diskpools, you'll want to treat them as destroyed since volumes are not log-structured like FILE-type volumes are. On Tue, Jan 27, 2015 at 09:15:34AM -0800, Andrew Ferris wrote: > Hello ADSM-ers, > > Our ancient 5.5 (EOL I know) TSM server on windows just corrupted it's C: > drive (so OS + Server Program Files) but everything else is fine - the > diskpools, the logs, the db files, the library, etc. I even have copies of > dsmserv.opt, devconfig.out, and volhist.out. I have a plan file but I would > prefer to pull back as few tapes as possible from offsite. > > What would be the quickest way to restore TSM given the large amount of > non-destroyed material I have? > > Sorry my DRM skills are so rusty. > > thanks, > Andrew Ferris > Network & System Management > UBC Centre for Heart & Lung Innovation > St. Paul's Hospital, Vancouver > http://www.hli.ubc.ca > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
