Thanks for looking at this Tilo.
More comments inline:
On 12/23/05, Heinrich, Tilo <[EMAIL PROTECTED]> wrote:
>
>
> Can not open file 'E:\sapdb\BOO\db\backups\io\backint.output'.
> (System error 32; The process cannot access the file because it is being
> used by another process.)
This was due
To: Heinrich, Tilo
Cc: maxdb@lists.mysql.com
Subject: Re: MaxDB backups
I've attached dbm.ebl
Jared
On 12/22/05, Heinrich, Tilo <[EMAIL PROTECTED]> wrote:
Hallo Jared,
>When the MaxDB backup fails, it does not cleanup its log files.
D
lto:[EMAIL PROTECTED]
Sent: Wednesday, December 21, 2005 9:10 PM
To: Heinrich, Tilo
Cc: maxdb@lists.mysql.com
Subject: Re: MaxDB backups
Hi Tilo,
Comments inline:
After the backup got canceled, there should be more information
within dbm.ebp, then just the "Waiting... is
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 a
ch
SAP Labs Berlin
From: Jared Still [mailto:[EMAIL PROTECTED] ]
Sent: Tuesday, December 20, 2005 7:58 PM
To: Heinrich, Tilo
Cc: maxdb@lists.mysql.com
Subject: Re: MaxDB backups
Thank you for the reply Tilo.
L PROTECTED]
> Sent: Tuesday, December 20, 2005 7:58 PM
> To: Heinrich, Tilo
> Cc: maxdb@lists.mysql.com
> Subject: Re: MaxDB backups
>
>
> Thank you for the reply Tilo.
>
> Yes, it is being killed.
>
> I changed the timeout to 30 seconds so it wouldn't take
>
PM
To: Heinrich, Tilo
Cc: maxdb@lists.mysql.com
Subject: Re: MaxDB backups
Thank you for the reply Tilo.
Yes, it is being killed.
I changed the timeout to 30 seconds so it wouldn't take
so long for the job to fail. It was taking several minutes
prevoiusly with the same results, which i
Thank you for the reply Tilo.
Yes, it is being killed.
I changed the timeout to 30 seconds so it wouldn't take
so long for the job to fail. It was taking several minutes
prevoiusly with the same results, which is why I set the
timeout value.
The job was working previously on our test NBU server
Hello Jared,
Please have a look into one of the files dbm.ebp and dbm.ebl. Most
probably you will find, that your Backint got killed by the DBM Server
after a certain timeout elapsed. If so, change the timeout with the help
of parameter "TIMEOUT_SUCCESS" in the configuration file for Backint for
M
