Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

Thanks Bill,  see below...

> On 19. Apr 2023, at 22:05, Bill Arlofski  wrote:
> 
> I just checked and I see that my memory was working correctly this morning...
> 
>>> I will ask my colleagues if they remember this issue in the Enterprise 
>>> version and if it was address/modified/fixed.
>>> 
>>> Be right back. :)
>> 
>> OK waiting :)
> 
> There was a ticket/bug where a customer had reported this same issue where 
> the truncate command always used the first Drive
> device in the disk Autochanger, but this has since been addressed.

In what version of Bacula has it been fixed? It is still a problem in 11.0.6. 
At least truncate doesn’t choose an unoccupied drive, you have to explicitly 
choose one manually.

> In bconsole, just type `truncate` and hit tab a few times to see what the 
> options are:
> 
> *truncate
> allpoolsdrive=  mediatype=  pool=   storage=volume=
> 
> 
> Notice `drive=xxx` can be specified.  I think you will need to specify 
> `DriveIndex=` (starting at 0) for each drive
> device in the Autochanger too. If not for this reason, I am 100% sure there 
> is another reason I had come across and had to
> prove to my colleagues several years back. :)

yes, with this it does work. Thanks for your help!




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Bill Arlofski via Bacula-users]

I just checked and I see that my memory was working correctly this morning...


I will ask my colleagues if they remember this issue in the Enterprise version 
and if it was address/modified/fixed.

Be right back. :)


OK waiting :)


There was a ticket/bug where a customer had reported this same issue where the 
truncate command always used the first Drive
device in the disk Autochanger, but this has since been addressed.


In bconsole, just type `truncate` and hit tab a few times to see what the 
options are:

*truncate
allpoolsdrive=  mediatype=  pool=   storage=volume=


Notice `drive=xxx` can be specified.  I think you will need to specify 
`DriveIndex=` (starting at 0) for each drive
device in the Autochanger too. If not for this reason, I am 100% sure there is 
another reason I had come across and had to
prove to my colleagues several years back. :)


This is with the Community version 13.0.2:

*ver
bacula-dir Version: 13.0.2
(18 February 2023) ...

I also checked the Enterprise 16.0.5 and it is the same.


Hope this helps.
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Truncate Volumes Before Retention Time is Up

[Justin Case]

you could try this:

truncate pool=mypool storage=mystorage

> On 30. Mar 2023, at 18:10, Chris Wilkinson  wrote:
> 
> Do I need to do this for each volume in the pool individually?
> 
> I was hoping to purge and delete all the volumes belonging to the pool as 
> there are quite a large number of volumes.
> 
> I guess I could script the procedure if not.
> 
> Chris.
> 
> On Thu, 30 Mar 2023, 4:59 pm Phil Stracchino,  > wrote:
> On 3/30/23 06:40, Chris Wilkinson wrote:
> > I have an old job that is no longer needed that is consuming some disk 
> > space that I'd like to recover. This storage for this job is on S3 cloud 
> > and the job has full/diff/incr pools associated.
> > 
> > The full backup pool/volumes of this job have a retention time of 365 
> > days so would not normally get pruned out for another year almost. The 
> > incr/diff pool/volumes have a retention time of 7days/31days respectively.
> > 
> > I'd like to truncate these now, delete the job resources and rm the 
> > actual disk volumes, deleting all traces of the defunct job.
> > 
> > What would I need to do to truncate these out now?
> > 
> > I haven't been able to find bconsole commands that would do this. I 
> > tried the truncate command but the volumes status remains unchanged at 
> > full or used or append. Thanks for any suggestions.
> 
> Fundamentally:
> 
> purge jobs volume=...
> delete volume=...
> 
> then rm the file.
> 
> -- 
>Phil Stracchino
>Babylon Communications
>ph...@caerllewys.net 
>p...@co.ordinate.org 
>Landline: +1.603.293.8485
>Mobile:   +1.603.998.6958
> 
> 
> 
> ___
> Bacula-users mailing list
> 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

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

