Our guys have each SQL DB on a different drive on the server.

They use SQL Maintenance Plan (I think that's what it's called) to have SQL 
create a backup to a folder on the same drive as that DB.

Then, install TSM client, not the TSM  Data Protection SQL.

They configure a TSM  Option file on each drive.

One TSM "node" for each, using different listening ports.

The node backup is configured to skip the live DB, only backing up the output 
created by the SQL Maint plan.

Granted, not "live", but acceptable for our DBs.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
David Ehresman
Sent: Wednesday, January 14, 2015 2:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Scheduled SQL Backups

Has anyone done TSM Server Scheduling of SQL backups where there are multiple 
SQL databases on a single server, each using a unique TSM node name for 
backups?  Any hints?  I'm a TSM server admin but know next to nothing about SQL 
or TSM for SQL.

David

[Confidentiality notice:]
***********************************************************************
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***********************************************************************