Re: [Bacula-users] Q: regarding bconsole.conf on Bacula client machines

[Marcin Haba]

Hello Justin,

On Wed, 15 Jun 2022 at 16:55, Justin Case  wrote:

> Thanks, I understand.
> Still the partial questions are open where I find the corresponding secret
> strings in Baculum. I am not complaining, just want to make explicit that
> not all parts of the questions are answered yet.
>
> Where ein Baculum do I find the bconsole secret for the bcsonsole config
> file? I understand that it must be somehow possible to restrict the
> bconsole access using ACLs. I am just trying to understand where in the
> most basic config I would find the secret (which menu path in Baculum).
>

This password is stored in files in two places: in your file daemon config
and in tray monitor config. If you want to see the password on the Baculum
interface, you need to install Baculum API on the file daemon host with
configuration feature enabled (bfdjson configured). After you need to
connect this host to your Baculum Web. At the end you need to go to:

Main menu -> Clients -> [ select the client ] -> Tab: Configure file daemon
-> Section: Director

If you have everything (Bacula and Baculum API/Web) already configured on
one host with the configuration feature enabled in API, you don't need to
add any additional API host.

In the same way you can monitor storage daemons and directors. In this case
the director configuration for the monitor connection will be in:

Main menu -> Director -> Tab: Configure director -> Console

and storage daemon configuration for the monitor will be in:

Main menu -> Storage -> [ select the storage ] -> Tab: Configure storage
daemon -> Section: Director

Best regards,
Marcin Haba (gani)


> Also: on what operating systems there is a tray monitor available that
> then uses the bacula-mon interface? Is this a Windows-specific thing? (So
> this interface is for localhost use only I I should find the corresponding
> secret string in the config for the tray app?). I am using mostly macOS and
> Debian, some FreeBSD - is this relevant on these platforms? (I don’t have
> Windows at all. Lucky me.)
>
> Thanks again,
>  J/C
>
>
> On 15. Jun 2022, at 16:39, Josh Fisher  wrote:
>
>
> On 6/15/22 08:12, Justin Case wrote:
>
> Hi all,
>
> when installing the bacula-client packageon Debian I end up i /etc/bacula
> with
> bacula-fd.conf
> and
> bconsole.conf
>
> I have 2 questions, that are still open although I searched through the
> main documentation and read the chapters containing bconsole.conf:
>
> (1) In bacula-fd.conf I understand how to set up the FileDaemon resource.
> I also understand how to set up the Director resource for bacula-dir, so
> that the actual backup works. There always is a second Director resource
> for bacula-mon and I do not understand what it used for and where I find
> the secret string in Baculum UI on the Bacula Director machine to put in
> Password for the Director resource on the Bacula FD client machine.
>
>
>
> The second bacula-mon Director interface is for the tray monitor app
> running on the client machine. The tray monitor acts as a simplified
> director only for retrieving info from the bacula-fd daemon.
>
> (2) What is the use for the bconsole.conf file on the Bacula FD client
> machine? Is it a means to allow the admin of the client machine to take a
> look at the jobs on the Bacula Director machine concerning this client
> machine? If I wanted this to work, where in Baculum UI on the Bacula
> Director machine do I find the secret string to put in Password for the
> Director resource in bcsonsole.conf on the client machine?
>
>
>
> That is the configuration file for the bconsole command line utility used
> to interface with Director and Storage daemons.
>
>
>
> Thanks for considering my questions and all the best,
>  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
>


-- 
"Greater love hath no man than this, that a man lay down his life for his
friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za
przyjaciół swoich." Jezus Chrystus
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive

[Justin Case]

Hi there,

I have a client behind a firewall and the director is unable to connect to this 
client, but the client may connect to the director and to the SD.

In the main manual is documented that one should to this:

on the Director side in the Client directive: 
  AllowFDConnections = yes

on the FD side in the Director directive:
Director {
  Name = bacula-dir
  Password = “redacted”
#  DirPort = 9101
  Address = bacula-dir.lan.net
  ConnectToDirector = yes
  ReconnectionTime = 40 min
}

I have done this, but the bacula-fd complains:

bacula-fd: ERROR TERMINATION at parse_conf.c:1157
Config error: Keyword "ConnectToDirector" not permitted in this resource.
Perhaps you left the trailing brace off of the previous resource.
: line 22, col 20 of file /etc/bacula/bacula-fd.conf
  ConnectToDirector = yes

Actually it would also complain about DirPort in the same way if I remove the 
comment character.

It looks like the documentation does not fit the behaviour of the Debian 
bacula-client package.

What can I do now?

Best
 J/C



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

Re: [Bacula-users] Q: fileset "magic" - still weird

[Justin Case]

Hello John,

I found this approach quite compelling:

> On 16. Jun 2022, at 00:24, John Lockard  wrote:
> 
> |sh -c ’echo /mnt/cdat-*’
No matter what characters i use for the ‘ I get "Error sending include list.” 
(already put in the actual pathes for sh and echo). Log: bacula-dir JobId 0: 
Fatal error: Error running program: /usr/bin/sh -c `/usr/bin/echo 
/mnt/containerdata-*`. ERR=No such file or directory

Running the same command in the shell on the host works.

So I tried this: RegexDir = ""^(?!cdat-).*

I turns out the the “?!” unfortunately leads to terminally crapping up the 
Baculum in my Bacula-Server container. I actually need to remove all the 
containers images and reainstall it. That doesn’t sound right, but its not a 
solution for me.

