Thanks for your help. I had not configured an auto changer hence my problem. I
will try this out now. Again thanks for pointing me in the right direction.
David Waller
david.wall...@blueyonder.co.uk
> On 4 Sep 2024, at 19:01, Bill Arlofski via Bacula-users
> <bacula-users@lists.sourceforge.net> wrote:
>
> On 9/4/24 11:27 AM, David Waller via Bacula-users wrote:
>> Sorry forgot to add:
>> I am running version 15.02 on Debian and the two pool definitions are as
>> follows:
>> Pool {
>> Name = "Air-Full"
>> PoolType = "Backup"
>> LabelFormat = "Air-"
>> ActionOnPurge = "Truncate"
>> MaximumVolumeJobs = 1
>> VolumeRetention = 31536000
>> NextPool = "Virtual-Air"
>> Storage = "FreeNAS1"
>> AutoPrune = yes
>> Recycle = yes
>> }
>> And
>> Pool {
>> Name = "Virtual-Air"
>> PoolType = "Backup"
>> LabelFormat = "Virtual-"
>> VolumeRetention = 31536000
>> Storage = "FreeNAS1"
>> }
>> My understanding is that the job creates the full and incremental backup
>> volumes in the Pool, Air-Full, by running the job with a level of full. I
>> can then run the job with a level of VirtualFull and bacula will copy the
>> full and the various incremental volumes to the pool Virtual-Air and
>> consolidate into one volume. The various volumes are created in the pool
>> Air-Full as expected, the failure happens when I run with a level of
>> VirtualFull.
>> Both pools are on the same storage, I have not tested yet if that is the
>> issue. If it is, and I have to have the two pools on separate storage, what
>> happens with the media type as my understanding is to use separate media
>> type if you have different storage devices in which case would bacula get
>> confused on a restore?
>
> Hello David,
>
> ----8<----
> Status “is waiting on max Storage jobs.”
> ----8<----
>
> This means what it says. Somewhere in the "pipeline" (in this case on the
> Storage) you have reached the limit on the number of concurrent jobs that can
> run on the defined storage.
>
> When you run a VirtualFull using the same storage (perfectly fine to do so),
> it needs a device to read and a device to write, which counts as two jobs to
> the Storage.
>
>
> What is your `MaximumConcurrentJobs` settings for the following:
>
> - Director Storage resource: `FreeNAS1`
> - The Storage Daemon itself (this is the top level limit of the number of
> jobs the SD can run concurrently)
> - The Device(s) in the SD. If you only have one device, the
> MaximumConcurrentJobs will not matter because a device can only read or write
> during a job, not both.
>
> Can you post your configurations for:
>
> - The Director storage resource `FreeNAS1`
> - The SD's Autochanger and devices
>
> If your Director's storage resource `FreeNAS1` points to a single device on
> the SD, then you need to instead create an Autochanger on the SD with some
> number of devices and point the Director's Storage resource `FreeNAS1` at
> that Autochanger.
>
> I usually start with 10 devices plus a couple more "ReadOnly" devices so
> there should always be a device available for reading during critical
> restores.
>
>
> Best regards,
> Bill
>
> --
> Bill Arlofski
> w...@protonmail.com <mailto:w...@protonmail.com>
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net <mailto:Bacula-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
