On 2020-05-14 14:29, Alan Brown wrote:
>
> As we all know, Bacula's File table grows to stupidly large sizes.
>
> Postgresql has the ability to partition large tables to make management
> easier, either manually or with pg_partman
>
>
> https://www.postgresql.org/docs/12/ddl-partitioning.html
>
As we all know, Bacula's File table grows to stupidly large sizes.
Postgresql has the ability to partition large tables to make management
easier, either manually or with pg_partman
https://www.postgresql.org/docs/12/ddl-partitioning.html
https://www.postgresql.org/about/news/1964/
https://g
Hi Martin,
I installed Bacula through the Ubuntu repository provided by Bacula:
deb http://bacula.org/packages//debs/9.6.3/bionic/amd64 bionic main
Other than building bacula myself or waiting for a new release there is
probably not much that I can do, right?
Met vriendelijke groet / With kind
Hi Martin,
Thanks for your help, I will contact them
Met vriendelijke groet / With kind regards,
Rick
> On May 14, 2020, at 6:48 PM, Martin Simmons wrote:
>
> Yes, there is no workaround. I suggest you contact Bacula Systems about it,
> becasue they might not know about the problem.
>
> __M
> On Thu, 14 May 2020 12:11:10 +0200, Radosław Korzeniewski said:
>
> It misses the most important part of the traceback - the debugger
> backtrace. :)
>
> /etc/bacula/scripts/btraceback.gdb:1: Error in sourced command file:
> > 'fail_time' has unknown type; cast it to its declared type
This
Yes, it will work if they have the same Archive Device. That is the expected
configuration.
An autochanger with more than one device allows you to use more than one
volume at a time. E.g. for simultaneous backups of different clients or to
use Copy or Migrate jobs.
__Martin
> On Thu, 14 M
Yes, there is no workaround. I suggest you contact Bacula Systems about it,
becasue they might not know about the problem.
__Martin
> On Thu, 14 May 2020 16:38:06 +, Rick Tuk said:
> Hi Martin,
>
> I installed Bacula through the Ubuntu repository provided by Bacula:
>
> deb http://ba
OK, so your bacula-sd-cloud-driver-9.6.3.so is built without S3 support for
some reason (there should be many lines mentioning s3_driver). The output of
objdump is also strangely mangled, because all of the references to fil_driver
should be file_driver.
It looks like libs3 was not detected when
Problem solved. FQDN needed in bconsole.conf
On Thu, May 14, 2020 at 8:55 AM Radosław Korzeniewski <
rados...@korzeniewski.net> wrote:
> Hello,
>
> First of all, you should respond to the list and not to me directly,
> please.
>
> czw., 14 maj 2020 o 15:30 Jeff Thomas napisał(a):
>
>> The dire
Hello,
czw., 14 maj 2020 o 13:57 Jeff Thomas napisał(a):
> Thanks. I can connect to the database manually without issue.
>
> sudo -u bacula psql bacula
> psql (9.2.24)
> Type "help" for help.
>
> bacula=>
>
>
Above you are using 'bacula' system user to connect to catalog
database with using uni
Hi Martin,
The Plugin Directory is /opt/bacula/plugins:
Storage {
Name = soteria-sd
SD Address = soteria.local.domain
SD Port = 9103
Maximum Concurrent Jobs = 20
Working Directory = /opt/bacula/working
Pid Directory = /opt/bacula/working
Plugin Directory = "/opt/bac
Is this still loading the driver from
/usr/lib64/bacula-sd-cloud-driver-9.6.3.so? It is a little strange that you
have bacula in /opt/bacula/bin/bacula-sd but the plugins are in /usr/lib64.
Please also post the output from:
objdump -t /usr/lib64/bacula-sd-cloud-driver-9.6.3.so | grep _driver
Do
# Generic catalog service
Catalog {
Name = MyCatalog
dbname = "bacula"; dbuser = "bacula"; dbpassword = ""
}
On Thu, May 14, 2020 at 8:55 AM Radosław Korzeniewski <
rados...@korzeniewski.net> wrote:
> Hello,
>
> First of all, you should respond to the list and not to me directly,
> please.
Hello,
First of all, you should respond to the list and not to me directly, please.
czw., 14 maj 2020 o 15:30 Jeff Thomas napisał(a):
> The director is running as 'bacula'
>
> bacula 27410 1 0 May13 ?00:00:00 /opt/bacula/bin/bacula-sd
> -fP -c /opt/bacula/etc/bacula-sd.conf
> roo
It looks to me like S3 support is missing.
What is the PluginDirectory in your bacula-sd.conf?
Find the bacula-sd-cloud-driver-9.6.3.so in that directory and post the output
of:
objdump -t /...path.../...to.../bacula-sd-cloud-driver-9.6.3.so | grep _driver
__Martin
> On Thu, 14 May 2020 0
Hello,
śr., 13 maj 2020 o 19:19 Jeff Thomas napisał(a):
> Greetings all,
>
> I would greatly appreciate some pointers to resolve this issue. I
> installed using the Community Installation Guide with:
>
> Centos 7, Bacula 9.6.3 and Postgresql 9.2
>
> The bconsole command returns to the shell i
Hello,
I'm completely a newbie with Bacula: I'm studying all the guides and just
few days ago I've been able to us it! Success!
But I still cannot understand how the virtual autochangers work:
I touched very little from the default config and I just created for
different network shares and mounted
Hello,
czw., 14 maj 2020 o 08:50 Phillip Dale
napisał(a):
> I could not get much information out of that traceback. Hopefully this
> helps, so here is the traceback file I got:
>
It is an almost perfect traceback. :)
> Thread 3 (Thread 0x7feb38fe4700 (LWP 19470)):
> #0 0x7feb41e201d9 in
Hello,
czw., 14 maj 2020 o 08:38 Chaz Vidal napisał(a):
> Hi All
> I got a segmentation violation again whilst attempting a restore operation
> while a number of backups were still occurring.
>
> This time the traceback was created and also an email was generated.
>
>
It seems your traceback is
On 14/05/2020 16:19, Chaz Vidal wrote:
Hi All
I got a segmentation violation again whilst attempting a restore operation
while a number of backups were still occurring.
Call me old-fashioned, but I wouldn't do this.
Bacula started life when all we had was a single tape-drive, on which we
phy
20 matches
Mail list logo