I am trying with regexdir for inclusion now.

Thanks anyways,
 J/C


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

Re: [Bacula-users] Q: fileset "magic" - still weird

[John Lockard]

Fileset {
 Name = “cadat"
 EnableVss = no
 EnableSnapshot = no
 Include {
   Options {
 OneFS = no
 RegexDir = "/mnt/cdat-.*"
   }
   Options {
 OneFS = no
 Exclude = yes
 RegexDir = ".*"
   }
   File = "/mnt"
 }
}

Justin, looking at this, Within /mnt, doesn't your exclude (".*") just end
up excluding everything?

Maybe you want something more like:

Include {
  Options {
OneFS = noExclude = yes
RegexDir = ""^(?!cdat-).*
  }
  File = /mnt
}


Or, get rid of the "Exclude" and use a script for the File...

Include {
  Options {
OneFS = no  }
  File = "|sh -c ’echo /mnt/cdat-*’"
}

Maybe?


On Wed, Jun 15, 2022 at 5:48 PM Justin Case  wrote:

> I understand what the example does, it is very much standard.
> Alas, it does not touch any of the points where my use case is special:
> - it enumerates all inclusions and exclusions - that is explicitely what I
> cannot and do not want to do as each FD machine has different subfolders,
> but all start with the same prefix
> - it does not employ wildcard characters for folder names
>
> Thank you for the example. To be honest, I did not learn anything new that
> would allow me to solve my problem.
>
> Thank you again , though, for considering my questions.
> J/C
>
> > On 15. Jun 2022, at 23:23, sru...@gemneye.org wrote:
> >
> > On 2022-06-15 13:47, Justin Case wrote:
> >> I re-read the chapter about filesets and fileset options.
> >> In order to better understand what is happening I simplified the
> >> fileset as follows:
> >>> Fileset {
> >>> Name = “cadat"
> >>> EnableVss = no
> >>> EnableSnapshot = no
> >>> Include {
> >>>   Options {
> >>> OneFS = no
> >>> #RegexDir = "/mnt/cdat-.*"
> >>>   }
> >>> #  Options {
> >>> #OneFS = no
> >>> #   Exclude = yes
> >>> #RegexDir = ".*”
> >>> #  }
> >>>   File = "/mnt"
> >>> }
> >>> }
> >> I was hoping it would then backup everything in /mnt (yes they are all
> >> different filesystems, but OneFS is set to no).
> >> Again, nothing was backed up.
> >> I do not understand this result. I thought I had understood what is in
> >> the manual about filesets, but obviously I did not.
> >>> On 15. Jun 2022, at 19:55, Justin Case  wrote:
> >>> Hi all,
> >>> I am somewhat struggling with the fileset algorithm, noob birth pains
> I guess.
> >>> I have a bunch of VMs that have mounted(!!) docker container appdata
> in /mnt/cdat-.
> >>> So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish
> that the content of each subdirectory in /mnt where the name starts with
> "cdat-“ gets backed up.
> >>> So I looked into the main manual for fileset directive syntax. And I
> found this example:
> >>> FileSet {
> >>>  Name = "Full Set”
> >>>  Include {
> >>> Options {
> >>>  wilddir = "/home/a*”
> >>>  wilddir = "/home/b*"
> >>> }
> >>> Options {
> >>> RegexDir = ".*”
> >>> exclude = yes
> >>>   }
> >>> File = /home
> >>> }
> >>> }
> >>> So what I did is this (and it does not work, just returns 1 file, and
> that is wrong):
> >>> Fileset {
> >>> Name = “cadat"
> >>> EnableVss = no
> >>> EnableSnapshot = no
> >>> Include {
> >>>   Options {
> >>> OneFS = no
> >>> RegexDir = "/mnt/cdat-.*"
> >>>   }
> >>>   Options {
> >>> OneFS = no
> >>> Exclude = yes
> >>> RegexDir = ".*"
> >>>   }
> >>>   File = "/mnt"
> >>> }
> >>> }
> >>> I know it must seem kinda obvious where the problem is for those who
> have been around with bacula for a while. For me it is kinda “magic”.
> >>> Where is my mistake?
> >>> Thanks for helping out!
> >>> J/C
> > Below is an example Fileset I use which has includes and excludes.
> >
> > Fileset {
> >  Name = "Firewall Full"
> >  Include {
> >File = "/"
> >File = "/boot"
> >File = "/home"
> >File = "/var"
> >Options {
> >  Compression = "Gzip"
> >  Signature = "Md5"
> >  Exclude = "Yes"
> >  WildDir = "/ISO"
> >  WildFile = "/.journal"
> >  WildFile = "/.fsck"
> >}
> >  }
> > }
> >
>
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>


-- 
- Adaptability -- Analytical --- Ideation  Input - Belief -
---
 John M. Lockard |  U of Michigan - School of Information
  Unix Sys Admin |  Suite 205 | 309 Maynard Street
  jlock...@umich.edu |Ann Arbor, MI  48104-2211
 www.umich.edu/~jlockard  |
734-615-8776 | 734-763-9677 FAX
---
- The University of Michigan will never ask you for your password -
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net

Re: [Bacula-users] Q: fileset "magic" - still weird

[Bill Arlofski via Bacula-users]

