Hi! I have the following pools:
*list pools +--------+---------+---------+---------+----------+-------------+ | poolid | name | numvols | maxvols | pooltype | labelformat | +--------+---------+---------+---------+----------+-------------+ | 1 | Default | 0 | 0 | Backup | * | | 2 | lib1 | 1 | 0 | Backup | * | | 3 | dp | 348 | 555 | Backup | Vol | | 4 | Scratch | 0 | 0 | Backup | * | +--------+---------+---------+---------+----------+-------------+ dp is the diskpool, containing 32GiB-Volumes. It is configured as follows: Pool { Name = dp Pool Type = Backup Recycle = yes Recycle Pool = dp Recycle Oldest Volume = yes AutoPrune = yes Volume Retention = 365 Days Storage = dp1 Next Pool = lib1 LabelFormat = "Vol" Maximum Volume Bytes = 32G Maximum Volumes = 555 # 17.76TB } Now the problem is that many of the scheduled jobs are often "... is waiting on Storage dp1", and status sd=dp1 says: Jobs waiting to reserve a drive: 3602 JobId=290 device "dp1" (/var/bacula/diskpool/fs1) is busy (already reading/writing). 3608 JobId=309 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=308 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=310 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=249 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=311 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=267 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=269 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). 3608 JobId=312 wants Pool="dp" but have Pool="" nreserve=0 on drive "dp1" (/var/bacula/diskpool/fs1). Device "dp1" (/var/bacula/diskpool/fs1) is mounted with: Volume: Vol0349 Pool: *unknown* Media type: File Total Bytes=11,726,668,867 Blocks=181,775 Bytes/block=64,512 Positioned at File=2 Block=3,136,734,274 So, he seems to be unhappy that the sd has a Volume from an *unknown* pool, whereas the jobs require a volume from the "dp" pool. "list media pool=dp" verifies that Vol0349 actually belongs to the "dp" pool. What's interesting is that when I manually start all my backup-jobs while no other job is running, all of them get going. Only the scheduled jobs suffer from this. Kind regards, -- Lukas ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users