Please mount append Volume or label a new one

[Eric Browning]

All,

"Please mount append Volume "Groups-Daily-20200416-2032" or label a new one"

I have beat my head against the wall with this issue for months now.  Why is bareos asking for another volume only half way through the month like it has run out?  I have retention times set to about twice as long as I need them with auto purge on.  It's all disk based and there is basically no limit to the number of volumes that it could create/need in a month.

Where is a good starting point for this issue?

--

Eric

[Brock Palen]

Bareos will be very aggressive about not reusing a volume unless it has to. The retention times remove entries form the database and make volumes eligible to be recycled, but if you allow auto labeling and do nothing to limit the number of volumes you have it will keep labeling until it uses up disk space.

As for your case can you send your config to the list for your storages and your pools?

That message says it wants to mount that volume and says it’s append-able (list volume pool=<pool name> and check the status, it should say append.

My guess is your pool or storage config ether limits the number of volumes you can mount or it thinks that these are manually mounted (like tapes or USB drives).

If you send the config for those to the list probably help more.


Brock Palen
1 (989) 277-6075
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting

> --
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/CAM%3D5oeCmn5pfUEpT4i6Ls%2BvsPq88LmjRoZ8bAzzzFAed_fwZjg%40mail.gmail.com.

[Eric Browning]

Thanks Brock.  Yes I was going to send the configs but was looking to narrow it down before blanketing the list with config files.

Pools config.  The goal because this is all disk based is one backup job per file on a direct attached raid.  The archive pool is a removable USB3 hard drive.  No single job has taken over 19 hours according to backup logs.

Pool {
  Name = Monthly
  Pool Type = Backup
  AutoPrune = yes
  VolumeRetention = 2 months
  Maximum Volume Bytes = 0
  Maximum Volume Jobs = 1
  Maximum Volumes = 0
  Recycle = yes
  Label Format = "${Client}-${Pool}-${Year}${Month:p/2/0/r}${Day:p/2/0/r}-${Hour:p/2/0/r}${Minute:p/2/0/r}"
  Next Pool = Archive
  Volume Use Duration = 19h
}
Pool {
  Name = Weekly
  Pool Type = Backup
  AutoPrune = yes
  VolumeRetention = 60 days
  Maximum Volume Bytes = 0
  Maximum Volume Jobs = 1
  Maximum Volumes = 0
  Recycle = yes
  Label Format = "${Client}-${Pool}-${Year}${Month:p/2/0/r}${Day:p/2/0/r}-${Hour:p/2/0/r}${Minute:p/2/0/r}"
  Next Pool = Archive
  Volume Use Duration = 19h
}

Pool {
  Name = Daily
  Pool Type = Backup
  AutoPrune = yes
  VolumeRetention = 40 days
  Maximum Volume Bytes = 0
  Maximum Volume Jobs = 1
  Maximum Volumes = 0
  Recycle = yes
  Label Format = "${Client}-${Pool}-${Year}${Month:p/2/0/r}${Day:p/2/0/r}-${Hour:p/2/0/r}${Minute:p/2/0/r}"
  Next Pool = Archive
  Volume Use Duration = 19h
}
Pool {
  Name = Archive
  Pool Type = Backup
  AutoPrune = no
  VolumeRetention = 6 months
  Maximum Volume Bytes = 0
  Maximum Volume Jobs = 1
  Maximum Volumes = 0
  Recycle = yes
  Label Format = "${Client}-${Pool}-${Year}${Month:p/2/0/r}${Day:p/2/0/r}-${Hour:p/2/0/r}${Minute:p/2/0/r}"
  Storage = ArchiveDrive

Storage config below is duplicated a number of times for concurrent backups, they're all the same as the one below.  

I have removed the IP and password.

Storage {
  Name = File
  Address = x.x.x.x
  Password = ""
  Device = FileStorage
  Media Type = File
  Maximum Concurrent Jobs = 1
}

--

Eric Browning
Systems Administrator
801-984-7623

Skaggs Catholic Center
Juan Diego Catholic High School
Saint John the Baptist Middle
Saint John the Baptist Elementary

Twitter: @SCCMrB

[Brock Palen]

I’m not a bareos expert so what I put here is speculative based on my own experience.

First for your Strorage {} config on your director, only have one entry but with multiple devices defined on your SD. eg here is what I have:

Storage {
Name = File
# Do not use "localhost" here
Address = <removed> # N.B. Use a fully qualified name here
#LanAddress = <removed>
Password = “<removed>"
Device = FileStorage
Device = FileStorage2
Device = FileStorage3
Device = FileStorage4
Device = FileStorage5
# number of devices = Maximum Concurrent Jobs
Maximum Concurrent Jobs = 5
Media Type = File
Heartbeat Interval = 60
}


Then for my pools I have:

Pool {
Name = catalog
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 1 week
Volume Use Duration = 1 day
Storage = File
Label Format = "catalog-"
Next Pool = Offsite # copy jobs write to this pool
Action On Purge=Truncate
}



I use the catalog pool because I only use catalog volumes once a day as I push them to a cloud provider for DR purposes to rebuild the catalog and all my tape keys.

What I am expecting is that the Storage {} entries you have your your pools pointing to (some don’t appear to have one I would make sure they have one) that when it goes to mount the volume there isn’t a storage device available in the mind of bareos.

If switching to a single director Storage {} entry with multiple SD storage devices pointing to the same directory, and adding Stroage = File to all your pool entries doesn’t work,

Send of a running job that’s blocked on asking for a volume

list joblog jobid=######
status storage=File

> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/CAM%3D5oeBb-yh7_xMk95RwEp5Z1jHrA6mh3_Aauh1HWCGZvuRBXg%40mail.gmail.com.