That's the way or DBA prefers it. He schedules the dumps with the
database tools,
and I just back up the dump files.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tyree, David
Sent: Wednesday, June 09, 2010 12:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TDP for SQL vs SQL dumps

                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.