Zoltan,
We are all eager to know if the something that happened had anything to do with 
TSM 6.3.2 or DB2. Since they seem to be fine and the OS needs to be rebuilt, 
presumably not. Sometimes i's and t's beg to dotted and crosed.

Best wishes,
Keith Arbogast
Indiana University

 
On Mar 10, 2014, at 10:55 AM, Zoltan Forray wrote:

> We recently had our offsite/recover TSM server (RH Linux 6.4, TSM
> 6.3.4.200) go south.  Something happened that caused DB2 to start
> crashing/dumping and subsequently completely filled the filesystem
> containing /home/tsminst1 directory.  Since this was the root folder, the
> system tanked and is now unrecoverable.  My OS guy says the root system
> seems to be corrupted and will probably require a complete OS reinstall.
> 
> However, the filesystems containing the TSM DB, LOG and ARCHLOG files all
> seem to be OK.
> 
> Since this is an offsite, non-critical server that simply stored DB
> Snapshots of my other production TSM servers, nuking and rebuilding is not
> a big deal, mostly lots of busy-work.  This could also give me the
> opportunity to install and play with 7.1.
> 
> I would like to make this a "DR recovery" scenario/test.  Since the DB is
> still there, can it be recovered from what remains, i.e. the /TSMDB,
> /TSMLOG, /TSMARCHLOG filesystems?
> 
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html