On 6/15/22 15:23, sruckh--- via Bacula-users wrote:> Below is an example 
Fileset I use which has includes and excludes.


Fileset {
Name = "Firewall Full"
Include {
  File = "/"
  File = "/boot"
  File = "/home"
  File = "/var"
  Options {
Compression = "Gzip"
Signature = "Md5"
Exclude = "Yes"
WildDir = "/ISO"
WildFile = "/.journal"
WildFile = "/.fsck"
  }
}
}


Hello,

I don't think yout fileset is working the way you think/want.


This fileset will not compress, nor create md5 signature for any files in /, /boot 
/home, or /var. I'd expect you to see "No
signature found for file " during restores. (or some similar message)

In words, your example fileset says to backup those included directories and 
below, but exclude those two wild files, and one
wilddir, but only if they are found in the root directory.

But, I am not even sure th
ose wilddir and wildfiles will correctly work because you have not included any 
wildcards in them.


I would re-write this fileset as follows:
8<
FileSet {
  Name = FirewallFull
  Include {
Options {
  compression = gzip
  signature = md5
}
File = "/"
File = "/boot"
File = "/home"
File = "/var"
  }
  Exclude {
File = ISO
File = .fsck
File = .journal
  }
}
8<

This example will compress and create an md5 signature for everything under /, 
/boot /home, or /var, and then will exclude
any files or directories called ISO, .fsck, and .journal wherever they are 
found.

If you want to anchor them to the root directory only, then set them to /ISO, 
/.fsck, and /.journal


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: fileset "magic" - still weird

[Justin Case]

I understand what the example does, it is very much standard.
Alas, it does not touch any of the points where my use case is special:
- it enumerates all inclusions and exclusions - that is explicitely what I 
cannot and do not want to do as each FD machine has different subfolders, but 
all start with the same prefix
- it does not employ wildcard characters for folder names

Thank you for the example. To be honest, I did not learn anything new that 
would allow me to solve my problem.

Thank you again , though, for considering my questions.
J/C

> On 15. Jun 2022, at 23:23, sru...@gemneye.org wrote:
> 
> On 2022-06-15 13:47, Justin Case wrote:
>> I re-read the chapter about filesets and fileset options.
>> In order to better understand what is happening I simplified the
>> fileset as follows:
>>> Fileset {
>>> Name = “cadat"
>>> EnableVss = no
>>> EnableSnapshot = no
>>> Include {
>>>   Options {
>>> OneFS = no
>>> #RegexDir = "/mnt/cdat-.*"
>>>   }
>>> #  Options {
>>> #OneFS = no
>>> #   Exclude = yes
>>> #RegexDir = ".*”
>>> #  }
>>>   File = "/mnt"
>>> }
>>> }
>> I was hoping it would then backup everything in /mnt (yes they are all
>> different filesystems, but OneFS is set to no).
>> Again, nothing was backed up.
>> I do not understand this result. I thought I had understood what is in
>> the manual about filesets, but obviously I did not.
>>> On 15. Jun 2022, at 19:55, Justin Case  wrote:
>>> Hi all,
>>> I am somewhat struggling with the fileset algorithm, noob birth pains I 
>>> guess.
>>> I have a bunch of VMs that have mounted(!!) docker container appdata in 
>>> /mnt/cdat-.
>>> So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish that 
>>> the content of each subdirectory in /mnt where the name starts with "cdat-“ 
>>> gets backed up.
>>> So I looked into the main manual for fileset directive syntax. And I found 
>>> this example:
>>> FileSet {
>>>  Name = "Full Set”
>>>  Include {
>>> Options {
>>>  wilddir = "/home/a*”
>>>  wilddir = "/home/b*"
>>> }
>>> Options {
>>> RegexDir = ".*”
>>> exclude = yes
>>>   }
>>> File = /home
>>> }
>>> }
>>> So what I did is this (and it does not work, just returns 1 file, and that 
>>> is wrong):
>>> Fileset {
>>> Name = “cadat"
>>> EnableVss = no
>>> EnableSnapshot = no
>>> Include {
>>>   Options {
>>> OneFS = no
>>> RegexDir = "/mnt/cdat-.*"
>>>   }
>>>   Options {
>>> OneFS = no
>>> Exclude = yes
>>> RegexDir = ".*"
>>>   }
>>>   File = "/mnt"
>>> }
>>> }
>>> I know it must seem kinda obvious where the problem is for those who have 
>>> been around with bacula for a while. For me it is kinda “magic”.
>>> Where is my mistake?
>>> Thanks for helping out!
>>> J/C
> Below is an example Fileset I use which has includes and excludes.
> 
> Fileset {
>  Name = "Firewall Full"
>  Include {
>File = "/"
>File = "/boot"
>File = "/home"
>File = "/var"
>Options {
>  Compression = "Gzip"
>  Signature = "Md5"
>  Exclude = "Yes"
>  WildDir = "/ISO"
>  WildFile = "/.journal"
>  WildFile = "/.fsck"
>}
>  }
> }
> 



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

Re: [Bacula-users] Q: fileset "magic" - still weird

[sruckh--- via Bacula-users]

On 2022-06-15 13:47, Justin Case wrote:

I re-read the chapter about filesets and fileset options.
In order to better understand what is happening I simplified the
fileset as follows:


