If you do not want to use TDP for MSSQL, you can just run regular old SQL backups (we do - they work great). All of those get copied to a folder named "SQLBackups" on one of the drives of any SQL server.
Our dsm.opt file looks like the following: Include "d:\SQLBackups\...\*" DBDUMPS EXCLUDE.DIR "c:\MSSQL7\*" EXCLUDE.DIR "d:\MSSQL7\*" That's for a SQL 7 server obviously, but the syntax is pretty much the same for a SQL2k server. Note that at the end of the include statement, I'm binding the backup files created to a specific management class different from that of the server as a whole. Feel free to not use that and just bind the whole client to a mgt class. HTH, Mike Bantz Systems Administrator Research Systems, Inc -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Del Hoobler Sent: Friday, April 02, 2004 7:05 AM To: [EMAIL PROTECTED] Subject: Re: creating an options file for a microsoft sql server Moses, Are you using Data Protection for SQL? It is a specialized TSM client that will perform online backup and restore of Microsoft SQL Server databases. The User's Guide for that book will help to explain how to set it up. http://publib.boulder.ibm.com/tividd/td/StorageManagerforDatabases5.2.1.html Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 04/02/2004 05:09:12 AM: > Have just been asked to include an SQL server into our TSM backup routine. > My problem at the moment is knowing what to exclude/include ( in terms of > file types) and the format it should take. I assume you set up the node as > a standard windows client with an SQL options file.......Please can > anybody help me ? >
