The TDP provides a few things:

- versioning
- easy restore
- shortest path between the live database and the final destination of the 
backup, thus the lowest number of things that can go wrong

Everybody always prefers to do things the way they've always been done. Nobody 
likes changes.

Dumping a db to disk, and then moving/copying that data to TSM means that you 
spend a bit of money on the diskspace that you need for the dumps. With big 
databases, that might be quite a bit of money. Also, because the dumps have to 
be complete before you can copy the data to TSM, there is an additional window 
for data-loss.

It makes no sense implementing a TDP for a single 2kb database, but neither 
does it to dedicate an additional few TB of disk to keep your dumps and then 
copy them to TSM. There is no single truth, it all depends. I like TDP, I like 
to have all backup related logging at the TSM server, even if the backups 
aren't scheduled by TSM. I like to be able to tell my customers 'if it's in 
TSM, it can be restored'. Now how do you guarantee the quality of a two-step 
process? What if the intermediate disk is full, or broken, or????? Who will 
check the consistency of the dumps?

On 9 jun 2010, at 21:04, Tyree, David wrote:

>               I was talking about backups with a couple of our DBAs
> and they mentioned using SQL scripts on the server to export the
> database and then use the regular TSM client to backup the exported file
> instead of using the TDP. 
> 
>               They suggested building a server with a bunch of shares,
> one share for each of our SQL servers. Then go into each of the SQL
> servers and set up a script that dumps the database to share that was
> created for it. The dump location would have the regular TSM client
> running to catch all the incoming SQL files. 
> 
>               The DBAs did some db dumps and also some log dumps as
> well and were able to restore them back into the server and they seemed
> happy with the process. 
> 
>               Is there anything I'm missing here? It seems like a
> reasonable idea to me. 
> 
> 
> 
> David Tyree 
> Interface Analyst 
> South Georgia Medical Center 
> 229.333.1155 
> 
> Confidential Notice:  This e-mail message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain
> confidential and privileged information.  Any unauthorized review, use,
> disclosure or distribution is prohibited.  If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of the original message.

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622