Mark, for the regular backups, I schedule an incremental backup that
excludes the SQL directories (in DSM.OPT).   For SQL backups, I schedule a
script command that invokes the SQL API, using the DSM.OPT in the SQL
directory.  Being the SQL Agent, it only backs up the SQL databases
referenced in the script.  Oh, by the way... I had to upgrade the backup
client software to V3.1.03 to get around incompatibilities in the passwords,
between the scheduler and the SQL agent.

> ----------
> From:         Mark Reschke[SMTP:M.Reschke AT ITS.UNIMELB.EDU DOT AU]
> Sent:         Monday, May 25, 1998 8:46 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: NT SQL agent Schedule command
>
> Larry,
>
> When you set up the SQL service with the same node name as the NT server
> how
> were you able to back up both the OS and database?  Did you make the
> command
> file run a command like 'dsmc incr -password=password' or did you use
> another
> method?  I am curious about the best way to set up and manage these nodes.
> Are you able to set action=incr and still run a command file?
>
> Regards,
> Mark.
>
> Mark Reschke
> Systems Support Analyst
> Information Technology Services
> University of Melbourne
> Ph. +613 9344 5411
> Fax. +613 9347 4803
>
> mailto:M.Reschke AT its.unimelb.edu DOT au
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Kerssen, Larry
> Sent: Tuesday, 26 May 1998 13:23
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: NT SQL agent Schedule command
>
>
> I've installed the ADSM SQL Agent and set it up like this, except I use
> the
> same nodename as the archive/backup client and use the same scheduler
> service as the archive/backup client to schedule the SQL script.
>
> > ----------
> > From:         Mark Reschke[SMTP:M.Reschke AT ITS.UNIMELB.EDU DOT AU]
> > Reply To:     ADSM: Dist Stor Manager
> > Sent:         Sunday, May 24, 1998 4:56 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: NT SQL agent Schedule command
> >
> > Steve,
> >
> > In order to back up a SQL Server database you need to install the ADSM
> SQL
> > Agent in a separate directory and set up a second node name for the SQL
> > database both on the Server and in the DSM.OPT file in the SQL Agent
> > directory.  You can then schedule this new node with a second schedule
> > service
> > using the DSMCUTIL.  You then need to set up a new backup schedule
> > specifically for your SQL Servers which has action=command and executes
> > the
> > command file that you have set up to back up your database.  You then
> > merely
> > add your SQL Servers to the backup schedule you have created.  Logging
> and
> > verification of successful backup of your SQL database is almost
> > non-existent
> > so setting up your command file to do some logging for you is an
> excellent
> > idea. Del's command file performs this logging for you.
> >
> > Regards,
> > Mark.
> >
> > Mark Reschke
> > Systems Support Analyst
> > Information Technology Services
> > University of Melbourne
> > Ph. +613 9344 5411
> > Fax. +613 9347 4803
> >
> >
> > mailto:M.Reschke AT its.unimelb.edu DOT au
> >
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
> > Of
> > Mike Martin
> > Sent: Saturday, 23 May 1998 1:01
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: NT SQL agent Schedule command
> >
> >
> > Del-   ( or anyone )
> >
> > How do we get the ADSM Server scheduler to cause the
> > client to execute the command file.  (We have the NT Service
> > installed)
> >
> > Is the following correct?  Is there anything else we need?
> >
> > COMMAND=ACTION
> > OBJECTS="c:\win32app\ibm\adsm\agentsql\daily1.bat"
> >
> > ( the above doesn't seem to work )
> >
> > Thanks.   Mike Martin
> >
> >
> > >>> Del Hoobler <hoobler AT US.IBM DOT COM> 05/21 3:34 PM >>>
> > Steve,
> >
> > Here is something to get you started...
> >
> >
> > Del Hoobler
> > ADSM Agent Development
> > ===================================================
> >
> > ......sample command file was here......
> >
> >
> > >> NT SQL Connect Agent Schedule Problem
> > >>
> > >> Can anyone provide an example of the schedule command
> > >> format needed to run a SQL agent batch file?  This batch
> > >> file is located in c:\win32app\ibm\adsm\agentsql and is
> > >> named daily1.bat.
> > >>
> > >> Thanks,
> > >> Steve Norton
> > >> Srnorton AT bhset DOT org
> >
> > !
> >
> >
> >                                  !
> >
>