Hi Tilo,
Comments inline:
> After the backup got canceled, there should be more information within
> dbm.ebp, then just the "Waiting... is running"-blocks you presented.
>
> Could you please explain further on the usefulness of dbm.ebp and the
> number of backups attempts?
>
NetBackup makes 3 attempts to run a job. If the 1st one fails, it tries
again. If that one also fails, it will try a 3rd time.
After the 3rd failure, NetBackup gives up and returns an error.
When the MaxDB backup fails, it does not cleanup its log files.
When the next attempt to run the job sees that those log files still exists,
it throws an error.
Since this second attempt to run has overwritten dbm.ebp, the log of the
initial failed backup job is lost.
Here is an example from dbm.epl:
Error thrown by 2nd backup attempt:
Have encountered error -24927:
The file 'E:\sapdb\BOO\db\backups\io\backint.output' already exists.
The real error appeared in the previous backup attempt as recorded in
dbm.epl.
The number of retries is probably configurable. I haven't checked yet, but
it would be useful to
set this to 1 for troubleshooting purposes.
Within dbm.prt only the issued DBM Server commands are accumulated not any
> logs. Did you mean dbm.ebl?
>
Yes, I did mean dbm.ebl.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