Fileset {
 Name = “cadat"
 EnableVss = no
 EnableSnapshot = no
 Include {
   Options {
 OneFS = no
 #RegexDir = "/mnt/cdat-.*"
   }
 #  Options {
 #OneFS = no
 #   Exclude = yes
 #RegexDir = ".*”
 #  }
   File = "/mnt"
 }
}



I was hoping it would then backup everything in /mnt (yes they are all
different filesystems, but OneFS is set to no).

Again, nothing was backed up.

I do not understand this result. I thought I had understood what is in
the manual about filesets, but obviously I did not.




On 15. Jun 2022, at 19:55, Justin Case  wrote:

Hi all,

I am somewhat struggling with the fileset algorithm, noob birth pains 
I guess.


I have a bunch of VMs that have mounted(!!) docker container appdata 
in /mnt/cdat-.


So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish 
that the content of each subdirectory in /mnt where the name starts 
with "cdat-“ gets backed up.


So I looked into the main manual for fileset directive syntax. And I 
found this example:


FileSet {
 Name = "Full Set”
 Include {
Options {
 wilddir = "/home/a*”
 wilddir = "/home/b*"
}
Options {
RegexDir = ".*”
exclude = yes
  }
File = /home
}
}

So what I did is this (and it does not work, just returns 1 file, and 
that is wrong):


Fileset {
 Name = “cadat"
 EnableVss = no
 EnableSnapshot = no
 Include {
   Options {
 OneFS = no
 RegexDir = "/mnt/cdat-.*"
   }
   Options {
 OneFS = no
 Exclude = yes
 RegexDir = ".*"
   }
   File = "/mnt"
 }
}

I know it must seem kinda obvious where the problem is for those who 
have been around with bacula for a while. For me it is kinda “magic”.


Where is my mistake?

Thanks for helping out!
J/C



Below is an example Fileset I use which has includes and excludes.

Fileset {
  Name = "Firewall Full"
  Include {
File = "/"
File = "/boot"
File = "/home"
File = "/var"
Options {
  Compression = "Gzip"
  Signature = "Md5"
  Exclude = "Yes"
  WildDir = "/ISO"
  WildFile = "/.journal"
  WildFile = "/.fsck"
}
  }
}


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

Re: [Bacula-users] Q: fileset "magic" - still weird

[Justin Case]

I re-read the chapter about filesets and fileset options.
In order to better understand what is happening I simplified the fileset as 
follows:

> Fileset {
>  Name = “cadat"
>  EnableVss = no
>  EnableSnapshot = no
>  Include {
>Options {
>  OneFS = no
>  #RegexDir = "/mnt/cdat-.*"
>}
>  #  Options {
>  #OneFS = no
>  #   Exclude = yes
>  #RegexDir = ".*”
>  #  }
>File = "/mnt"
>  }
> }


I was hoping it would then backup everything in /mnt (yes they are all 
different filesystems, but OneFS is set to no).

Again, nothing was backed up.

I do not understand this result. I thought I had understood what is in the 
manual about filesets, but obviously I did not.



> On 15. Jun 2022, at 19:55, Justin Case  wrote:
> 
> Hi all,
> 
> I am somewhat struggling with the fileset algorithm, noob birth pains I guess.
> 
> I have a bunch of VMs that have mounted(!!) docker container appdata in 
> /mnt/cdat-.
> 
> So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish that the 
> content of each subdirectory in /mnt where the name starts with "cdat-“ gets 
> backed up.
> 
> So I looked into the main manual for fileset directive syntax. And I found 
> this example:
> 
> FileSet { 
>Name = "Full Set” 
>Include { 
>   Options { 
>wilddir = "/home/a*” 
>wilddir = "/home/b*" 
>   }
>   Options {
>   RegexDir = ".*”
>   exclude = yes 
> } 
>   File = /home 
>   }
> } 
> 
> So what I did is this (and it does not work, just returns 1 file, and that is 
> wrong):
> 
> Fileset {
>  Name = “cadat"
>  EnableVss = no
>  EnableSnapshot = no
>  Include {
>Options {
>  OneFS = no
>  RegexDir = "/mnt/cdat-.*"
>}
>Options {
>  OneFS = no
>  Exclude = yes
>  RegexDir = ".*"
>}
>File = "/mnt"
>  }
> }
> 
> I know it must seem kinda obvious where the problem is for those who have 
> been around with bacula for a while. For me it is kinda “magic”.
> 
> Where is my mistake?
> 
> Thanks for helping out!
> J/C
> 
> 



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

[Bacula-users] Q: fileset "magic"

[Justin Case]

Hi all,

I am somewhat struggling with the fileset algorithm, noob birth pains I guess.

I have a bunch of VMs that have mounted(!!) docker container appdata in 
/mnt/cdat-.

So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish that the 
content of each subdirectory in /mnt where the name starts with "cdat-“ gets 
backed up.

So I looked into the main manual for fileset directive syntax. And I found this 
example:

FileSet { 
 Name = "Full Set” 
 Include { 
Options { 
 wilddir = "/home/a*” 
 wilddir = "/home/b*" 
}
Options {
RegexDir = ".*”
exclude = yes 
  } 
File = /home 
}
} 

So what I did is this (and it does not work, just returns 1 file, and that is 
wrong):

Fileset {
  Name = “cadat"
  EnableVss = no
  EnableSnapshot = no
  Include {
Options {
  OneFS = no
  RegexDir = "/mnt/cdat-.*"
}
Options {
  OneFS = no
  Exclude = yes
  RegexDir = ".*"
}
File = "/mnt"
  }
}

