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
We schedule SQL Manager Studio do the actual SQL backups, and then we have TSM
back those up and archive.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David
Ehresman
Sent: Wednesday, January 14, 2015 3:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject:
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 ea
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
