Greetings,

I know this is "working as designed", but I was hoping someone might have a
work-a-round.

Several times over the last 10 or so years, we have had file systems on
servers cause problems and become unavailable, either through inadvertent
dismounts or hardware issues.  If we don't catch this quickly, TSM's
behavior in these cases leaves something to be desired.  TSM will assume
that we have thrown away our data and will happily inactivate all of it's
backed up objects.  When we discover the problem, we are faced with backing
up the data again (unless it was a true disk failure) and even if it is a
recovery scenario, we need to do a point in time restore, as all active data
has been inactivated (also followed by another complete backup).

What I'm looking for is ideas as to what I could do to automatically cancel
any active backup job if a file system becomes unavailable for whatever
reason.   Perhaps in some future version of TSM, a flag could be added for
each domain statement to fail the backup and keep the previously stored data
unless something explicit was entered to confirm the intent to expire.

Thanks for listening...Any thoughts?

Bob Levad
Winnebago Industries, Inc.



This electronic transmission and any documents accompanying this electronic 
transmission contain confidential information belonging to the sender.  This 
information may be legally privileged.  The information is intended only for 
the use of the individual or entity named above.  If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or the taking of any action in reliance on or regarding the contents of this 
electronically transmitted information is strictly prohibited.