Thanks for your answer, Martin!
Here's an example of what I get in the logs (of course, I changed the
machine names):
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: Start Backup
JobId 12159, Job=Backup-MyBaculaCLient.2013-01-30_04.35.00_32
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: Using Device
"MyBaculaCLient-Device"
30-Jan 04:35 MyBacula-SD.private.domain.com JobId 12159: Volume
"MyBaculaCLient-Inc-0064" previously written, moving to end of data.
30-Jan 04:35 MyBacula-SD.private.domain.com JobId 12159: Error: Bacula
cannot write on disk Volume "MyBaculaCLient-Inc-0064" because: The sizes
do not match! Volume=229213150 Catalog=107132479
30-Jan 04:35 MyBacula-SD.private.domain.com 12159: Marking Volume
"MyBaculaCLient-Inc-0064" in Error in Catalog.
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: There are no
more Jobs associated with Volume "MyBaculaCLient-Inc-0357". Marking it
purged.
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: All records
pruned from Volume "MyBaculaCLient-Inc-0357"; marking it "Purged"
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: Recycled volume
"MyBaculaCLient-Inc-0357"
30-Jan 04:35 MyBacula-SD.private.domain.com JobId 12159: Recycled volume
"MyBaculaCLient-Inc-0357" on device "MyBaculaCLient-Device"
(/data/mybaculaclient), all previous data lost.
MyBacula-SD.private.domain.com bombarde-fd JobId 12159: /tmp is a
different filesystem. Will not descend from / into /tmp
30-Jan 04:35 JobId 12159: Job write elapsed time = 00:00:39, Transfer
rate = 772.6 K Bytes/second
30-Jan 04:35 MyBaculaDIr.private.domain.com JobId 12159: Bacula
MyBaculaDIr.private.domain.com 5.0.2 (28Apr10): 30-Jan-2013 04:35:42
Build OS: i486-pc-linux-gnu debian 6.0.3
JobId: 12159
Job: Backup-MyBaculaCLient.2013-01-30_04.35.00_32
Backup Level: Incremental, since=2013-01-29 04:35:02
Client: "mybaculaclient-fd" 2.4.4 (28Dec08)
i486-pc-linux-gnu,debian,5.0
FileSet: "MyBaculaCLient-Fileset" 2012-06-15 04:35:00
Pool: "MyBaculaCLient-Inc-Pool" (From Job IncPool
override)
Catalog: "MainCatalog" (From Client resource)
Storage: "MyBaculaCLient-Storage" (From Job resource)
Scheduled time: 30-Jan-2013 04:35:00
Start time: 30-Jan-2013 04:35:02
End time: 30-Jan-2013 04:35:42
Elapsed time: 40 secs
Priority: 10
FD Files Written: 1,737
SD Files Written: 1,737
FD Bytes Written: 29,892,114 (29.89 MB)
SD Bytes Written: 30,133,218 (30.13 MB)
Rate: 747.3 KB/s
Software Compression: 64.4 %
VSS: no
Encryption: no
Accurate: no
Volume name(s): MyBaculaCLient-Inc-0357
Volume Session Id: 83
Volume Session Time: 1359391908
Last Volume Bytes: 30,221,121 (30.22 MB)
Non-fatal FD errors: 0
SD Errors: 1
FD termination status: OK
SD termination status: OK
Termination: Backup OK -- with warnings
There's no explanation of what's going on actually, at least none I can
identify. It just says that the "size does not match". But the backup is
ok with another volume (another file on the same disk). The problem is
that next time bacula will try and use the volume marked in Error, it
will fail and the job will fail too...
I've checked the disk on the SD, as it could be obviously a problem of
that kind, but couldn't find anything...
If you've got further ideas on how to debug this, they will be most welcome!
Thanks!
Le 30/01/2013 19:59, Martin Simmons a écrit :
>>>>>> On Wed, 30 Jan 2013 11:28:11 +0100, Jean-François Leroux said:
>> Hi,
>> It's been a few weeks (2-3) that I have more and more volumes marked in
>> error. I haven't had this problem before.
>> I'm doing backups on disk on a remote machine. So all my volumes are
>> files really. I've checked the disks, of course (e2fsck), which are fine.
>>
>> The volumes go into error mode after this message : /The sizes do not
>> match! Volume=229213150 Catalog=107132479/
>>
>> My question is : how can I repair these volumes, possibly without
>> loosing data? I know I can change the Volume status, but next time it is
>> used, it goes back to Error.
>>
>> So what's the correct way to repair the database ? I've run dbcheck
>> already, and mysql tools. The DB seems OK otherwise.
> Before fixing them, I suggest you find out what caused the mismatch. Look in
> the bacula log to see what happened when the volumes were used (e.g. maybe a
> job failed due to network errors).
>
> The safest and simplest way to repair them is to use the purge command, but
> that will lose data (it deletes any jobs on them).
>
> You could also adjust the media.volbytes field to match the file size using
> sql commands, but you need to do that carefully to avoid wrecking the catalog.
>
> __Martin
>
> ------------------------------------------------------------------------------
> 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
|
