ADSM-L

Re: [ADSM-L] TSM Scheduled SQL Backups

2015-01-14 16:06:15
Subject: Re: [ADSM-L] TSM Scheduled SQL Backups
From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 14 Jan 2015 21:04:23 +0000
Yes, Microsoft SQL Server Management Studio.

TSM client installed, but two Services created using the 'setup wizard' from 
the gui, one for the normal BAC and one for what we call SQL Cluster.  We have 
a separate .opt file on a different drive.
The service points to the same dsm.exe but with parm -optfile=d:\tsm\dsm.opt   
(and this .opt file is for the SQL backups).
And we have separate copygroup and management class for the SQL backups which 
we include in the dsm.opt on the d:


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Wednesday, January 14, 2015 3:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Scheduled SQL Backups

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.
***********************************************************************

<Prev in Thread] Current Thread [Next in Thread>