We are using the ADSM SQL Connect Agent (or TSM SQL Data Protection Agents)
to do our backups. Our DBA's are scheduling and running the backups with
SQL jobs that they have setup through the SQL Enterprise Manager. Then they
can have the status of the backup jobs emailed to them through SQL Mail.
As far as issuing "net" commands in pre/post, I would assume that at a
minimum you would have to configure the ADSM/TSM "Central Scheduler Agent"
and/or the "Client Acceptor" to run as an NT account with the required
privilege to stop/start services. Just a guess...
Phil Bone
Sr. Systems Consultant
Network Services, Infrastructure Management
Office: 706.596.5928
Fax: 706.596.5950
Email: [EMAIL PROTECTED]
Email: [EMAIL PROTECTED]
-----Original Message-----
From: Gary Ison [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 15, 2000 8:08 AM
To: [EMAIL PROTECTED]
Subject: Base TMS client and SQL backup question
Hi Folks,
Is anyone using the pre/post exits of the base client to stop/start
the MSSQL server with the "net stop/start mssqlserver" commands? I have a
client who is trying this and the schedule log stops recording when the pre
command file is triggered. The client has also failed to back up since this
method was implemented.
If you are not using the net commands, how are you using the
pre/post (or other methods) commands to stop the SQL server so the databases
can be backed up? Any help or examples would be greatly appreciated.
Thanks.
Gary L. Ison
Governor's Office for Technology
101 Cold Harbor Drive
Frankfort, Ky. 40601
Phone: (502) 564-8724
Fax: (502) 564-6856
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
