I personally prefer the mixed scenario:
- using include/exclude list of the API client metadata is sent to a
dedicated disk pool (which *does not* migrate to tape)
- full and differential backups go direct to tape
- transaction log backups go to another disk pool which in turn migrates
to tape

As any other solution this has its drawbacks, but I like it and it works
(knock on wood, we been hit once by a bug. Thank you for helping us to
resolve it, Del).

Zlatko Krastev
IT Consultant






Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09.12.2003 19:55
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: SQL TDP configurations


Dave,

I find this to be a mix. That is, there are some customers
backing their SQL databases to disk first, then migrating
them to tape. There are other customers backing them up
directly to tape. There is no "correct" answer, because it
depends on your service level agreements, your TSM Server
infrastructure, whether you are using Data Protection
for SQL backup striping, colocation settings, backup strategy, etc.
Maybe others on this list can share the techniques
that work best for them.

Thanks,

Del

----------------------------------------------------

> It looks like our particular problem is with the machine itself.
>
> I guess the origin of the question start because, is backing up the SQL
> databases straight to tape the correct thing to do?  What is everyone
> else doing?