On Dec 4, 2008, at 4:18 AM, Christian Svensson wrote:

During the backup window and we say that maybe 50% of all our
backups have run successfully and the other half is maybe in
progress or are waiting for their time slot. But middle of the
backup windows does my SAN go down and all my backups stops that
mean 50% has run OK and 50% hasn't.
Now when I try to start my TSM Server it shows up that my log files
are corrupt and I need to do a TSM Database Recovery and my latest
TSM DB Backup is from Day 1.

Whoa, Christian...  Are you saying that your TSM database is on an
unreliable SAN, rather than a far more reliable storage unit such as
local disk?  This is the problem that really needs to be addressed,
rather than secondary effects.  Your site is in great jeopardy where
its storage networking is unreliable *and* its fall-back data store
(TSM) is being crashed (and may be suffering damage you don't
immediately perceive, which could make some restorals impossible).

Any issues with client backups needs to very much take a back seat
until the manifest problems with TSM server infrastructure are
corrected.  TSM db recovery should be a very exceptional thing, and
not a routine consequence of unreliable storage.

   Richard Sims