Additional info: Bacula 2.2.6 on Debian 4.0, /mnt/bacula is mounted using
smbfs on a W2K3 NAS gateway.
--- Foo Bar <[EMAIL PROTECTED]> wrote:
> Hi,
>
> after changing the pool settings for a volume (from 365days retention to
> 2,
> lowering the number of bytes to 1 GB max etc.) and doing an 'update
> volume', the output of 'llist volume' shows MaxVolBytes: 1 where it was
> MaxVolBytes: 0 before.
I found this is due to using commas in the Pool definition, which I changed
now:
Pool {
Name = Pool_foo_full
Pool Type = Backup
Volume Use Duration = 7d
## this results in MaxVolBytes 1 instead of 1 GiB:
## Maximum Volume Bytes = 1,073,741,824
Maximum Volume Bytes = 1073741824
Maximum Volume Jobs = 8
Volume Retention = 2 days
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Recycle = yes
AutoPrune = yes
}
However, before changing it this morning (and doing update volume) the job
ran last night and the following happened:
21-Nov 01:45 foo-dir JobId 499: No prior Full backup Job record found.
21-Nov 01:45 foo-dir JobId 499: No prior or suitable Full backup found in
catalog. Doing FULL backup.
21-Nov 01:45 foo-dir JobId 496: Start Backup JobId 496,
Job=foo_fulltest.2007-11-21_01.45.06
21-Nov 01:45 foo-dir JobId 496: Max Volume bytes exceeded. Marking Volume
"Vol_foo_full" as Full.
21-Nov 01:45 foo-dir JobId 496: Purging oldest volume "Vol_foo_full"
21-Nov 01:45 foo-dir JobId 496: 2 Files on Volume "Vol_foo_full" purged
from catalog.
21-Nov 01:45 foo-dir JobId 496: There are no more Jobs associated with
Volume "Vol_foo_full". Marking it purged.
21-Nov 01:45 foo-dir JobId 496: All records pruned from Volume
"Vol_foo_full"; marking it "Purged"
21-Nov 01:45 foo-dir JobId 496: Using Device "NAS_mount"
21-Nov 01:45 foo-sd JobId 496: User defined maximum volume capacity 1
exceeded on device "NAS_mount" (/mnt/bacula).
21-Nov 01:45 foo-sd JobId 496: Error: label.c:485 Unable to write device
"NAS_mount" (/mnt/bacula): ERR=
21-Nov 01:45 foo-sd JobId 496: Marking Volume "Vol_foo_full" in Error in
Catalog.
21-Nov 01:45 foo-sd JobId 496: Job foo_fulltest.2007-11-21_01.45.06
waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "NAS_mount" (/mnt/bacula)
Pool: Pool_foo_full
Media type: NAS_File
The last bit is repeated after 1, 2 and 4 hours.
I had a single Vol_foo_full volume which was 11 GB (lots of
full/incremental backups before changing max size/duration/retention
settings) which changed to 0 bytes during the above.
I will of course label at least one new volume, but out of curiosity, when,
if ever, will the single volume I have now be recycled and reused? Was it
blocked because of the 1 byte limit I set yesterday and should it work
during the backup tonight? (or after 16 hours, whichever comes first)
Couple more questions:
- why does the job output say 2 files were deleted from the catalog when
there were many thousands of files (in dozens of jobs) in the volume (and
catalog) already?
- how do I change the Volume's 'Error' status to 'Append' again? (will a
manual cancel job do it for example?)
- how do I make sure such an error does not block any other backups without
resorting to parallel backups and/or autolabeling?
- if this job runs OK tonight the other jobs that are waiting behind it
(scheduled to be run at the same time once a day) will presumably run, but
will they run again immediately due to the schedule? Or if they take a few
minutes, will passing the scheduled time mean they are not executed?
___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
