On Wednesday 09 July 2008 23:50:24 Mingus Dew wrote:
> All,
> I have been running Bacula in production for over a year now, and have
> upgraded through 3 versions to
2.4.0. All this time I've had an issue
> managing disk Volumes. I have posted many times before asking for
> assistance with this issue. The first issue I encountered was using the
> "Max Volume Duration" setting to have each Volume only be used for 7 days,
> then marked as Used. However, I would run into this issue
>
> The job starts:
> 03-Mar 20:00 back4.director JobId 1951: Start Backup JobId 1951,
> Job=www1.client_Daily_Disk.2008-03-03_20.00.12
> 03-Mar 20:00 back4.director JobId 1951: Using Device "My_ZFS_Storage"
>
> The troubles start:
> 03-Mar 20:00 back4.director JobId 1951: Max configured use duration
> exceeded. Marking Volume "My_Disks-3" as Used.
> 03-Mar 20:00 back4.director JobId 1951: There are no more Jobs associated
> with Volume "My_Disks-4". Marking it purged.
> 03-Mar 20:00 back4.director JobId 1951: All records pruned from Volume
> "My_Disks-4"; marking it "Purged"
> 03-Mar 20:00 back4.director JobId 1951: Recycled volume "My_Disks-4"
> 03-Mar 20:00 back4.storage JobId 1951: Fatal error: acquire.c:366 Wanted to
> append to Volume "My_Disks-4", but device "My_ZFS_Storage"
> (/mnt/backup1/mydisks/bacula) is busy writing on "My_Disks-3" .
> 03-Mar 20:00 www1.client JobId 1951: Fatal error: ../../filed/job.c:1811
> Bad response to Append Data command. Wanted 3000 OK data
> , got 3903 Error append data
>
> And this continues for any other jobs with this schedule:
>
> 03-Mar 20:01 back4.storage JobId 1950: Fatal error: acquire.c:366 Wanted to
> append to Volume "My_Disks-4", but device "My_ZFS_Storage"
> (/mnt/backup1/mydisks/bacula) is busy writing on "My_Disks-3" .
> 03-Mar 20:01 www2.mentora JobId 1950: Fatal error: ../../filed/job.c:1811
> Bad response to Append Data command. Wanted 3000 OK data
> , got 3903 Error append data
>
> Basically the Volume expires in the middle of job runs, and subsequent jobs
> fail. I HAVE NOT BEEN ABLE TO SOLVE THIS ISSUE AT ALL and I've gotten no
> help either. Its kind of frustrating, but I've kept plugging away.
>
> To keep this from happening, I removed the "Max Volume Duration" setting
> and updated my Volumes. This has stopped the previous issue, but not really
> been a satisfactory solution as now my disk volumes do not overwrite, they
> only continually Append. This means that while the jobs are pruned from the
> database according to the Retention period I've set, the Volume size never
> decreases and the volume is never overwritten.
>
> This caused almost catastophic failure recently when the disk volumes grew
> beyond the size available on disk. I had to purge and delete them, because
> they can't be readily truncated. This caused a loss of 30 days worth of
> backups that are now not recoverable.
>
> I'm at my wits end here and don't know how to address these issues. I only
> hope that there are members in this community who can help me with this
> problem.
>
> Thank you,
> Shon