Hi Bill, see below

> On 19. Apr 2023, at 17:22, Bill Arlofski via Bacula-users 
>  wrote:
> 
> On 4/19/23 03:52, Justin Case wrote:
>> For the sake of completeness: I have read in the document “Community Disk 
>> Backup Design” in section 3.1 that it is possible what you are proposing and 
>> how to do it and implemented it, but it is not working the way one would 
>> expect (see my other mail a few minutes ago).
> 
> Hello Justin,
> 
> 
> This message does not indicate to me a problem with a drive being in use, but 
> rather this volume cannot be truncated because it is reserved by a job.
> 
> 8<
> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
> “pool1-vol-0599", because it is reserved by someone else.
> 8<
> 

You need to look a two lines together:

Error truncating Volume “pool1-incr-vol-1109"
3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
“pool2-full-vol-0703", because it is reserved by someone else.

This seems to say that pool1-incr-vol-1109 couldn’t be mounted to be truncated 
because pool2-full-vol-0703 is still mounted, and it cannot be unmounted as it 
is stil used by a backup job.

To me this makes some sense.

> Let me check something too... In other operations (like label), you can 
> specify the disk device to use. I think I recall this not being the case with 
> the truncate command, and that it always uses the first drive in the 
> autochanger.

Well, if this is true, its a problem, as the first drive is busy with the 
backup job.

> I will ask my colleagues if they remember this issue in the Enterprise 
> version and if it was address/modified/fixed.
> 
> Be right back. :)

OK waiting :)

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Bill Arlofski via Bacula-users]

On 4/19/23 03:52, Justin Case wrote:
For the sake of completeness: I have read in the document “Community Disk Backup Design” in section 3.1 that it is possible 
what you are proposing and how to do it and implemented it, but it is not working the way one would expect (see my other mail 
a few minutes ago).


Hello Justin,


This message does not indicate to me a problem with a drive being in use, but rather this volume cannot be truncated because 
it is reserved by a job.


8<
3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume “pool1-vol-0599", 
because it is reserved by someone else.
8<


Let me check something too... In other operations (like label), you can specify the disk device to use. I think I recall this 
not being the case with the truncate command, and that it always uses the first drive in the autochanger.


I will ask my colleagues if they remember this issue in the Enterprise version 
and if it was address/modified/fixed.

Be right back. :)


Best regards,
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Bill Arlofski via Bacula-users]

On 4/19/23 03:07, Justin Case wrote:

Thanks Mat,
that sounds plausible, but is it even possible to have two devices for the same 
folder on disk, which have access to the same
volumes?
So far I believed that was impossible, but I am only a casual user of Bacula.


Hello Justin,

It is absolutely possible, and strongly encouraged to have multiple Devices in 
a disk Autochanger in the SD config. As a
matter of fact, this is the purpose of an Autochanger. It makes no sense to 
have a disk Autochanger with only one device in
it. :)

Each device config should be exactly the same, except for the `Name` and 
`DriveIndex`

Additionally, you can can create some devices with `ReadOnly = yes` and these will be 
"reserved" for Restore/Copy/Migration
Job read devices and will never be used by a Backup job to write data.

You can create as many devices in an Autochanger as you want/need - they are 
free, and more is better. :)

FYI, I never create an Autochanger with less tha
n 10+ devices, each having `MaximumConcurrentJobs = 1`, and several of them
being `ReadOnly = yes`


Hope this helps,
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Nee Help for bacula storage S3 cloud configuration

[Chris Wilkinson]

I have the plugins dir set as /usr/lib which is why I mv'd it there. I
could have set the dir as whatever the default driver make assumes also I
suppose.

-Chris-

On Wed, 19 Apr 2023, 15:47 Bill Arlofski via Bacula-users, <
bacula-users@lists.sourceforge.net> wrote:

