tags: apache   archive   business   charity   climbing   comic   communication   database   email   exchange   family   fm2008   hack   hardware   humour   linux   liverpool   microsoft   money   mysql   network   oes   opensource   outlook   php   pictures   process   project   quote   real_life   review   rss   science   security   software   thought   tsm   updates   webdev   website   windows  

Hints and Tips 2 - TSM

Thu, 13 Dec 2007 02:56:58

You experience a database corruption and do a point in time restore(PIT). Any storage pool media that was written to after the PIT is now invalid/damaged data. We resolve this by running an audit of the storage pool. The simple rule of thumb is once you've restored your TSM database, "disable sessions" so clients can't write any data, then run an "audit volume stgpool=FISH", FISH is the only parameter you need to change for you envioronment. Also audit your tape library if any tapes were used after the DB backup, you can check this by reviewing your volhist file before restoring your DB (it will be overwritten afterwards). Once auditing is complete and the server is healthy, "enable sessions".

Cheers
Ryan Partington