And:
Suppose you are in enough trouble that you need to restore your DB from
tape, the last thing you need to worry about is having a media problem on
that tape!  Even the best, most reliable tape drives, will sometimes eat a
tape.
Then ....  you're toast.
It's the old saying "Don't put all your eggs in one tape".





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Wednesday, September 15, 2004 10:36 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: each dbbackup to new tape?


Its designed to work that way.  I assume the reasoning is that you want
to keep db backups offsite so you can recover your db in case of a
disaster.  If so, you want to start each db backup on a new tape so that
it can go offsite.


>>> lgreis AT MKV DOT DE 9/15/2004 9:13:46 AM >>>
Hi list,

I'm rather green with TSM, actually working through my first
client-project with it and have come to a (small for sure) problem
System: TSM 5.2 on SuSe SLES8, feeding an Adic Scalar24 with one
IBM-LTO2.
Basically, the system works.
Whenever I command a dbBackup, wether full or incremetal, TSM wants to
write to a scratch tape only. If i give the volser of a tape used for
an
earlier dbbackup explicitly, TSM says the tape is full (which it is
not).
Can someone point me to the right direction?

Regards, Lucian Greis
MKV GmbH