Hi,

I'm a bit confused on whats happening here. Our current setup is backing
up to a mounted storage partition. It's got like 2TB of space there
which is more than enough for out needs.

I have setup my pools and backups setup as such.....

Schedule {
  Name = "BackupCycle"
  Run = Level=Full Pool=Full-Pool 1st mon at 1:05
  Run = Level=Differential Pool=Diff-Pool mon at 1:05
  Run = Level=Incremental Pool=Inc-Pool mon-sun at 1:05
}


Pool {
  Name = Full-Pool
  Pool Type = Backup
  Recycle = yes           # automatically recycle Volumes
  AutoPrune = yes         # Prune expired volumes
  Volume Retention = 3 months
  Maximum Volume Jobs = 1
  Label Format =
"Monthly-Full-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${Hour:p/2/0/r}-${Minute:p/2/0/r}"
  Maximum Volumes = 12
}
Pool {
  Name = Inc-Pool
  Pool Type = Backup
  Recycle = yes           # automatically recycle Volumes
  AutoPrune = yes         # Prune expired volumes
  Volume Retention = 1 month
  Maximum Volume Jobs = 1
  Label Format =
"Weekly-Inc-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${Hour:p/2/0/r}-${Minute:p/2/0/r}"
  Maximum Volumes = 63
}
Pool {
  Name = Diff-Pool
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 14 days
  Maximum Volume Jobs = 1
  Label Format =
"Daily-Diff-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${Hour:p/2/0/r}-${Minute:p/2/0/r}"
  Maximum Volumes = 12
}

The Idea is that we have a monthly full, a weekly diff, and daily incs.

So far things are working out well, it's only been about 2 weeks. But I
keep getting this email.

18-Feb 01:05 serv01-sd JobId 33: Job serv02.2009-02-18_01.05.00.06 waiting. 
Cannot find any appendable volumes.
Please use the "label"  command to create a new Volume for:
    Storage:      "FileStorage" (/mnt/storage)
    Pool:         Inc-Pool
    Media type:   File

But all the backup jobs complete, with no errors. Looking at the storage
directory, all my files are there, though they have a bit funky of
permissions that I don't understand yet.

-rwxrwSrwt 1 root root 9.4M Feb 16 01:05 Weekly-Inc-2009-02-16-01-05
-rwxrwSrwt 1 root root 7.0G Feb 16 03:05 Weekly-Inc-2009-02-16-02-05
-rwxrwSrwt 1 root root  20K Feb 16 03:51 Weekly-Inc-2009-02-16-03-51
-rwxrwSrwt 1 root root  11M Feb 17 01:05 Weekly-Inc-2009-02-17-01-05
-rwxrwSrwt 1 root root 6.7G Feb 17 03:04 Weekly-Inc-2009-02-17-02-05
-rwxrwSrwt 1 root root  20K Feb 17 03:05 Weekly-Inc-2009-02-17-03-05
-rwxrwSrwt 1 root root 8.4M Feb 18 01:05 Weekly-Inc-2009-02-18-01-05
-rw-r----- 1 root root 7.2G Feb 18 03:11 Weekly-Inc-2009-02-18-02-05
-rw-r----- 1 root root  92K Feb 18 03:11 Weekly-Inc-2009-02-18-03-11

This is how they look every morning when I check on them. We are only
backing up 2 external hosts, and the local host.

My real question is, why am I getting intervention emails, but bacula
goes ahead and mounts / writes the right backup anyways?

Thanks,

Charlie


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users