> On 4/18/23 12:41, Chris Wilkinson wrote:
> > In my case the driver is installed in /usr/lib/
> bacula-sd-cloud-driver-11.0.6.so 
> >
> > I vaguely recall that the make file didn't put it there and I had to mv
> it. I forget now what the default is.
> >
> > -Chris-
>
> Hello Chris,
>
> In your bacula-sd.conf config, the SD will look for plugins in the
> directory specified by the `PluginDirectory = xxx` line
>
> If it is not specified, then no plugins will be loaded. :)
>
>
> Hope this helps,
> Bill
>
> --
> Bill Arlofski
> w...@protonmail.com
>
> ___
> Bacula-users mailing list
> 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

Re: [Bacula-users] Nee Help for bacula storage S3 cloud configuration

[Bill Arlofski via Bacula-users]

On 4/18/23 12:41, Chris Wilkinson wrote:

In my case the driver is installed in /usr/lib/bacula-sd-cloud-driver-11.0.6.so 


I vaguely recall that the make file didn't put it there and I had to mv it. I 
forget now what the default is.

-Chris-


Hello Chris,

In your bacula-sd.conf config, the SD will look for plugins in the directory 
specified by the `PluginDirectory = xxx` line

If it is not specified, then no plugins will be loaded. :)


Hope this helps,
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

In the meanwhile I also tried to create a separate storage in the director in 
analogy to a restore storage device with AutoSelect=no. This also does not work 
as the volumes I want to truncate are then not found to belong to this storage 
device.

> On 19. Apr 2023, at 11:43, Justin Case  wrote:
> 
> Hi all
> 
> I declared a second device in the disk autochanger, but the same problem 
> occurs when trying to truncate volumes while a backup job is running.
> I also have set MaximumConcurrentJobs to 5, so this shouldn’t be the problem.
> It seems that the second device which I declared in the autochanger is not 
> used for the truncating:
> 
> truncate pool=pool1 storage=storage1
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> Connecting ...
> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
> “pool1-vol-0599", because it is reserved by someone else.
> 
> Error truncating Volume “pool11-vol-0700"
> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
> “pool1-vol-0599", because it is reserved by someone else.
> 
> Error truncating Volume “pool1-vol-0703”
> 
> 
> This is how I declared the second device in the disk autochanger (dev1 and 
> dev2 are declared identical):
> 
> director config file:
> 
> Storage {
>  Name = “storage1"
>  Device = "changer1"
>  MediaType = “file1"
>  MaximumConcurrentJobs = 5
> }
> 
> SD config file:
> 
> Autochanger {
>  Name = “changer1"
>  Device = “restore1"
>  Device = “dev1"
>  Device = “dev2"
>  ChangerDevice = "/dev/null"
>  ChangerCommand = "/dev/null"
> }
> 
> Device {
>  Name = “dev1"
>  MediaType = “file1"
>  DeviceType = "File"
>  ArchiveDevice = "/mnt/folder1"
>  RemovableMedia = no
>  RandomAccess = yes
>  AutomaticMount = yes
>  LabelMedia = yes
>  AlwaysOpen = no
>  Autochanger = yes
>  MaximumConcurrentJobs = 5
> }
> 
> Device {
>  Name = “dev2"
>  MediaType = “file1"
>  DeviceType = "File"
>  ArchiveDevice = "/mnt/folder1"
>  RemovableMedia = no
>  RandomAccess = yes
>  AutomaticMount = yes
>  LabelMedia = yes
>  AlwaysOpen = no
>  Autochanger = yes
>  MaximumConcurrentJobs = 5
> }
> 
>> On 19. Apr 2023, at 11:07, Justin Case  wrote:
>> 
>> Thanks Mat,
>> that sounds plausible, but is it even possible to have two devices for the 
>> same folder on disk, which have access to the same volumes?
>> So far I believed that was impossible, but I am only a casual user of Bacula.
>> 
>>> On 19. Apr 2023, at 08:00, Matlink  wrote:
>>> 
>>> Bacula works with disk volumes similarly as it does with tape volumes. 
>>> Therefore, when truncating, it needs to mount the volume in a free drive to 
>>> write some metadata on it. If you have no available drive, bacula can't 
>>> operate.
>>> To solve this issue you probably need to declare a second drive like the 
>>> first one.
>>> Cheers,
>>> Mat.
>>> 
>>> 
>>> Le 19 avril 2023 00:58:39 GMT+02:00, Justin Case  a 
>>> écrit :
>>> Hello all,
>>> 
>>> while I have running backup jobs the storage is running out of space (disk 
>>> file changer volumes). As the pool (pool2) that is currently written has 
>>> already been truncated (manually some weeks ago), recycling of volumes does 
>>> not create free space.
>>> 
>>> I thus wanted to truncate volumes from a different pool (pool1) while the 
>>> backup is writing to pool2:
>>> truncate pool=pool1-incr storage=storage1
>>> 
>>> I get the following error (for each purged volume in pool1)(showing just 1 
>>> here):
>>> 
>>> Error truncating Volume “pool1-incr-vol-1109"
>>> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
>>> “pool2-full-vol-0703", because it is reserved by someone else.
>>> 
>>> What is the reason that I cannot truncate on storage1 while a backup job is 
>>> running on storage1?
>>> There is only 1 backup job running at a time.
>>> 
>>> The MaximumConcurrentJobs directives are configured as follows:
>>> 
>>> SD config file:
>>> -Storage1 allows 20 concurrent jobs in the SD config file.
>>> -The device allows for 5 concurrent jobs. 
>>> 
>>> Director config file:
>>> -The director allows 20 concurrent jobs.
>>> -Storage1 only allows 1 concurrent job in the director config file. Would 
>>> this have to be configured to the same number as in the SD config file?
>>> -Is the limit of 1 here prohibiting me to truncate while the backup job is 
>>> running?
>>> -The clients allow only 1 concurrent job. 
>>> 
>>> FD config file:
>>> -The FD allows 20 concurrent jobs.
>>> 
>>> In general I want jobs to run sequentially, but truncating should be able 
>>> to happen simultaneously. Is it possible to realize that?
>>> Wich MaximumConcurrentJobs directives would I need to change and how?
>>> 
>>> Thanks for taking the time to consider my question,
>>> J/C
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>> 
> 



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourc

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