I know it must seem kinda obvious where the problem is for those who have been 
around with bacula for a while. For me it is kinda “magic”.

Where is my mistake?

Thanks for helping out!
 J/C




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

Re: [Bacula-users] Q: one job for a group of "identical" machines using the same fileset?

[Justin Case]

Thanks, found it under Director > Configure Director > JobDefs

> On 15. Jun 2022, at 18:28, Bill Arlofski via Bacula-users 
>  wrote:
> 
> On 6/15/22 10:21, Justin Case wrote:
>> Hi there,
>> 
>> in the age of virtualization and cloud technology such as Kubernetes I would 
>> assume that people might have a lot of VMs that use the same setup where 
>> they may store container user data under the same path for each machine.
>> 
>> While I see that it is possible to define just one fileset to use for all 
>> these VMs, I seem to miss a way to define a job that is run for a group of 
>> clients (e.g. sequentially for each of them to not overload the VM host) for 
>> the same fileset.
>> 
>> Is there way in Bacula to achieve this or is this a hard limitation that a 
>> need an individual job per each bacula-fd machine?
>> 
>> Just looking for clarification, before I proceed setting up a larger number 
>> of jobs (which is a pain, even if you can use the templating in Baculum).
>> 
>> Thanks and best,
>>  J/C
> 
> With Bacula, it is "One Client Per Job"
> 
> So in your example, you would create a Job template, that uses a JobDefs{} 
> resource containing all t
> he things common to the
> jobs (Fileset, Priority, Messages, Storage, Pool, etc), then for each Job, 
> just use that JobDefs and only override the things
> that will be different, like the Client, for example.
> 
> 
> 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] Q: one job for a group of "identical" machines using the same fileset?

[dmitri maziuk]

On 2022-06-15 11:21 AM, Justin Case wrote:


in the age of virtualization and cloud technology such as Kubernetes I would 
assume that people might have a lot of VMs that use the same setup where they 
may store container user data under the same path for each machine.


This is somewhat related to your FreeNAS question: VM/container storage 
tend to be iSCSI volumes, not network shares, so they have to be backed 
up from the client. Each has to have their own bacula client and each 
client has to have a job.


ZFS will let you export its filesystems as iSCSI volumes. You can 
snapshot them, ship the snapshots away, back up the snapshots etc. I 
don't see why you couldn't do all your volumes as one job.


Dima


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

Re: [Bacula-users] Q: one job for a group of "identical" machines using the same fileset?

[Bill Arlofski via Bacula-users]

On 6/15/22 10:21, Justin Case wrote:

Hi there,

in the age of virtualization and cloud technology such as Kubernetes I would 
assume that people might have a lot of VMs that use the same setup where they 
may store container user data under the same path for each machine.

While I see that it is possible to define just one fileset to use for all these 
VMs, I seem to miss a way to define a job that is run for a group of clients 
(e.g. sequentially for each of them to not overload the VM host) for the same 
fileset.

Is there way in Bacula to achieve this or is this a hard limitation that a need 
an individual job per each bacula-fd machine?

Just looking for clarification, before I proceed setting up a larger number of 
jobs (which is a pain, even if you can use the templating in Baculum).

Thanks and best,
  J/C


With Bacula, it is "One Client Per Job"

So in your example, you would create a Job template, that uses a JobDefs{} 
resource containing all t
he things common to the
jobs (Fileset, Priority, Messages, Storage, Pool, etc), then for each Job, just 
use that JobDefs and only override the things
that will be different, like the Client, for example.


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

[Bacula-users] Q: one job for a group of "identical" machines using the same fileset?

[Justin Case]

Hi there,

in the age of virtualization and cloud technology such as Kubernetes I would 
assume that people might have a lot of VMs that use the same setup where they 
may store container user data under the same path for each machine.

While I see that it is possible to define just one fileset to use for all these 
VMs, I seem to miss a way to define a job that is run for a group of clients 
(e.g. sequentially for each of them to not overload the VM host) for the same 
fileset. 

Is there way in Bacula to achieve this or is this a hard limitation that a need 
an individual job per each bacula-fd machine?

Just looking for clarification, before I proceed setting up a larger number of 
jobs (which is a pain, even if you can use the templating in Baculum).

Thanks and best,
 J/C



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

Re: [Bacula-users] Q: Bacula for TrueNAS Core?

[Austin C Phelps]

Bacula is in the freebsd freshports. Currently 11.0.5 is the highest version. 
There are other versions there as well. To use it you create a jail, then you 
can install from freshports. You can mount your datasets into the jail from the 
jails tool.

Now truenas scale you either have to side load or compile. I not to that point 
yet. I'm still testing backing up my cores first. I did ask in ix discord about 
bacula and scale but didn't a response. It's probably still to cutting edge at 
this point.

I gotten sas tape drives and loaders working in the jail. Freebsd uses a 
different program to change media. The script included with the freshport 
doesn't work correctly. I had to modify it. My tape system has an iscsi bridge 
which doesn't work in freebsd. I had to run the SD in Linux. I did have to 
compile bacula in Linux so I could get the versions to match.

If you want I can post my code how I got it all working.

Get Outlook for Android

From: Justin Case 
Sent: Wednesday, June 15, 2022 6:49:06 AM
To: Bacula users 
Subject: [Bacula-users] Q: Bacula for TrueNAS Core?

