I am finding that a job is sometimes stalled as no suitable disk volume is
available. Auto create of a new volume is not occurring. When I label a new
volume manually the job proceeds as normal.
When I look at the volume list for the pool, there are indeed no recycle
candidates. I expected that a new volume would be created if the Maximum
Volumes limit specified has not been exceeded.
I thought that the pool def below would do that but I am obviously missing
something.
There are 10 volumes in the pool presently with status "used" or "full" and
all unexpired.
Pool {
Name = file_archive
Pool Type = Backup
Volume Retention = 1 month
Recycle = yes
AutoPrune = yes
LabelFormat = archive
Maximum Volume Bytes = 10G
Maximum Volumes = 20
Action On Purge = Truncate
Volume Use Duration = 14 hours
}
This pool def is one of several similar ones. They all exhibit this
behaviour from time to time.
Regards
Chris Wilkinson
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