For the sake of completeness: I have read in the document “Community Disk 
Backup Design” in section 3.1 that it is possible what you are proposing and 
how to do it and implemented it, but it is not working the way one would expect 
(see my other mail a few minutes ago). 

> On 19. Apr 2023, at 11:07, Justin Case  wrote:
> 
> Thanks Mat,
> that sounds plausible, but is it even possible to have two devices for the 
> same folder on disk, which have access to the same volumes?
> So far I believed that was impossible, but I am only a casual user of Bacula.
> 
>> On 19. Apr 2023, at 08:00, Matlink > > wrote:
>> 
>> Bacula works with disk volumes similarly as it does with tape volumes. 
>> Therefore, when truncating, it needs to mount the volume in a free drive to 
>> write some metadata on it. If you have no available drive, bacula can't 
>> operate.
>> To solve this issue you probably need to declare a second drive like the 
>> first one.
>> Cheers,
>> Mat.
>> 
>> 
>> Le 19 avril 2023 00:58:39 GMT+02:00, Justin Case > > a écrit :
>> Hello all,
>> 
>> while I have running backup jobs the storage is running out of space (disk 
>> file changer volumes). As the pool (pool2) that is currently written has 
>> already been truncated (manually some weeks ago), recycling of volumes does 
>> not create free space.
>> 
>> I thus wanted to truncate volumes from a different pool (pool1) while the 
>> backup is writing to pool2:
>> truncate pool=pool1-incr storage=storage1
>> 
>> I get the following error (for each purged volume in pool1)(showing just 1 
>> here):
>> 
>> Error truncating Volume “pool1-incr-vol-1109"
>> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
>> “pool2-full-vol-0703", because it is reserved by someone else.
>> 
>> What is the reason that I cannot truncate on storage1 while a backup job is 
>> running on storage1?
>> There is only 1 backup job running at a time.
>> 
>> The MaximumConcurrentJobs directives are configured as follows:
>> 
>> SD config file:
>> -Storage1 allows 20 concurrent jobs in the SD config file.
>> -The device allows for 5 concurrent jobs. 
>> 
>> Director config file:
>> -The director allows 20 concurrent jobs.
>> -Storage1 only allows 1 concurrent job in the director config file. Would 
>> this have to be configured to the same number as in the SD config file?
>> -Is the limit of 1 here prohibiting me to truncate while the backup job is 
>> running?
>> -The clients allow only 1 concurrent job. 
>> 
>> FD config file:
>> -The FD allows 20 concurrent jobs.
>> 
>> In general I want jobs to run sequentially, but truncating should be able to 
>> happen simultaneously. Is it possible to realize that?
>> Wich MaximumConcurrentJobs directives would I need to change and how?
>> 
>> Thanks for taking the time to consider my question,
>>  J/C
>> Bacula-users mailing list
>> 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

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