Hello all,

I was looking for a Bacula Plugin for a recent TrueNAS Core (bacula-fd to 
backup its content, bacula-dir, bacula-sd to backup other machines’ content). I 
can see that there has been a Bacula Plugin maintained by iX-Systems for 
FreeNAS in the past, but it has been abandoned by iX-Systems.

Since TrueNAS Core is the closest we get for free to something like an 
enterprise storage appliance, I was assuming it makes a lot of sense and there 
is a lot of demand to have Bacula for TrueNAS Core. I haven’t found it in the 
Community Plugins either.

I saw that someone on this list was compiling Bacula for TrueNAS Core, so it 
must be feasible.

Are just too few people here using TrueNAS Core? Or has everyone gone through 
compiling it for themselves? Wouldn’t it be more  “user-friendly” to have a 
plugin? Maybe no-one has sufficient motivation to make and maintain one (yeah, 
I know someone is going to respond “why don’t you do it?”).
Or is there another explanation?

Or is there actually a Bacula Plugin for TrueNAS Core and I just did not look 
right and did not find it?

All the best, I am looking forward to your thoughts on this.
 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: Bacula for TrueNAS Core?

[dmitri maziuk]

On 2022-06-15 5:49 AM, Justin Case wrote:
...

All the best, I am looking forward to your thoughts on this.


My $.02 is why? If you're looking for a basic undelete/rollback 
capability, ZFS has snapshots. It can ship those incrementally to 
another ZFS system, in the long run the 2nd system tends to be cheaper 
than the tape. You can even "hold" the snapshots on the receiver have 
the filesystem mounted and accessible -- read-only of course -- while 
deleting them on the source to save space.


If you need archival forever, it's probably trivial (I haven't looked) 
to connect a "cloud bucket" and dump your ZFS snapshots onto it for 
posterity.


So I'm not quite sure why muck around with tapes, all things considered.

Dima


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

Re: [Bacula-users] Q: regarding bconsole.conf on Bacula client machines

[Justin Case]

Thanks, I understand.
Still the partial questions are open where I find the corresponding secret 
strings in Baculum. I am not complaining, just want to make explicit that not 
all parts of the questions are answered yet.

Where ein Baculum do I find the bconsole secret for the bcsonsole config file? 
I understand that it must be somehow possible to restrict the bconsole access 
using ACLs. I am just trying to understand where in the most basic config I 
would find the secret (which menu path in Baculum).

Also: on what operating systems there is a tray monitor available that then 
uses the bacula-mon interface? Is this a Windows-specific thing? (So this 
interface is for localhost use only I I should find the corresponding secret 
string in the config for the tray app?). I am using mostly macOS and Debian, 
some FreeBSD - is this relevant on these platforms? (I don’t have Windows at 
all. Lucky me.)

Thanks again,
 J/C


> On 15. Jun 2022, at 16:39, Josh Fisher  wrote:
> 
> 
> On 6/15/22 08:12, Justin Case wrote:
>> Hi all,
>> 
>> when installing the bacula-client packageon Debian I end up i /etc/bacula 
>> with
>> bacula-fd.conf
>> and
>> bconsole.conf
>> 
>> I have 2 questions, that are still open although I searched through the main 
>> documentation and read the chapters containing bconsole.conf:
>> 
>> (1) In bacula-fd.conf I understand how to set up the FileDaemon resource. I 
>> also understand how to set up the Director resource for bacula-dir, so that 
>> the actual backup works. There always is a second Director resource for 
>> bacula-mon and I do not understand what it used for and where I find the 
>> secret string in Baculum UI on the Bacula Director machine to put in 
>> Password for the Director resource on the Bacula FD client machine.
> 
> 
> The second bacula-mon Director interface is for the tray monitor app running 
> on the client machine. The tray monitor acts as a simplified director only 
> for retrieving info from the bacula-fd daemon.
> 
>> (2) What is the use for the bconsole.conf file on the Bacula FD client 
>> machine? Is it a means to allow the admin of the client machine to take a 
>> look at the jobs on the Bacula Director machine concerning this client 
>> machine? If I wanted this to work, where in Baculum UI on the Bacula 
>> Director machine do I find the secret string to put in Password for the 
>> Director resource in bcsonsole.conf on the client machine?
> 
> 
> That is the configuration file for the bconsole command line utility used to 
> interface with Director and Storage daemons.
> 
> 
>> 
>> Thanks for considering my questions and all the best,
>>  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: regarding bconsole.conf on Bacula client machines

[Josh Fisher]

On 6/15/22 08:12, Justin Case wrote:

Hi all,

when installing the bacula-client packageon Debian I end up i /etc/bacula with
bacula-fd.conf
and
bconsole.conf

I have 2 questions, that are still open although I searched through the main 
documentation and read the chapters containing bconsole.conf:

(1) In bacula-fd.conf I understand how to set up the FileDaemon resource. I 
also understand how to set up the Director resource for bacula-dir, so that the 
actual backup works. There always is a second Director resource for bacula-mon 
and I do not understand what it used for and where I find the secret string in 
Baculum UI on the Bacula Director machine to put in Password for the Director 
resource on the Bacula FD client machine.



The second bacula-mon Director interface is for the tray monitor app 
running on the client machine. The tray monitor acts as a simplified 
director only for retrieving info from the bacula-fd daemon.



