Steve,

I am still not convinced that the backups
are "succeeding".  When you say the
"SQL log" says that the backup was successful
are you referring to the SQL Agent log or the
SQL Server Log?   The fact that the
"manual" backups are working indicates
that maybe your schedule may be set up wrong...
...or maybe using different parameters than you
think it is using...
Double-check the scheduled event to make sure
it is using the correct dsm.opt file and
the nodename, comm parameters, etc.

Also, the SQL Agent 1.1.1 (PTF IP21419) added
ADSM V3 Server activity logging for SQL Agent backups.
This will let you see the actual start and end
of each DB backup.

After doing that, if things still don't make sense,
please call IBM service.  It will enable us
to get the proper files and traces needed
to diagnose this in the quickest possible fashion.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com

>

Del,
> Thanks for your reply about the missing database problem.
>
> Here is some more info on the problem.
>
> Note that I do have ver 1.1 but not with the PTF ip2149.
> Every thing worked fine for the first few months with
> only a few failures related to storage space and tape mounts.
> The only change made to the option file was I turned on
> the wait for tape mount option.
>
> The database names do have upper and lower case
> characters but no non-standard characters.
>
> I backup 8 sql databases with a schedule which executes
> a command to start the backup.
>
> Both the ADSM log and the SQL log say the scheduled
> backup was successful
>
> If I start the SQL Agent GUI and click on the database in
> question, click on "restore" then on "refresh" to see the
> backup of the database, it is not there.
>
> If I sign on my mvs system and display the file spaces I show
> that the file space was created.
>
> If I manually backup the database it works fine.
>
> One short term fix was to delete the sql node and give the
> server another node name. This worked fine for the first
> scheduled backup then the original problem returned
> but this time with another database.
> Any idea what I should do next ?
>
> Thanks,
> Steve Norton
> srnorton AT bhset DOT org