Re: [Bacula-users] Distributed Bacula daemons

2021-12-20 Thread Gary R. Schmidt

On 21/12/2021 13:52, Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) wrote:

Hi all,

We need to host bacula-dir, bacula-sd and PostgreSQL on different 
servers, what is an efficient architecture amongst the two options given 
below:


 1. Hosting bacula-dir and PostgreSQL together on one host, bacula-sd on
another host
 2. Hosting bacula-dir on one host, bacula-sd and PostgreSQL together on
another host


Director and Storage Daemon on one system.
Database on another.

Cheers,
GaryB-)


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


[Bacula-users] Distributed Bacula daemons

2021-12-20 Thread Shaligram Bhagat, Yateen (Nokia - IN/Bangalore)
Hi all,

We need to host bacula-dir, bacula-sd and PostgreSQL on different servers, what 
is an efficient architecture amongst the two options given below:


  1.  Hosting bacula-dir and PostgreSQL together on one host, bacula-sd on 
another host
  2.  Hosting bacula-dir on one host, bacula-sd and PostgreSQL together on 
another host

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


Re: [Bacula-users] bconsole 'stop' command always cancels job instead

2021-12-20 Thread Graham Sparks
Thanks very much Bill--that's good to know.

Also, thank you for reminding me there's a Mantis site (I'd completely 
forgotten)!


From: Bill Arlofski via Bacula-users 
Sent: 19 December 2021 21:05
To: bacula-users@lists.sourceforge.net 
Subject: Re: [Bacula-users] bconsole 'stop' command always cancels job instead

On 12/19/21 13:28, Graham Sparks wrote:
> Hello,
>
> I just wondered if anyone else has seen this problem.  I wanted to disconnect 
> the removable disk of a running job so that I
> could reconnect it to a faster USB port.  I thought I'd try the "stop" 
> bconsole command to stop and restart the job in
> question.  However, my Bacula director always seems to cancel running jobs 
> instead, stating that the job hasn't started and
> so cannot be stopped.  Of course, the cancelled job cannot be resumed (and is 
> not marked as 'Incomplete').  Here is an
> example from bconsole:

Hello Graham,

Yes, I reported this as a bug a while ago. It has been fixed and should be in 
the next release (11.0.6 or higher, depending
if they make the jump to 13 as I am expecting)

https://bugs.bacula.org/view.php?id=2610


Best regards,
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] Why isn't bacula recycling these volumes?

2021-12-20 Thread Eric Bollengier via Bacula-users

Hello Larry,

On 12/8/21 15:08, Larry Rosenman wrote:
I have a bunch of volumes that bacula seems to have forgotten about. Can you 
explain why?


Also, what SQL/etc can I do to fix it?

Attached are a DB list for the volumes, and the ls -l.


Normally the information about the pruning/recycling is printed in the
debug trace file, something with

 setdebug trace=1 level=100 tags=volume,sql dir

It should give give you the different traces and SQL commands that
are used to list volumes and jobs and prune them. You might look them
and check why the records are not properly sent back. (Recycle=No,
VolumeRetention=0, incorrect Pool, incorrect status, etc...)

Then it depends on your different settings, for example, I have seen
that you are using a Volume Retention = 0, that means the recycling
algorithm is disabled for your volume, it might explain why you cannot
achieve what you want. In recent Bacula versions, the pruning
algorithm has bee reviewed to not prune jobs that are necessary to
restore to the last restore point. So, you might need to run a Full
or a Differential backup to get rid of a chain of Incremental jobs
for example. If you don't want to use that feature, the Volume Retention
is the last variable that is checked for a volume, set it to 2 hours,
and after 2 hours, a Full/Used volume in a Pool A should be recycled
when a new job in Pool A requires a volume.


Hope it helps!

Best Regards,
Eric


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