Hello,
the problem was really easy to fix but the messages has been sent me
to a complete different not really relevant and helpfull way:
On server I use @tls.conf file line to load the certificates files.
On client these is directly configured two times instead of only
one time I found. So I
We have started building our Bacula server, and after some month of adding
SD, FD, Pools and Media we have found that our naming convention was too
dumb.
There's some way to rename all this stuff? Or better to redefine all,
relabel the media and then clanup the DB manually via SQL?
Thanks.
--
Hello,
pon., 23 sty 2023 o 15:23 Robin Schröter napisał(a):
> Hello,
>
> I have two questions.
>
> 1.
>
> I have two different Ubunut 20.04 systems.
> One runs bacula 9.4.2 Storage daemon and the other runs bacula 9.4.2
> director.
> I instaled this through ubuntu apt install.
> Now I want to up
Hello,
I have two questions.
1.
I have two different Ubunut 20.04 systems.
One runs bacula 9.4.2 Storage daemon and the other runs bacula 9.4.2
director.
I instaled this through ubuntu apt install.
Now I want to update the bacula version to 13.0.x. Is an inplace update
from Bacula 9.4.2 to 1
Am 23.01.23 um 13:31 schrieb Pierre Bernhardt:
My self signed root ca and my certs has to been outdated.
So I created a new ca key, self segned ca cert and new
certs for bacula director and all clients.
...
I only replaced the tls certs and installed a new ca cert.
I double checked the inst
My self signed root ca and my certs has to been outdated.
So I created a new ca key, self segned ca cert and new
certs for bacula director and all clients.
The issue is that the message appears so i cerated a
new ca cert so the
basicConstraints = CA:true
also contains the ca cert
So I i
