Not the last run for this backup job, the last job that used this VOLUME. There 
is no way for a volume to be marked in error without logging. Look for the 
error. 



----- Original Message -----
From: Jean-François Leroux [mailto:leroux.jeanfrancois AT gmail DOT com]
Sent: Thursday, January 31, 2013 05:27 AM
To: bacula-users AT lists.sourceforge DOT net <bacula-users AT 
lists.sourceforge DOT net>
Subject: Re: [Bacula-users] Volumes in Error

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.

Here's my client Pool  configuration:

# Pool for Full MyClient-Storage
#One full per month
Pool {
   Name = MyClient-Full-Pool
   Use Volume Once = yes
   Pool Type =  Backup
   LabelFormat = "MyClient-Full-"
   AutoPrune = yes
   VolumeRetention = 2 months
   Maximum Volumes = 3
   Recycle = yes
}

# Pool for Differential MyClient-Storage
# One diff per week
Pool {
   Name = MyClient-Diff-Pool
   Use Volume Once = yes
   Pool Type =  Backup
   LabelFormat = "MyClient-Diff-"
   AutoPrune = yes
   VolumeRetention = 62 days
   Maximum Volumes = 10
   Recycle = yes
}

# Pool for Incremental MyClient-Storage
#One inc Monday-Saturday
Pool {
   Name = MyClient-Inc-Pool
   #Use Volume Once = yes
   Maximum Volume Jobs = 6
   Pool Type =  Backup
   LabelFormat = "MyClient-Inc-"
   AutoPrune = yes
   VolumeRetention = 62 days
   Maximum Volumes = 10
   Recycle = yes
}

So the volume previously marked as 'Used'  in the message above should 
be recycled. It looks like the recycling doesn't work properly in some 
cases because of this 'sizes mismatch' message. So, when all volumes are 
used or marked in Error, the jobs finally fails.

PS : I've got 20 volumes in Error tonight! It seems it is increasing at 
a very fast pace.

JFL

Le 31/01/2013 04:44, Joseph L. Casale a écrit :
>> Here's an example of what I get in the logs (of course, I changed the
>> machine names):
>
> That looks more like the log that encounters the error, not the log from 
> which time
> the error was produced. What does the log look like for the last job that 
> wrote to
> that volume?
> ------------------------------------------------------------------------------
> 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


------------------------------------------------------------------------------
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