(2) What is the use for the bconsole.conf file on the Bacula FD client machine? 
Is it a means to allow the admin of the client machine to take a look at the 
jobs on the Bacula Director machine concerning this client machine? If I wanted 
this to work, where in Baculum UI on the Bacula Director machine do I find the 
secret string to put in Password for the Director resource in bcsonsole.conf on 
the client machine?



That is the configuration file for the bconsole command line utility 
used to interface with Director and Storage daemons.





Thanks for considering my questions and all the best,
  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] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello,

On 6/15/22 14:26, Olivier Delestre wrote:

Hi,

Still in v 9.6.7 with the repo https://bacula.org/packages/5

an idea of the return of the site ?

Before i use Git but it's down too.


You can clone the repository from
https://www.bacula.org/git

The previous URL should work, but apparently not. Packages will be re-imported
in the next days.

Best Regards,
Eric


Thanks for your works.

A+

Le 03/06/2022 à 16:35, Eric Bollengier a écrit :

Hello Olivier,

On 6/3/22 15:51, OLIVIER DELESTRE (Personnel) wrote:

Hi,

What's the difference between 11.3.4 and 11.0.6 ? no, I would like to know if 
it is in beta for 11.0.6 ?


11.0.6 is the current *stable* version of Bacula.

11.3.4 is the last beta version of the next major release 13.0.0.

9.6.7 is the previous stable version of Bacula.

Hope it helps!

Best Regards,
Eric


I still with 9.6.7 in a production environnement.

Thanks for work.

Bye.

Le 03/06/2022 à 15:00, Eric Bollengier via Bacula-users a écrit :

Hello,

We are pleased to announce the new BETA release of the next major Bacula
version 11.3.4 to both the Bacula website (www.bacula.org) and to SourceForge.
Thanks for the valuable feedback.

https://www.bacula.org/downloads/Beta-Bacula-11.3.4

This is the last beta version of the new 13.0 major release with many new
features and a number of changes. Please take care to test this code carefully
before putting it into production.  Although the new features have been tested,
they have not run in a production environment.

We had a service outage this week and some of the bacula services are still not
fully recovered (cdash, wiki, packages). It should be resolved next week.

Compatibility:
--
As always, both the Director and Storage daemon(s) must be upgraded at
the same time. Any File daemon running on the same machine as a Director
or Storage daemon must be of the same version.

Older File Daemons should be compatible with the 11.3 Director and Storage
daemons.  There should be no need to upgrade older File Daemons.

New Catalog format in version 11.3.0 and greater


This release of Bacula uses a new catalog format.  We provide a set of scripts
that permit conversion from 9.x and earlier versions to the new 11.3 format
(1025).  Normally the conversion/upgrade is fast.

Keep in mind that there is a big change from 9.x to 11.0 that takes longer than
usual, the upgrade process will require about twice the disk space of the
actual database.

If you start from scratch, you don't need to run the update_bacula_tables
script because the create_bacula_tables script automatically creates the new
table format.  However, if you are using a version of Bacula older than 5.0.0
(e.g.  3.0.3) then you need to run the update_bacula_tables script that will be
found in the /src/cats directory after you run the ./configure command.

As mentioned above, before running this script, please backup your catalog
database, be sure to shutdown Bacula and be aware that running the script can
take some time depending on your database size.

Thanks for using Bacula!

Best Regards,
Eric



Changelog 11.3.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option with
  multiple incremental jobs. Add support for ACL updates
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available in the BSR

 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the catalog
 - snapshot: Add support for new LVM 2.03.15

 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue

 - Fix query SQL provided in sample-query.sql
 - Fix compilation on s3 driver
 - Fix ./configure error with test-cpp.c
 - win32: Update to OpenSSL 1.1.1o

 - baculum: Fix clearing OAuth2 properties after testing API connection on 
security page
 - baculum: Fix directing to default page after log in for users with 
non-admin roles

 - baculum: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD 
and older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8

Bugs fixed/closed since last release:
2633 2658 2659 2661 2662 2667 9116 9125 9127 9143




New Features:
 - Job Storage group support
 - Kubernetes Plugin
 - New Accurate Option to Save Only File's Metadata
 - Windows CSV (Cluster Shared Volumes) support
 - Adding more logging for daemon<->daemon connection in job output
 - Tag support on catalog objects
 - Support for SHA256 and SHA512 signatures in FileSet
 - 

Re: [Bacula-users] Beta Release 11.3.4

[Olivier Delestre]

Hi,

Still in v 9.6.7 with the repo https://bacula.org/packages/5

an idea of the return of the site ?

Before i use Git but it's down too.

Thanks for your works.

A+

Le 03/06/2022 à 16:35, Eric Bollengier a écrit :

Hello Olivier,

On 6/3/22 15:51, OLIVIER DELESTRE (Personnel) wrote:

Hi,

What's the difference between 11.3.4 and 11.0.6 ? no, I would like to 
know if it is in beta for 11.0.6 ?


11.0.6 is the current *stable* version of Bacula.

11.3.4 is the last beta version of the next major release 13.0.0.

9.6.7 is the previous stable version of Bacula.

Hope it helps!

Best Regards,
Eric


I still with 9.6.7 in a production environnement.

Thanks for work.

Bye.

Le 03/06/2022 à 15:00, Eric Bollengier via Bacula-users a écrit :

Hello,