Hi all

I declared a second device in the disk autochanger, but the same problem occurs 
when trying to truncate volumes while a backup job is running.
I also have set MaximumConcurrentJobs to 5, so this shouldn’t be the problem.
It seems that the second device which I declared in the autochanger is not used 
for the truncating:

truncate pool=pool1 storage=storage1
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Connecting ...
3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume “pool1-vol-0599", 
because it is reserved by someone else.

Error truncating Volume “pool11-vol-0700"
3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume “pool1-vol-0599", 
because it is reserved by someone else.

Error truncating Volume “pool1-vol-0703”


This is how I declared the second device in the disk autochanger (dev1 and dev2 
are declared identical):

director config file:

Storage {
  Name = “storage1"
  Device = "changer1"
  MediaType = “file1"
  MaximumConcurrentJobs = 5
}

SD config file:

Autochanger {
  Name = “changer1"
  Device = “restore1"
  Device = “dev1"
  Device = “dev2"
  ChangerDevice = "/dev/null"
  ChangerCommand = "/dev/null"
}

Device {
  Name = “dev1"
  MediaType = “file1"
  DeviceType = "File"
  ArchiveDevice = "/mnt/folder1"
  RemovableMedia = no
  RandomAccess = yes
  AutomaticMount = yes
  LabelMedia = yes
  AlwaysOpen = no
  Autochanger = yes
  MaximumConcurrentJobs = 5
}

Device {
  Name = “dev2"
  MediaType = “file1"
  DeviceType = "File"
  ArchiveDevice = "/mnt/folder1"
  RemovableMedia = no
  RandomAccess = yes
  AutomaticMount = yes
  LabelMedia = yes
  AlwaysOpen = no
  Autochanger = yes
  MaximumConcurrentJobs = 5
}

