ADSM-L

SQL TDP backup not running and......

2003-02-06 11:09:18
Subject: SQL TDP backup not running and......
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Feb 2003 11:09:07 -0500
When the schedule returns a "-1", it still reports as being
successful.......

Got this box that backs-up MS-SQL using the TDP (5.1.5).   TSM client is
5.1.5.0 (yes, I am scheduling an update).

For no reason we can fathom, the SQL scheduled backups stopped working on
01/31/03.

When I check the TSM server logs, I see:

02/06/2003 00:21:43   ANR2507I Schedule BACKUP.ACADNT8.SQL for domain
UCS_NETWARE_SERVER started at 02/05/2003 23:30:00 for node ACADNT8
completed successfully at 02/06/2003 00:21:43.

This is confusing since the DSMSCHED.LOG file says:

02/06/2003 00:23:02 Executing Operating System command or script:
   D:\Program Files\TIVOLI\TSM\TDPSQL\sqlfull.cmd
02/06/2003 00:23:02 Finished command.  Return code is: 1
02/06/2003 00:23:02 ANS1909E The scheduled command failed.
02/06/2003 00:23:03 ANS1512E Scheduled event 'BACKUP.ACADNT8.SQL' failed.
Return code = 1.
02/06/2003 00:23:03 Sending results for scheduled event
'BACKUP.ACADNT8.SQL'.
02/06/2003 00:23:03 Results sent to server for scheduled event
'BACKUP.ACADNT8.SQL'.

DSIERROR.LOG agrees:

02/06/2003 00:23:03 ANS1909E The scheduled command failed.
02/06/2003 00:23:03 ANS1512E Scheduled event 'BACKUP.ACADNT8.SQL' failed.
Return code = 1.

Since the SQLFULL.CMD file pipes to a logfile called SQLFULL.LOG, I
checked it. Nothing since the 31st until when I ran the SQLFULL.CMD file
manually, this morning:

01/31/2003 23:47:45 Elapsed processing time:                  184.21 Secs
02/06/2003 09:54:51 ============== Log file pruned using log retention
period of 60 day(s)


So, what gives ?

<Prev in Thread] Current Thread [Next in Thread>