We are pleased to announce the new BETA release of the next major 
Bacula
version 11.3.4 to both the Bacula website (www.bacula.org) and to 
SourceForge.

Thanks for the valuable feedback.

https://www.bacula.org/downloads/Beta-Bacula-11.3.4

This is the last beta version of the new 13.0 major release with 
many new
features and a number of changes. Please take care to test this code 
carefully
before putting it into production.  Although the new features have 
been tested,

they have not run in a production environment.

We had a service outage this week and some of the bacula services 
are still not
fully recovered (cdash, wiki, packages). It should be resolved next 
week.


Compatibility:
--
As always, both the Director and Storage daemon(s) must be upgraded at
the same time. Any File daemon running on the same machine as a 
Director

or Storage daemon must be of the same version.

Older File Daemons should be compatible with the 11.3 Director and 
Storage

daemons.  There should be no need to upgrade older File Daemons.

New Catalog format in version 11.3.0 and greater


This release of Bacula uses a new catalog format.  We provide a set 
of scripts
that permit conversion from 9.x and earlier versions to the new 11.3 
format

(1025).  Normally the conversion/upgrade is fast.

Keep in mind that there is a big change from 9.x to 11.0 that takes 
longer than
usual, the upgrade process will require about twice the disk space 
of the

actual database.

If you start from scratch, you don't need to run the 
update_bacula_tables
script because the create_bacula_tables script automatically creates 
the new
table format.  However, if you are using a version of Bacula older 
than 5.0.0
(e.g.  3.0.3) then you need to run the update_bacula_tables script 
that will be
found in the /src/cats directory after you run the 
./configure command.


As mentioned above, before running this script, please backup your 
catalog
database, be sure to shutdown Bacula and be aware that running the 
script can

take some time depending on your database size.

Thanks for using Bacula!

Best Regards,
Eric



Changelog 11.3.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option 
with

  multiple incremental jobs. Add support for ACL updates
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available 
in the BSR


 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the 
catalog

 - snapshot: Add support for new LVM 2.03.15

 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue

 - Fix query SQL provided in sample-query.sql
 - Fix compilation on s3 driver
 - Fix ./configure error with test-cpp.c
 - win32: Update to OpenSSL 1.1.1o

 - baculum: Fix clearing OAuth2 properties after testing API 
connection on security page
 - baculum: Fix directing to default page after log in for users 
with non-admin roles

 - baculum: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for 
FreeBSD and older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8

Bugs fixed/closed since last release:
2633 2658 2659 2661 2662 2667 9116 9125 9127 9143




New Features:
 - Job Storage group support
 - Kubernetes Plugin
 - New Accurate Option to Save Only File's Metadata
 - Windows CSV (Cluster Shared Volumes) support
 - Adding more logging for daemon<->daemon connection in job output
 - Tag support on catalog objects
 - Support for SHA256 and SHA512 signatures in FileSet
 - External LDAP Console Authentication

Misc Features:
 - Windows Installer Silent Mode options
 - Add PriorJob to llist job output
 - Check for IP SANs when verifying TLS certs
 - Clarify SD vbackup 

[Bacula-users] Q: regarding bconsole.conf on Bacula client machines

[Justin Case]

Hi all,

when installing the bacula-client packageon Debian I end up i /etc/bacula with
bacula-fd.conf
and
bconsole.conf

I have 2 questions, that are still open although I searched through the main 
documentation and read the chapters containing bconsole.conf:

(1) In bacula-fd.conf I understand how to set up the FileDaemon resource. I 
also understand how to set up the Director resource for bacula-dir, so that the 
actual backup works. There always is a second Director resource for bacula-mon 
and I do not understand what it used for and where I find the secret string in 
Baculum UI on the Bacula Director machine to put in Password for the Director 
resource on the Bacula FD client machine.

(2) What is the use for the bconsole.conf file on the Bacula FD client machine? 
Is it a means to allow the admin of the client machine to take a look at the 
jobs on the Bacula Director machine concerning this client machine? If I wanted 
this to work, where in Baculum UI on the Bacula Director machine do I find the 
secret string to put in Password for the Director resource in bcsonsole.conf on 
the client machine?

Thanks for considering my questions and all the best,
 J/C






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

[Bacula-users] Q: Bacula for TrueNAS Core?

[Justin Case]

Hello all,

I was looking for a Bacula Plugin for a recent TrueNAS Core (bacula-fd to 
backup its content, bacula-dir, bacula-sd to backup other machines’ content). I 
can see that there has been a Bacula Plugin maintained by iX-Systems for 
FreeNAS in the past, but it has been abandoned by iX-Systems.

Since TrueNAS Core is the closest we get for free to something like an 
enterprise storage appliance, I was assuming it makes a lot of sense and there 
is a lot of demand to have Bacula for TrueNAS Core. I haven’t found it in the 
Community Plugins either.

I saw that someone on this list was compiling Bacula for TrueNAS Core, so it 
must be feasible.

Are just too few people here using TrueNAS Core? Or has everyone gone through 
compiling it for themselves? Wouldn’t it be more  “user-friendly” to have a 
plugin? Maybe no-one has sufficient motivation to make and maintain one (yeah, 
I know someone is going to respond “why don’t you do it?”). 
Or is there another explanation?

Or is there actually a Bacula Plugin for TrueNAS Core and I just did not look 
right and did not find it?

All the best, I am looking forward to your thoughts on this.
 J/C

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