> Wanda,
> thanks for your fast reply!
>
> We would like to get the best of both worlds.
> Until now our SQL DBAs used SQL management studio to write their backups
> to disk.
> Now they would like to use the same Maintenance Plans to backup their
> databases writing directly to TSM.
>
> Our oracle DBAs do all their management (including scheduling backups and
> checking backup success) using the oracle enterprise manager.
> So our SQL DBAs would like to do all management tasks using the management
> studio.
>
> Do you think this is possible?

No, I don't think so.  The Oracle Enterprise Manager (RMAN) does the
Oracle backups; the TSM Oracle TDP just makes TSM look like a funny tape
driver to RMAN.  So RMAN is doing what it normally does.

The TSM SQL TDP is actually a client itself, it does the backup.  I don't
believe there is any way to make the SQL enterprise manager talk directly
to TSM (unless Microsoft is willing to provide it!)

I think your best bet is to just let TSM back up the flat files that SQL
Enterprise Manager produces. Then the DBA's can use the SQL Enterprise
Manager for everything, assuming they have the available disk space.

W



Does this make sense?
>
> Thanks a lot
> Thomas Rupp
>
> -----Ursprüngliche Nachricht-----
> Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
> von
> Wanda Prather
> Gesendet: Dienstag, 03. Juli 2007 17:37
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: [ADSM-L] Manage backup of MS SQL 2005 server with TDP from
> SQL
>
>
> Personally, I don't see the point of using the SQL management studio AND
> the TDP together.
>
> The SQL Maintenance plan creates an exported copy of the SQL data base(s)
> into the SQL BACKUPS directory.  These are unlocked, flat files that the
> regular TSM backup client can back up just fine.
>
> IF you have enough disk space to keep a couple of generations of those SQL
> backups on your SQL server, it works out very nicely.  The SQL maintenance
> plan specifies how many generations to keep in that directory, and SQL
> purges  the old copies from the directory.
>
> If you set up a management class so that TSM keeps versions of the flat
> files that SQL purges for several more generations, you have an ideal
> situation - the SQL DBA can restore back a day or 2 with SQL tools,
> without involving TSM.
>
> If they need to go back further than that, they can use TSM to restore the
> older flat file copies back to the BACKUPS directory, then restore those
> versions using the SQL tools.  It's a very clean setup; I especially
> recommend doing it this way when the SQL application is a 3rd party
> product.  If the DBA never uses anything but the SQL tools to do the
> restores, you never get into "finger pointing" situations if there is data
> corruption.
>
> You would use the TDP INSTEAD of the SQL maintenance tool, if you can't
> afford the disk space on the SQL server to do the backups there.  With the
> TDP you can send your backups direct to tape; use Lan Free, etc.
>
> Just my 2c.
> Wanda
>
>
>
>
>
>
>
>
>> Hi TSM-ers,
>>
>> I have to backup our MS SQL 2005 server with TDP and was asked how TDP
>> can be integrated in the MS SQL Maintenance Plans.
>>
>> Our SAP backups are scheduled by SAP
>> Our Oracle backups are scheduled by OEM
>> Our SQL backups should be scheduled by the MS SQL Management Studio
>>
>> I'm no MS SQL guy so I would like to hear how you schedule your SQL
>> backups.
>>
>> Thanks in advance
>> Thomas Rupp
>>
>>
>>
>> Vorarlberger Illwerke AG ein Unternehmen von illwerke vkw
>> Rechtsform: Aktiengesellschaft, Sitz: Bregenz, Firmenbuchnummer: FN
>> 59202
>> m, Firmenbuchgericht: LG Feldkirch, UID-Nr.: ATU 36737402
>>
>
>
> Vorarlberger Illwerke AG ein Unternehmen von illwerke vkw
> Rechtsform: Aktiengesellschaft, Sitz: Bregenz, Firmenbuchnummer: FN 59202
> m, Firmenbuchgericht: LG Feldkirch, UID-Nr.: ATU 36737402
>