"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/16/2008
10:16:38 AM:
> But many times, overlap can't be avoided.
Exactly.
- we run expiration around the clock.
- If the disk pool fills, we've got migrations running along with backups.
- We run movedata/reclamation around the clock. (we coded our own
move data script to handle reclamation since it is brain dead on
picking
tapes to process.)
- Backups run mostly over night, but Oracle log backups that are pushed
to TSM occur around the clock.
- Of course, the are probably restores in here somewhere.
Partly this was caused by letting a couple TSM servers to grow too big
before
we finally started bringing up more instances. But, in general, TSM
handles
it VERY well. We get an occasional deadlock condition, and movedata's
often
fail due to tape contention (and get retried in a couple hour). What has
NOT
happened is any data corruption problems (db/log or backups/archives).
My experience: Don't be afraid to push TSM. But you will run into problem
when you push too far (disk contention, tape/drive contention, deadlocks,
log pins).
Rick
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
