Good morning mates,
Apologies for my very very late response….
Just one question for confirming, in Josh’s third point, when sais :
> Level 3:
> # This level requires encryption and that the certificate presented by
> the peer be signed by a trusted CA
It means a CA in CA certificate
Hello,
To be honest I'm not sure what you want to achieve, but you can verify a
job logs with bconsole command: list joblog jobid=. It require a
message with catalog=all to populate a log table in catalog.
I hope it help.
best regards
2015-10-01 16:06 GMT+02:00 Michael Schwager
Dear bacula users,
I recently upgraded from 5.1.3 to 7.2.0.
Runs like a charm except for one thing:
We do copy jobs every morning to copy the disk backups to tape. Every copy job
sends a mail reporting "Backup OK of clientname incremental". Never had this in
5.1.3.
My message ressources are:
On 10/2/2015 2:47 AM, Egoitz Aurrekoetxea wrote:
Good morning mates,
Apologies for my very very late response….
Just one question for confirming, in Josh’s third point, when sais :
Level 3:
# This level requires encryption and that the certificate
presented by the peer be
Hello Christoph,
How is your job copy "messages" directive defined? It seems it is
configured as "messages = Standard". Could you check if the text of this
e-mail appears in /var/log/bacula/bacula.log or /var/log/bacula/copy.log?
Best regards,
Ana
On Fri, Oct 2, 2015 at 9:22 AM, Christoph
Hi,
In the config file for a file storage device, randomaccess should be set
to "yes". But what if nothing is explicitly mentioned ? What is the
default in bacula ?
I use multiplexing on file storage to backup servers to bacula and
experience very bad performance to copy backup stored on disk
All,
I believe I'm having mysql database issues since upgrading to 7.2 (from
7.0.2). I run mysql innodb with 900Gb database that's largely the File
table.
Since upgrading, I lose a few jobs a night due to database locking
timeouts, which I have set to 3600. I also log slow queries.
It
On 10/02/2015 04:54 PM, Thomas Eriksson wrote:
> Hi,
>
> I updated my director from 7.0.5 to 7.2.0 on a CentOS 7 box, using
> Simone's COPR repository. I ran the database update script and have
> successfully run some backups after the upgrade.
>
> However, the catalog backup (using the
Hi,
I updated my director from 7.0.5 to 7.2.0 on a CentOS 7 box, using
Simone's COPR repository. I ran the database update script and have
successfully run some backups after the upgrade.
However, the catalog backup (using the make_catalog_backup.pl script)
fails with the following error:
