I want to use concurrent jobs for backing up slow roaming clients during the
day with spool directories. This works fine. They take a long time, but they
each write to their own spool.
My challange is we have on disk volumes and a single tape drive where jobs are
copied to over time.
When a
Hi,
I'm sorry to bother you, but I'm having troubles restoring a NDMP
backup and the error is driving me crazy.
Im currently using bareos 18.2.5 and bareos-webui.
I also have a netapp AFF-A220 storage properly configured to support NDMP.
I configured NDMP client in bareos and tested it s
did you try
psql -h 192.168.1.126 -U bareos bareos -p 5432
to check if your credentials correct to access bareos DB?
On Mon, Dec 2, 2019 at 5:03 PM DUCARROZ Birgit
wrote:
> Hi,
>
> Thank you for responding again.
> ok I added dbaddress and dport but it does not work. Same error if
> trying
Hi,
Thank you for responding again.
ok I added dbaddress and dport but it does not work. Same error if
trying just as root user:
Catalog {
Name = MyCatalog
#dbdriver = ""
dbdriver = postgresql
dbname = bareos
dbaddress = 192.168.1.126
dbport = 5432
dbuser = bareos
dbpassword =
Hi, Birgit
as I said before, it's because you missed dbaddress part in your MyCatalog
config.
(so bareos-dir -t -u bareos works, but bareos-dir -t doesn't work)
If you add dbaddress to MyCatalog.conf, both forms (with and without -u
bareos) will not work đŸ˜€
So, I recommend to add dbaddress to cat
Hi,
Yes, that's it:
The problem comes from the fact that I run bareos-dir -t as root user
and that the bareos user has no problem to connect but the root user has.
bareos-dir -u bareos -t works.
Thank you a lot!!
Kind regards,
Birgit
Heya,
just an idea ...
On Mon, Dec 02, 2019 at 02:36:
Heya,
just an idea ...
On Mon, Dec 02, 2019 at 02:36:23PM +0100, 'DUCARROZ Birgit' via bareos-users
wrote:
> root@diufnas26:/etc/bareos# bareos-dir -u bareos -t --> no error
> root@diufnas26:/etc/bareos# bareos-dir -t
>
> --> Error:
> "
> bareos-dir: dird/dird.cc:927-0 Could not open Catalog
Hi,
Thank you for your answer. So according your last post I think I can
ignore this error. Here some details:
Yes, no probles and no error message after
systemctl stop bareos-dir bareos-sd bareos-fd
systemctl stop bareos-dir bareos-sd bareos-fd
root@diufnas26:/etc/bareos# bareos-dir -u bar