> On 19. Apr 2023, at 11:07, Justin Case  wrote:
> 
> Thanks Mat,
> that sounds plausible, but is it even possible to have two devices for the 
> same folder on disk, which have access to the same volumes?
> So far I believed that was impossible, but I am only a casual user of Bacula.
> 
>> On 19. Apr 2023, at 08:00, Matlink  wrote:
>> 
>> Bacula works with disk volumes similarly as it does with tape volumes. 
>> Therefore, when truncating, it needs to mount the volume in a free drive to 
>> write some metadata on it. If you have no available drive, bacula can't 
>> operate.
>> To solve this issue you probably need to declare a second drive like the 
>> first one.
>> Cheers,
>> Mat.
>> 
>> 
>> Le 19 avril 2023 00:58:39 GMT+02:00, Justin Case  a 
>> écrit :
>> Hello all,
>> 
>> while I have running backup jobs the storage is running out of space (disk 
>> file changer volumes). As the pool (pool2) that is currently written has 
>> already been truncated (manually some weeks ago), recycling of volumes does 
>> not create free space.
>> 
>> I thus wanted to truncate volumes from a different pool (pool1) while the 
>> backup is writing to pool2:
>> truncate pool=pool1-incr storage=storage1
>> 
>> I get the following error (for each purged volume in pool1)(showing just 1 
>> here):
>> 
>> Error truncating Volume “pool1-incr-vol-1109"
>> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
>> “pool2-full-vol-0703", because it is reserved by someone else.
>> 
>> What is the reason that I cannot truncate on storage1 while a backup job is 
>> running on storage1?
>> There is only 1 backup job running at a time.
>> 
>> The MaximumConcurrentJobs directives are configured as follows:
>> 
>> SD config file:
>> -Storage1 allows 20 concurrent jobs in the SD config file.
>> -The device allows for 5 concurrent jobs. 
>> 
>> Director config file:
>> -The director allows 20 concurrent jobs.
>> -Storage1 only allows 1 concurrent job in the director config file. Would 
>> this have to be configured to the same number as in the SD config file?
>> -Is the limit of 1 here prohibiting me to truncate while the backup job is 
>> running?
>> -The clients allow only 1 concurrent job. 
>> 
>> FD config file:
>> -The FD allows 20 concurrent jobs.
>> 
>> In general I want jobs to run sequentially, but truncating should be able to 
>> happen simultaneously. Is it possible to realize that?
>> Wich MaximumConcurrentJobs directives would I need to change and how?
>> 
>> Thanks for taking the time to consider my question,
>>  J/C
>> Bacula-users mailing list
>> 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

Re: [Bacula-users] Q: cannot truncate volumes while backup running on same storage, need advice to set MaximumCOncurrentJobs properly

[Justin Case]

Thanks Mat,
that sounds plausible, but is it even possible to have two devices for the same 
folder on disk, which have access to the same volumes?
So far I believed that was impossible, but I am only a casual user of Bacula.

> On 19. Apr 2023, at 08:00, Matlink  wrote:
> 
> Bacula works with disk volumes similarly as it does with tape volumes. 
> Therefore, when truncating, it needs to mount the volume in a free drive to 
> write some metadata on it. If you have no available drive, bacula can't 
> operate.
> To solve this issue you probably need to declare a second drive like the 
> first one.
> Cheers,
> Mat.
> 
> 
> Le 19 avril 2023 00:58:39 GMT+02:00, Justin Case  a 
> écrit :
> Hello all,
> 
> while I have running backup jobs the storage is running out of space (disk 
> file changer volumes). As the pool (pool2) that is currently written has 
> already been truncated (manually some weeks ago), recycling of volumes does 
> not create free space.
> 
> I thus wanted to truncate volumes from a different pool (pool1) while the 
> backup is writing to pool2:
> truncate pool=pool1-incr storage=storage1
> 
> I get the following error (for each purged volume in pool1)(showing just 1 
> here):
> 
> Error truncating Volume “pool1-incr-vol-1109"
> 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume 
> “pool2-full-vol-0703", because it is reserved by someone else.
> 
> What is the reason that I cannot truncate on storage1 while a backup job is 
> running on storage1?
> There is only 1 backup job running at a time.
> 
> The MaximumConcurrentJobs directives are configured as follows:
> 
> SD config file:
> -Storage1 allows 20 concurrent jobs in the SD config file.
> -The device allows for 5 concurrent jobs. 
> 
> Director config file:
> -The director allows 20 concurrent jobs.
> -Storage1 only allows 1 concurrent job in the director config file. Would 
> this have to be configured to the same number as in the SD config file?
> -Is the limit of 1 here prohibiting me to truncate while the backup job is 
> running?
> -The clients allow only 1 concurrent job. 
> 
> FD config file:
> -The FD allows 20 concurrent jobs.
> 
> In general I want jobs to run sequentially, but truncating should be able to 
> happen simultaneously. Is it possible to realize that?
> Wich MaximumConcurrentJobs directives would I need to change and how?
> 
> Thanks for taking the time to consider my question,
>  J/C
> Bacula-users mailing list
> 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