FW: Installing TDP for SQL 2.2

[Tyree, David]

I've got the script name correct in the schedule. I had someone else look at
it make sure I hadn't gone blind.
I'm watching the console messages go by and I see the messages showing the
session starting and then end for the node. I go back to the logs on the
client and nothing shows up as being done. All I see is an entry in the
dsmerror.log ANS1029E Communications have been dropped at the time the
schedule ran.


-Original Message-
From: Bill Maloney [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 2:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Installing TDP for SQL 2.2

David,

Make sure that script name in the schedule is identical to the name of the
script on the NT box. Check the .extension of the script.

Bill
- Original Message -
From: Tyree, David [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, April 22, 2002 1:58 PM
Subject: Installing TDP for SQL 2.2


 We are trying to install the TDP for SQL version 2.2 on to a
 WinNT4 machine running MS-SQL. So far we have the client (version
4.2.1.20)
 installed to catch all the non SQL files. It's set up to be called by the
 TSM server to run and it's doing fine. All the non SQL backups are fine.
We
 have the SQL folders set to be excluded.

 We are now trying to install the SQL part now and it does not
 want to play nice. We loaded version 2.2.0.0 and we have gotten it working
 to point where we can do a SQL backup from the command line and from
within
 the GUI. We can't get it run when it's called from the TSM server.

 The programs are all installed to the default locations and I
 ran the dsmcutil install command from the baclient folder to create a new
 scheduler service for the SQL part. I referred it to the dsm file in the
 tdpsql folder just like the docs said. I've got a schedule on the TSM
server
 set to kick off at a certain time but nothing happens.

 I've looked at the assorted log files nothing shows up.

 If I run tdpsqlc backup * full it runs just fine. Am I
missing
 something here? Do I need to call the sqlfull.cmd from one of the dsm.opt
 files?



 David Tyree
 Microcomputer Specialist
 South Georgia Medical Center
 229.333.1155

 Confidential Notice:  This e-mail message, including any attachments, is
for
 the sole use of the intended recipient(s) and may contain confidential and
 privileged information.  Any unauthorized review, use,  disclosure or
 distribution is prohibited.  If you are not the intended recipient, please
 contact the sender by reply e-mail and destroy all copies of the original
 message.

FW: Installing TDP for SQL 2.2

[Tyree, David]

Except for some minor changes it's almost exactly what it has in the book on
page 199.
Def sched current sql_webtrend desc=Webtrend SQL action=command
objects=d:\sqlfull.cmd priority=2 starttime=16:00 duration=15 duru=minutes
period=1 perunits=day dayofweek=any


-Original Message-
From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 3:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Installing TDP for SQL 2.2

David,

What do the parameters of your schedule look like on the TSM server??



Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte  Touche USA LLP
615.882.6861


-Original Message-
From: Tyree, David [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 12:58 PM
To: [EMAIL PROTECTED]
Subject: Installing TDP for SQL 2.2


We are trying to install the TDP for SQL version 2.2 on to a
WinNT4 machine running MS-SQL. So far we have the client (version 4.2.1.20)
installed to catch all the non SQL files. It's set up to be called by the
TSM server to run and it's doing fine. All the non SQL backups are fine. We
have the SQL folders set to be excluded.

We are now trying to install the SQL part now and it does not
want to play nice. We loaded version 2.2.0.0 and we have gotten it working
to point where we can do a SQL backup from the command line and from within
the GUI. We can't get it run when it's called from the TSM server.

The programs are all installed to the default locations and I
ran the dsmcutil install command from the baclient folder to create a new
scheduler service for the SQL part. I referred it to the dsm file in the
tdpsql folder just like the docs said. I've got a schedule on the TSM server
set to kick off at a certain time but nothing happens.

I've looked at the assorted log files nothing shows up.

If I run tdpsqlc backup * full it runs just fine. Am I missing
something here? Do I need to call the sqlfull.cmd from one of the dsm.opt
files?



David Tyree
Microcomputer Specialist
South Georgia Medical Center
229.333.1155

Confidential Notice:  This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, use,  disclosure or
distribution is prohibited.  If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.