Bacula-users

Re: [Bacula-users] Volumes in Error

2013-01-31 14:52:13
Subject: Re: [Bacula-users] Volumes in Error
From: "Novosielski, Ryan" <novosirj AT umdnj DOT edu>
To: "'waa-bacula AT revpol DOT com'" <waa-bacula AT revpol DOT com>, "'bacula-users AT lists.sourceforge DOT net'" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 31 Jan 2013 14:49:06 -0500
I would definitely check the more common and more likely circumstance first, 
where the previous backup on the volume does complete in error. It is certainly 
possible that there will be no error, but one should eliminate that probable 
log entry first -- if the last volume use does complete without error, I'd 
agree, but I've not seen it yet. 



----- Original Message -----
From: Bill Arlofski [mailto:waa-bacula AT revpol DOT com]
Sent: Thursday, January 31, 2013 01:34 PM
To: bacula-users AT lists.sourceforge DOT net <bacula-users AT 
lists.sourceforge DOT net>
Subject: Re: [Bacula-users] Volumes in Error

On 01/31/13 10:09, Martin Simmons wrote:
>>>>>> On Thu, 31 Jan 2013 11:27:07 +0100, Jean-François Leroux said:
>>
>> The previous entry for this backup shows this:
>>
>> 29-Jan 04:35 unisson.private.tice.ac-orlea JobId 12110: Start Backup 
>> JobId 12110, Job=Backup-MyClient.2013-01-29_04.35.00_41
>> 29-Jan 04:35 MyBaculaDir.MyDomain.com JobId 12110: Using Device 
>> "MyClient-Device"
>> 29-Jan 04:35 MyBaculaSD.MyDomain.com JobId 12110: Volume 
>> "MyClient-Inc-0205" previously written, moving to end of data.
>> 29-Jan 04:35 MyBaculaSD.MyDomain.com JobId 12110: Ready to append to end 
>> of Volume "MyClient-Inc-0205" size=228201991
>> 29-Jan 04:35 MyBaculaDir.MyDomain.com JobId 12110: Max Volume jobs 
>> exceeded. Marking Volume "MyCLient-Inc-0205" as Used.
> 
> Can you find the log from the previous use of the volume
> MyBaculaCLient-Inc-0064, which is the one that got the error in your previous
> post?
> 
> __Martin

Hi Martin, Hi Ryan,

I suspect he will see what I was seeing.

Namely, the previous job that used the volume would complete OK (no errors, no
warnings) and everything looked perfectly fine.

But behind the scenes due to memory problems, SD threads were crashing and I
didn't know it, and then the next job to use the volume would report it as
having a size mismatch, and/or mark it in error.  Heck, even when I did
noticed the SD threads crashing, it still made no sense because the jobs were
completing OK and there were no errors or complaints from Bacula.

Because of the multitude of non-related issues all occurring at the same time,
it was a real pita to figure out the whole problem  but in the end the causes
were pretty simple and I am glad it is back to normal again. :)

Hope Jean-François has similar results. :)

--
Bill Arlofski
Reverse Polarity, LLC


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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