[Bacula-users] Failed to connect to Client -fd
Hi,
I've installed and configured the free Bacula version 5.2.13, but I'm not
able to establish the connection with remote client the local backup works
fine. IP and port has been allowed in the firewall and telnet in both
machines works fine. All the configurations are done as per the document:
https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
- OS: CentOS Linux release 7.6.1810 (Core)
- Bacula Version: 5.2.13
=
[root@baculaserver ~]# bconsole
Connecting to Director localhost:9101
1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
Enter a period to cancel a command.
*status client
The defined Client resources are:
1: bacula-fd
2: client1.hostname-fd
3: client2.hostname-fd
Select Client (File daemon) resource (1-3): 2
Connecting to Client client1.hostname-fd at client1.hostname:9102
Failed to connect to Client client1.hostname-fd.
You have messages.
=
# tail -f /var/log/bacula/bacula.log
28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
28-Apr 23:10 bacula-dir JobId 71: End auto prune.
28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
"/usr/libexec/bacula/delete_catalog_backup"
29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to authenticate with
File daemon at "client1.hostname:9102". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
for help.
=
# vi /etc/bacula/conf.d/clients.conf
Client {
Name = client1.hostname-fd
Address = client1.hostname
FDPort = 9102
Catalog = MyCatalog
Password = "mypassword" # password for Remote FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
Job {
Name = "Backupclient1.hostname"
JobDefs = "DefaultJob"
Client = client1.hostname-fd
Pool = RemoteFile
FileSet="Home and Etc"
}
=
# cat /etc/bacula/bacula-fd.conf
Director {
Name = servername-dir
Password = "mypassword"
}
Director {
Name = bacula-mon
Password = "mypassword"
Monitor = yes
}
FileDaemon { # this is me
Name = client1.hostname-fd
FDAddress =
FDport = 9102 # where we listen for the director
WorkingDirectory = /var/spool/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = servername-dir = all, !skipped, !restored
}
=
kindly update me any solution for this, let me know if you require any
further details.
Regards,
Preash.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Failed to connect to Client -fd
Hi Martin, >> You could try running the director and remote client with debug level 100 to print more information (add the command line arguments -f -d 100). Could you please let me know the exact full command for a debug run? On Tue, Apr 30, 2019 at 6:42 PM preash raj wrote: > Sure! will do. > > On Tue, Apr 30, 2019 at 6:39 PM Martin Simmons > wrote: > >> Please CC bacula-users with replies. >> >> __Martin >> >> >> >>>>> On Tue, 30 Apr 2019 18:35:38 +0530, preash raj said: >> > >> > Hi Martin, >> > >> > thank you for the quick response! the bacula client version is 5.0.0, >> I'll >> > try to debug as you specified and will update you soon. >> > >> > Regards, >> > Preash >> > >> > >> > On Tue, Apr 30, 2019 at 5:41 PM Martin Simmons >> wrote: >> > >> > > >>>>> On Tue, 30 Apr 2019 11:16:25 +0530, preash raj said: >> > > > >> > > > Hi, >> > > > >> > > > I've installed and configured the free Bacula version 5.2.13, but >> I'm not >> > > > able to establish the connection with remote client the local backup >> > > works >> > > > fine. IP and port has been allowed in the firewall and telnet in >> both >> > > > machines works fine. All the configurations are done as per the >> document: >> > > > >> > > >> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7 >> > > > >> > > >- OS: CentOS Linux release 7.6.1810 (Core) >> > > >- Bacula Version: 5.2.13 >> > > > >> > > > = >> > > > >> > > > [root@baculaserver ~]# bconsole >> > > > Connecting to Director localhost:9101 >> > > > 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013) >> > > > Enter a period to cancel a command. >> > > > *status client >> > > > The defined Client resources are: >> > > > 1: bacula-fd >> > > > 2: client1.hostname-fd >> > > > 3: client2.hostname-fd >> > > > Select Client (File daemon) resource (1-3): 2 >> > > > Connecting to Client client1.hostname-fd at client1.hostname:9102 >> > > > Failed to connect to Client client1.hostname-fd. >> > > > >> > > > You have messages. >> > > > = >> > > > >> > > > # tail -f /var/log/bacula/bacula.log >> > > > >> > > > 28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files. >> > > > 28-Apr 23:10 bacula-dir JobId 71: No Files found to prune. >> > > > 28-Apr 23:10 bacula-dir JobId 71: End auto prune. >> > > > >> > > > 28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob >> > > > "/usr/libexec/bacula/delete_catalog_backup" >> > > > 29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to >> authenticate with >> > > > File daemon at "client1.hostname:9102". Possible causes: >> > > > Passwords or names not the same or >> > > > Maximum Concurrent Jobs exceeded on the FD or >> > > > FD networking messed up (restart daemon). >> > > > Please see >> > > > >> > > >> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 >> > > > for help. >> > > >> > > Is the remote client also running Bacula version 5.2.13? If not, >> which >> > > version? >> > > >> > > You could try running the director and remote client with debug level >> 100 >> > > to >> > > print more information (add the command line arguments -f -d 100). >> > > >> > > __Martin >> > > >> > >> > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Failed to connect to Client -fd
Hi, I've tried running the Bacula in debug mode and got the below results; I've checked with the DB and make sure the passwords are correct. Can you guys please guide me through this. The bacula files are located under /etc/bacula = [root@bacula]# bacula-dir -f -d 100 bacula-dir: dird.c:223-0 Debug level = 100 01-May 08:12 bacula-dir: ERROR TERMINATION at bsys.c:484 bacula-dir is already running. pid=571 Check file /var/run/bacula-dir.9101.pid [root@bacula]# bacula-sd -f -d 100 bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon 01-May 08:12 bacula-sd: ERROR TERMINATION at bsys.c:484 bacula-sd is already running. pid=32149 Check file /var/run/bacula-sd.9103.pid [root@bacula]# bacula-fd -f -d 100 bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon 01-May 08:12 bacula-fd: ERROR TERMINATION at bsys.c:484 bacula-fd is already running. pid=32119 Check file /var/run/bacula-fd.9102.pid = On Wed, May 1, 2019 at 3:43 AM Dimitri Maziuk via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > On 4/30/19 11:42 AM, William Muriithi wrote: > > Heitor, > > > > He is using Centos, and version 5.2.13 ended up being whats shipped by > RedHat. Very understandable > > > > Do you know why RedHat does ship something newer? Like even version 7? > > RedHat gets paid for supporting their customers. Presumably they have > reasons for not supporting newer bacula versions. At least 5.2.13 is > still in base, there have been several instances where they dropped > software supported by other commercial entities altogether. DRBD, for > example. > > Of course on centos you needn't care about RH support terms so you may > as well install from upstream repo. > > -- > Dimitri Maziuk > Programmer/sysadmin > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > ___ > 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] Failed to connect to Client -fd
Hi Guys, I've tried debugging after stopping the services, please check the server and client results below. Any clue? Bacula Server: = [root@bacula ~]# bacula-dir -f -d 100 bacula-dir: dird.c:223-0 Debug level = 100 bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 bacula-dir: jcr.c:147-0 Read num_items=10 bacula-dir: dir_plugins.c:160-0 Load dir plugins bacula-dir: dir_plugins.c:162-0 No dir plugin dir! bacula-dir: mysql.c:709-0 db_init_database first time bacula-dir: mysql.c:177-0 mysql_init done bacula-dir: mysql.c:202-0 mysql_real_connect done bacula-dir: mysql.c:204-0 db_user=bacula db_name=bacula db_password=admin@123 bacula-dir: mysql.c:227-0 opendb ref=1 connected=1 db=5578f76a53a0 bacula-dir: mysql.c:249-0 closedb ref=0 connected=1 db=5578f76a53a0 bacula-dir: mysql.c:256-0 close db=5578f76a53a0 bacula-dir: dird.c:1215-0 Unlink: /var/spool/bacula/bacula-dir.bacula-dir.1653251192.mail bacula-dir: pythonlib.c:102-0 No script dir. prog=DirStartUp bacula-dir: bnet_server.c:112-0 Addresses host[ipv4:127.0.0.1:9101] bacula-dir: job.c:1334-0 wstorage=File bacula-dir: job.c:1343-0 wstore=File where=Job resource bacula-dir: job.c:1034-0 JobId=0 created Job=*JobMonitor*.2019-05-02_01.37.47_01 [root@bacula ~]# bacula-sd -f -d 100 bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon bacula-sd: jcr.c:140-0 read_last_jobs seek to 192 bacula-sd: jcr.c:147-0 Read num_items=10 bacula-sd: stored.c:564-0 calling init_dev /bacula/backup bacula-sd: bnet_server.c:112-0 Addresses host[ipv4::9103] bacula-sd: dev.c:318-0 init_dev: tape=0 dev_name=/bacula/backup bacula-sd: stored.c:566-0 SD init done /bacula/backup [root@bacula ~]# bacula-fd -f -d 100 bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon bacula-fd: jcr.c:140-0 read_last_jobs seek to 192 bacula-fd: jcr.c:147-0 Read num_items=10 bacula-fd: pythonlib.c:102-0 No script dir. prog=FDStartUp bacula-fd: filed.c:276-0 filed: listening on port 9102 bacula-fd: bnet_server.c:112-0 Addresses host[ipv4:0.0.0.0:9102] Bacula Client: = root@client [~]# bacula-fd -f -d 100 bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon staff.hostdime.in-fd: jcr.c:140-0 read_last_jobs seek to 192 staff.hostdime.in-fd: jcr.c:147-0 Read num_items=0 staff.hostdime.in-fd: pythonlib.c:104-0 No script dir. prog=FDStartUp staff.hostdime.in-fd: filed.c:275-0 filed: listening on port 9102 staff.hostdime.in-fd: bnet_server.c:96-0 Addresses host[ipv4: 103.13.242.170:9102] On Wed, May 1, 2019 at 7:43 PM Martin Simmons wrote: > The output says: "bacula-dir is already running" -- you need to stop the > existing process first. > > __Martin > > > >>>>> On Wed, 1 May 2019 17:44:53 +0530, preash raj said: > > > > Hi, > > > > I've tried running the Bacula in debug mode and got the below results; > I've > > checked with the DB and make sure the passwords are correct. Can you guys > > please guide me through this. > > The bacula files are located under /etc/bacula > > = > > [root@bacula]# bacula-dir -f -d 100 > > bacula-dir: dird.c:223-0 Debug level = 100 > > 01-May 08:12 bacula-dir: ERROR TERMINATION at bsys.c:484 > > bacula-dir is already running. pid=571 > > Check file /var/run/bacula-dir.9101.pid > > > > [root@bacula]# bacula-sd -f -d 100 > > bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon > > 01-May 08:12 bacula-sd: ERROR TERMINATION at bsys.c:484 > > bacula-sd is already running. pid=32149 > > Check file /var/run/bacula-sd.9103.pid > > > > [root@bacula]# bacula-fd -f -d 100 > > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > > 01-May 08:12 bacula-fd: ERROR TERMINATION at bsys.c:484 > > bacula-fd is already running. pid=32119 > > Check file /var/run/bacula-fd.9102.pid > > = > > > > On Wed, May 1, 2019 at 3:43 AM Dimitri Maziuk via Bacula-users < > > bacula-users@lists.sourceforge.net> wrote: > > > > > On 4/30/19 11:42 AM, William Muriithi wrote: > > > > Heitor, > > > > > > > > He is using Centos, and version 5.2.13 ended up being whats shipped > by > > > RedHat. Very understandable > > > > > > > > Do you know why RedHat does ship something newer? Like even version > 7? > > > > > > RedHat gets paid for supporting their customers. Presumably they have > > > reasons for not supporting newer bacula versions. At least 5.2.13 is > > > still in base, there have been several instances where they dropped > > > software supported by other commercial entities altogether. DRBD, for > > > example. >
Re: [Bacula-users] Failed to connect to Client -fd
I've also tried debbuging bconsole too; please find the result attached. # bconsole -d 100 -dt Connecting to Director localhost:9101 02-May-2019 05:30:42 bconsole: bsock.c:236-0 Current host[ipv6:::1:9101] All host[ipv6:::1:9101] host[ipv4:127.0.0.1:65535] 02-May-2019 05:30:42 bconsole: bsock.c:236-0 Current host[ipv4: 127.0.0.1:9101] All host[ipv6:::1:9101] host[ipv4:127.0.0.1:9101] 02-May-2019 05:30:42 bconsole: bsock.c:157-0 who=Director daemon host=localhost port=9101 02-May-2019 05:30:42 bconsole: cram-md5.c:131-0 cram-get received: auth cram-md5 <282828203.1556789442@bacula-dir> ssl=0 02-May-2019 05:30:42 bconsole: cram-md5.c:150-0 sending resp to challenge: QT/fB9/mn9woD+IqY5+XlD 02-May-2019 05:30:42 bconsole: cram-md5.c:79-0 send: auth cram-md5 <1502355591.1556789442@bconsole> ssl=0 02-May-2019 05:30:42 bconsole: cram-md5.c:98-0 Authenticate OK yw+DUAdzxH/MeD9/58+PXB 02-May-2019 05:30:42 bconsole: authenticate.c:150-0 >dird: 1000 OK auth 02-May-2019 05:30:42 bconsole: authenticate.c:157-0 -fd 3: -fd Select Client (File daemon) resource (1-3): 02-May-2019 05:30:48 bconsole: console.c:329-0 Got poll BNET_SUB_PROMPT 2 Connecting to Client -fd at :9102 Failed to connect to Client -fd. You have messages. 02-May-2019 05:31:12 bconsole: console.c:329-0 Got poll BNET_EOD # bconsole Connecting to Director localhost:9101 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013) Enter a period to cancel a command. *setdebug level=100 All Connecting to Storage daemon File at :9103 3000 OK setdebug=100 Connecting to Client bacula-fd at localhost:9102 2000 OK setdebug=100 trace=0 hangup=0 Connecting to Client -fd at :9102 Failed to connect to Client. Connecting to Client -fd at :9102 Failed to connect to Client. On Thu, May 2, 2019 at 11:15 AM preash raj wrote: > Hi Guys, > > I've tried debugging after stopping the services, please check the server > and client results below. Any clue? > > > Bacula Server: > = > [root@bacula ~]# bacula-dir -f -d 100 > bacula-dir: dird.c:223-0 Debug level = 100 > bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 > bacula-dir: jcr.c:147-0 Read num_items=10 > bacula-dir: dir_plugins.c:160-0 Load dir plugins > bacula-dir: dir_plugins.c:162-0 No dir plugin dir! > bacula-dir: mysql.c:709-0 db_init_database first time > bacula-dir: mysql.c:177-0 mysql_init done > bacula-dir: mysql.c:202-0 mysql_real_connect done > bacula-dir: mysql.c:204-0 db_user=bacula db_name=bacula > db_password=admin@123 > bacula-dir: mysql.c:227-0 opendb ref=1 connected=1 db=5578f76a53a0 > bacula-dir: mysql.c:249-0 closedb ref=0 connected=1 db=5578f76a53a0 > bacula-dir: mysql.c:256-0 close db=5578f76a53a0 > bacula-dir: dird.c:1215-0 Unlink: > /var/spool/bacula/bacula-dir.bacula-dir.1653251192.mail > bacula-dir: pythonlib.c:102-0 No script dir. prog=DirStartUp > bacula-dir: bnet_server.c:112-0 Addresses host[ipv4:127.0.0.1:9101] > bacula-dir: job.c:1334-0 wstorage=File > bacula-dir: job.c:1343-0 wstore=File where=Job resource > bacula-dir: job.c:1034-0 JobId=0 created > Job=*JobMonitor*.2019-05-02_01.37.47_01 > > [root@bacula ~]# bacula-sd -f -d 100 > bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon > bacula-sd: jcr.c:140-0 read_last_jobs seek to 192 > bacula-sd: jcr.c:147-0 Read num_items=10 > bacula-sd: stored.c:564-0 calling init_dev /bacula/backup > bacula-sd: bnet_server.c:112-0 Addresses host[ipv4::9103] > bacula-sd: dev.c:318-0 init_dev: tape=0 dev_name=/bacula/backup > bacula-sd: stored.c:566-0 SD init done /bacula/backup > > [root@bacula ~]# bacula-fd -f -d 100 > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > bacula-fd: jcr.c:140-0 read_last_jobs seek to 192 > bacula-fd: jcr.c:147-0 Read num_items=10 > bacula-fd: pythonlib.c:102-0 No script dir. prog=FDStartUp > bacula-fd: filed.c:276-0 filed: listening on port 9102 > bacula-fd: bnet_server.c:112-0 Addresses host[ipv4:0.0.0.0:9102] > > > Bacula Client: > = > root@client [~]# bacula-fd -f -d 100 > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > staff.hostdime.in-fd: jcr.c:140-0 read_last_jobs seek to 192 > staff.hostdime.in-fd: jcr.c:147-0 Read num_items=0 > staff.hostdime.in-fd: pythonlib.c:104-0 No script dir. prog=FDStartUp > staff.hostdime.in-fd: filed.c:275-0 filed: listening on port 9102 > staff.hostdime.in-fd: bnet_server.c:96-0 Addresses host[ipv4: > 103.13.242.170:9102] > > > On Wed, May 1, 2019 at 7:43 PM Martin Simmons > wrote: > >> The output says: "bacula-dir is already running" -- you need to stop the >> existing process first. >> >> __Martin >> >> >> >>>>> On Wed, 1 May 2019 17:44:53 +0530, preash raj said: >> > >> > Hi, >> > >> &g
Re: [Bacula-users] Failed to connect to Client -fd
Hi Martin, >> while the bacula-dir and the remote bacula-fd were running with these command line args? You mean starting the bacula-dir in debug mode while I check the 'status client' in bconsole? It shows the below error while try to connect the clients using bconsole. the passwords looks fine, Please let me know if you have any clue on this. == Server: bacula-dir = bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=9101 bacula-dir: job.c:1334-0 wstorage=File bacula-dir: job.c:1343-0 wstore=File where=Job resource bacula-dir: job.c:1034-0 JobId=0 created Job=-Console-.2019-05-03_04.51.02_02 bacula-dir: cram-md5.c:72-0 send: auth cram-md5 <1917691640.1556873462@bacula-dir> ssl=0 bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5 <1594513444.1556873462@bconsole> ssl=0 bacula-dir: cram-md5.c:150-0 sending resp to challenge: s5xs1Ct7B+/C/R+/d7+hcB bacula-dir: ua_status.c:142-0 status:status client: bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All host[ipv4:103.13.242.170:9102] bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd host= staff.hostdime.in port=9102 bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100 Connection from unknown Director bacula-dir at 109.73.166.242 rejected. bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100 Connection from unknown Director bacula-dir at 109.73.166.242 rejected. bacula-dir: authenticate.c:218-0 cram_get_auth failed for Client: staff.hostdime.in-fd bacula-dir: authenticate.c:222-0 Director and File daemon passwords or names not the same. bacula-dir: bsys.c:79-0 safe_unlink unlinking: /var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail == On Fri, May 3, 2019 at 12:17 AM Martin Simmons wrote: > Did you run the failing bconsole command while the bacula-dir and the > remote > bacula-fd were running with these command line args? That should make it > print more debug information for both of them. > > __Martin > > > >>>>> On Thu, 2 May 2019 11:15:16 +0530, preash raj said: > > > > Hi Guys, > > > > I've tried debugging after stopping the services, please check the server > > and client results below. Any clue? > > > > > > Bacula Server: > > = > > [root@bacula ~]# bacula-dir -f -d 100 > > bacula-dir: dird.c:223-0 Debug level = 100 > > bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 > > bacula-dir: jcr.c:147-0 Read num_items=10 > > bacula-dir: dir_plugins.c:160-0 Load dir plugins > > bacula-dir: dir_plugins.c:162-0 No dir plugin dir! > > bacula-dir: mysql.c:709-0 db_init_database first time > > bacula-dir: mysql.c:177-0 mysql_init done > > bacula-dir: mysql.c:202-0 mysql_real_connect done > > bacula-dir: mysql.c:204-0 db_user=bacula db_name=bacula > > db_password=admin@123 > > bacula-dir: mysql.c:227-0 opendb ref=1 connected=1 db=5578f76a53a0 > > bacula-dir: mysql.c:249-0 closedb ref=0 connected=1 db=5578f76a53a0 > > bacula-dir: mysql.c:256-0 close db=5578f76a53a0 > > bacula-dir: dird.c:1215-0 Unlink: > > /var/spool/bacula/bacula-dir.bacula-dir.1653251192.mail > > bacula-dir: pythonlib.c:102-0 No script dir. prog=DirStartUp > > bacula-dir: bnet_server.c:112-0 Addresses host[ipv4:127.0.0.1:9101] > > bacula-dir: job.c:1334-0 wstorage=File > > bacula-dir: job.c:1343-0 wstore=File where=Job resource > > bacula-dir: job.c:1034-0 JobId=0 created > > Job=*JobMonitor*.2019-05-02_01.37.47_01 > > > > [root@bacula ~]# bacula-sd -f -d 100 > > bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon > > bacula-sd: jcr.c:140-0 read_last_jobs seek to 192 > > bacula-sd: jcr.c:147-0 Read num_items=10 > > bacula-sd: stored.c:564-0 calling init_dev /bacula/backup > > bacula-sd: bnet_server.c:112-0 Addresses host[ipv4::9103] > > bacula-sd: dev.c:318-0 init_dev: tape=0 dev_name=/bacula/backup > > bacula-sd: stored.c:566-0 SD init done /bacula/backup > > > > [root@bacula ~]# bacula-fd -f -d 100 > > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > > bacula-fd: jcr.c:140-0 read_last_jobs seek to 192 > > bacula-fd: jcr.c:147-0 Read num_items=10 > > bacula-fd: pythonlib.c:102-0 No script dir. prog=FDStartUp > > bacula-fd: filed.c:276-0 filed: listening on port 9102 > > bacula-fd: bnet_server.c:112-0 Addresses host[ipv4:0.0.0.0:9102] > > > > > > Bacula Client: > > = > > root@client [~]# bacula-fd -f -d 100 > > bacula-fd: filed_co
Re: [Bacula-users] Failed to connect to Client -fd
Hi Martin, Thank you for pointing this out; it's fixed now, excellent! Just a heads up, can we create a snapshot backup in Bacula? let me know if that works even in a upgraded version. On Fri, May 3, 2019 at 10:04 PM Martin Simmons wrote: > Yes, that's what I meant. > > It shows an error from the remote fd: > > Connection from unknown Director bacula-dir at 109.73.166.242 rejected. > > It looks like the Director > Name in the bacula-fd.conf on the remote fd > does > not match the Director > Name in the bacula-dir.conf. > > __Martin > > > >>>>> On Fri, 3 May 2019 17:20:34 +0530, preash raj said: > > > > Hi Martin, > > > > >> while the bacula-dir and the remote > > bacula-fd were running with these command line args? > > > > You mean starting the bacula-dir in debug mode while I check the 'status > > client' in bconsole? > > It shows the below error while try to connect the clients using bconsole. > > the passwords looks fine, Please let me know if you have any clue on > this. > > > > == > > Server: bacula-dir > > = > > bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=9101 > > bacula-dir: job.c:1334-0 wstorage=File > > bacula-dir: job.c:1343-0 wstore=File where=Job resource > > bacula-dir: job.c:1034-0 JobId=0 created > Job=-Console-.2019-05-03_04.51.02_02 > > bacula-dir: cram-md5.c:72-0 send: auth cram-md5 > <1917691640.1556873462@bacula-dir> ssl=0 > > bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5 > <1594513444.1556873462@bconsole> ssl=0 > > bacula-dir: cram-md5.c:150-0 sending resp to challenge: > s5xs1Ct7B+/C/R+/d7+hcB > > bacula-dir: ua_status.c:142-0 status:status client: > > bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All > host[ipv4:103.13.242.170:9102] > > bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd host= > staff.hostdime.in port=9102 > > bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon > > bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling > > bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100 > Connection from unknown Director bacula-dir at 109.73.166.242 rejected. > > bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100 > Connection from unknown Director bacula-dir at 109.73.166.242 rejected. > > bacula-dir: authenticate.c:218-0 cram_get_auth failed for > Client:staff.hostdime.in-fd > > bacula-dir: authenticate.c:222-0 Director and File daemon passwords or > names not the same. > > bacula-dir: bsys.c:79-0 safe_unlink unlinking: > /var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail > > > > == > > > > > > > > On Fri, May 3, 2019 at 12:17 AM Martin Simmons > wrote: > > > > > Did you run the failing bconsole command while the bacula-dir and the > > > remote > > > bacula-fd were running with these command line args? That should make > it > > > print more debug information for both of them. > > > > > > __Martin > > > > > > > > > >>>>> On Thu, 2 May 2019 11:15:16 +0530, preash raj said: > > > > > > > > Hi Guys, > > > > > > > > I've tried debugging after stopping the services, please check the > server > > > > and client results below. Any clue? > > > > > > > > > > > > Bacula Server: > > > > = > > > > [root@bacula ~]# bacula-dir -f -d 100 > > > > bacula-dir: dird.c:223-0 Debug level = 100 > > > > bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 > > > > bacula-dir: jcr.c:147-0 Read num_items=10 > > > > bacula-dir: dir_plugins.c:160-0 Load dir plugins > > > > bacula-dir: dir_plugins.c:162-0 No dir plugin dir! > > > > bacula-dir: mysql.c:709-0 db_init_database first time > > > > bacula-dir: mysql.c:177-0 mysql_init done > > > > bacula-dir: mysql.c:202-0 mysql_real_connect done > > > > bacula-dir: mysql.c:204-0 db_user=bacula db_name=bacula > > > > db_password=admin@123 > > > > bacula-dir: mysql.c:227-0 opendb ref=1 connected=1 db=5578f76a53a0 > > > > bacula-dir: mysql.c:249-0 closedb ref=0 connected=1 db=5578f76a53a0 > > > > bacula-dir: mysql.c:256-0 close db=5578f76a53a0 > > > > bacula-dir: dird.c:1215-0 Unlink: > > > > /var/spool/bacula/bacula-dir.bacula-dir.1653251192.mail > > >
[Bacula-users] How to upgrade Bacula 5.2.13 to 7.2
Hello Guys, How do I upgrade Bacula 5.2.13 to 7.2 with Snapshot Management feature? = Bacula: 5.2.13 OS : CentOS Linux release 7.6.1810 (Core) Database : mysql Ver 15.1 Distrib 5.5.60-MariaDB = Please provide me with a step by step instruction for the upgrade, I couldn’t find a proper documentation for the bacula upgrade. Hope you guys will help :) Regards, Preash ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to upgrade Bacula 5.2.13 to 7.2
Hi Wanderlei, Thank you for the quick response, I'll check this out and let you know the result. Just a heads up; is there any problem in upgrading 5.2.13 directly to 9.4.3? On Thu, May 30, 2019 at 4:18 PM Wanderlei Huttel wrote: > Hello Preash > > Have you install Bacula compiling source code or using packages? > > I have some tips to upgrade bacula by compilation of source code. It works > to install using packages also. > You need to do in mind that the basically, Bacula have conf files and a > catalog (database), and volumes. > If you have these 3 pillars, you can restore any Bacula environment. > > = > Tips on how to upgrade Bacula > - Stop all bacula daemons and make sure none are running, if necessary > execute the command (pkill -9 bacula) > - Perform a backup of the Bacula database (run the standard Bacula backup > script, usually "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog". > Copy the file generated by the script to a secure location. > - Make a backup of the Bacula configuration folder (*.conf), usually > /etc/bacula or /opt/bacula (make sure do the backup of correct directory) > - If your bacula was installed using packages, it is interesting to remove > all packages related to Bacula. Use the command: "apt-get remove > package_name or yum remove package_name" > If the bacula was installed using compilation, it is interesting to use > the same options used in the "./configure" > - Download the source code, and proceed as if it were a new installation > - Copy the configuration files (* .conf) from the backup to /etc/bacula or > /opt/bacula > - Verify that the paths that were informed in the build are the same as > the previous configuration, otherwise, you need to edit the configuration > files and change these paths. > - Run the script to update the Bacula database (usually > update_bacula_tables or update_mysql_tables or update_postgresql_tables) > - Run the daemons test commands and make sure they have no configuration > errors. bacula-dir -t, bacula-sd -t and bacula-fd-t > - Start the bacula and run bconsole > - And if all went well, congratulations, your bacula was updated > successfully! > - In case of errors you must run Bacula in debug mode and check for > possible errors. Sometimes it's interesting to run a pkill -9 to stop all > bacula daemons, and start each separate daemon with the debug option (-d > 500). bacula-dir-d 500, bacula-sd-d 500, bacula-fd-d 500 > = > > There is a script to install Bacula by packages from Bacula repositories > (But this script was tested for fresh installations, I don't know the > behavior in installations already existent) > > http://www.bacula.lat/community/bacula-community-9-x-official-packages-installation-script/?lang=en > > > Or you can compile using this link: > > http://www.bacula.lat/community/community-bacula-9-0-8-compilation-and-installation-commands/?lang=en > > > I suggest also you upgrade to the latests Bacula version (9.4.4) (only > compilation for a while or 9.4.3 by packages) > https://www.bacula.org/source-download-center/ > > Best regards > > *Wanderlei Hüttel* > http://www.bacula.com.br > > > Em qui, 30 de mai de 2019 às 03:23, preash raj > escreveu: > >> Hello Guys, >> >> How do I upgrade Bacula 5.2.13 to 7.2 with Snapshot Management feature? >> >> = >> Bacula: 5.2.13 >> OS : CentOS Linux release 7.6.1810 (Core) >> Database : mysql Ver 15.1 Distrib 5.5.60-MariaDB >> = >> >> Please provide me with a step by step instruction for the upgrade, I >> couldn’t find a proper documentation for the bacula upgrade. >> >> Hope you guys will help :) >> >> Regards, >> Preash >> ___ >> 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] How to upgrade Bacula 5.2.13 to 7.2
Hi Abdul, Thanks for the quick response, I'll check this out and let you know. On Thu, May 30, 2019 at 12:24 PM Abdul Qoyyuum wrote: > It's in the manual: > https://www.bacula.org/7.2.x-manuals/en/main/Installing_Bacula.html#SECTION00122 > > On Thu, May 30, 2019 at 2:20 PM preash raj wrote: > >> Hello Guys, >> >> How do I upgrade Bacula 5.2.13 to 7.2 with Snapshot Management feature? >> >> = >> Bacula: 5.2.13 >> OS : CentOS Linux release 7.6.1810 (Core) >> Database : mysql Ver 15.1 Distrib 5.5.60-MariaDB >> = >> >> Please provide me with a step by step instruction for the upgrade, I >> couldn’t find a proper documentation for the bacula upgrade. >> >> Hope you guys will help :) >> >> Regards, >> Preash >> ___ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > > -- > Abdul Qoyyuum Bin Haji Abdul Kadir > HP No: +673 720 8043 > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] How to install Bacula 9.4.4/9.4.3 in Centos 7
Hi Guys, Please let me know a step by step instruction to install Bacula 9.4.4/9.4.3 in Centos 7 and configure snapshot management. Regards, Preash ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula 9.4.3: bacula-sd not starting
Hi, I've installed Bacula 9.4.3 and the bacula-sd service is not getting started. the same configuration works fine with Bacula 5.2.13, please check the below debug error and shed some light on this. === # bacula-sd -f -d 200 bacula-sd: address_conf.c:274-0 Initaddr 0.0.0.0:9103 bacula-sd: jcr.c:131-0 read_last_jobs seek to 192 bacula-sd: jcr.c:138-0 Read num_items=10 bacula-sd: stored.c:608-0 calling init_dev FileStorage bacula-sd: init_dev.c:116-0 init_dev dev_type=0 bacula-sd: init_dev.c:152-0 Num drivers=15 bacula-sd: bnet_server.c:86-0 Addresses 109.73.166.242:9103 bacula-sd: init_dev.c:165-0 loadable=0 type=1 loaded=1 name=file handle=0 bacula-sd: init_dev.c:391-0 init_dev: tape=0 dev_name=/bacula/backup bacula-sd: stored.c:610-0 SD init done FileStorage bacula-sd: block_util.c:170-0 New block adata=0 len=64512 block=7f54f0002560 bacula-sd: acquire.c:663-0 Attach 0xf0001f48 to dev "FileStorage" (/bacula/backup) === ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 9.4.3: bacula-sd not starting
Hi, It is centos 7 and bacula- sd started and enabled before but it got stopped once I test run a remote backup, then it doesn't get started again. Please shed some light on this. On Fri, Jun 7, 2019, 7:01 PM Martin Simmons That looks like a normal start to me. > > Which OS is this? How is the service started? Is the service enabled? > Check > the syslog (or service-specific logs) for error messages. > > Does it run bacula-sd as a non-root user? If so, you need to test it like > that. > > __Martin > > > >>>>> On Fri, 7 Jun 2019 15:33:15 +0530, preash raj said: > > > > Hi, > > I've installed Bacula 9.4.3 and the bacula-sd service is not getting > > started. the same configuration works fine with Bacula 5.2.13, please > check > > the below debug error and shed some light on this. > > > > === > > # bacula-sd -f -d 200 > > bacula-sd: address_conf.c:274-0 Initaddr 0.0.0.0:9103 > > bacula-sd: jcr.c:131-0 read_last_jobs seek to 192 > > bacula-sd: jcr.c:138-0 Read num_items=10 > > bacula-sd: stored.c:608-0 calling init_dev FileStorage > > bacula-sd: init_dev.c:116-0 init_dev dev_type=0 > > bacula-sd: init_dev.c:152-0 Num drivers=15 > > bacula-sd: bnet_server.c:86-0 Addresses 109.73.166.242:9103 > > bacula-sd: init_dev.c:165-0 loadable=0 type=1 loaded=1 name=file handle=0 > > bacula-sd: init_dev.c:391-0 init_dev: tape=0 dev_name=/bacula/backup > > bacula-sd: stored.c:610-0 SD init done FileStorage > > bacula-sd: block_util.c:170-0 New block adata=0 len=64512 > block=7f54f0002560 > > bacula-sd: acquire.c:663-0 Attach 0xf0001f48 to dev "FileStorage" > > (/bacula/backup) > > === > > > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 9.4.3: bacula-sd not starting
acula Storage Daemon service Loaded: loaded (/usr/lib/systemd/system/bacula-sd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2019-06-10 01:49:08 EDT; 4s ago Process: 10655 ExecStart=/opt/bacula/bin/bacula-sd -fP -c /opt/bacula/etc/bacula-sd.conf (code=exited, status=1/FAILURE) Main PID: 10655 (code=exited, status=1/FAILURE) Jun 10 01:49:08 bacula.server.in systemd[1]: Started Bacula Storage Daemon service. Jun 10 01:49:08 bacula.server.in bacula-sd[10655]: bacula-sd: ERROR TERMINATION at parse_conf.c:1021 Jun 10 01:49:08 bacula.server.in systemd[1]: bacula-sd.service: main process exited, code=exited, status=1/FAILURE Jun 10 01:49:08 bacula.server.in systemd[1]: Unit bacula-sd.service entered failed state. Jun 10 01:49:08 bacula.server.in systemd[1]: bacula-sd.service failed. == Although bacula-dir service started it shows the below errors: == service bacula-dir status Redirecting to /bin/systemctl status bacula-dir.service ● bacula-dir.service - Bacula Director Daemon service Loaded: loaded (/usr/lib/systemd/system/bacula-dir.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-06-05 03:51:29 EDT; 4 days ago Main PID: 8561 (bacula-dir) Tasks: 3 CGroup: /system.slice/bacula-dir.service └─8561 /opt/bacula/bin/bacula-dir -fP -c /opt/bacula/etc/bacula-dir.conf Jun 09 23:06:06 bacula.server.in bacula-dir[8561]: 09-Jun 23:06 Message delivery ERROR: Mail program terminated in error. Jun 09 23:06:06 bacula.server.in bacula-dir[8561]: CMD=/usr/sbin/bsmtp -h localhost -f "(Bacula) " -s "Bacula: Backup Fatal Error of cor...localhost Jun 09 23:06:06 bacula.server.in bacula-dir[8561]: ERR=Child exited with code 1 Jun 09 23:06:06 bacula.server.in bacula-dir[8561]: 09-Jun 23:06 Message delivery ERROR: Mail program terminated in error. CMD=/usr/sbin/bsmtp -h localhost -f "(Bacula) " -s "Bacula: Backup Fatal Error of cor...localhost ERR=Child exited with code 1... Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: 09-Jun 23:10 Message delivery ERROR: Mail prog: bsmtp: bsmtp.c:488-0 Failed to connect to mailhost localhost Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: 09-Jun 23:10 Message delivery ERROR: Mail prog: bsmtp: bsmtp.c:488-0 Failed to connect to mailhost localhost Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: 09-Jun 23:10 Message delivery ERROR: Mail program terminated in error. Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: CMD=/usr/sbin/bsmtp -h localhost -f "(Bacula) " -s "Bacula: Backup Error of bacula-fd...localhost Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: ERR=Child exited with code 1 Jun 09 23:10:03 bacula.server.in bacula-dir[8561]: 09-Jun 23:10 Message delivery ERROR: Mail program terminated in error. CMD=/usr/sbin/bsmtp -h localhost -f "(Bacula) " -s "Bacula: Backup Error of bacula-fd...localhost ERR=Child exited with code 1... Hint: Some lines were ellipsized, use -l to show in full. == On Sun, Jun 9, 2019 at 3:50 PM Tilman Schmidt wrote: > Given that the debug log you shared shows a normal successful start and > no error, please share your evidence that it stopped and doesn't get > started again. > Did you get any error message? > If so, please share its exact wording and where it appeared. > Did you check with the ps command whether there is a bacula-sd process > running? > > Be aware that CentOS 7 uses systemd which adds a layer of complexity to > service management and is notorious for misreporting service status. > To make sure you're not actually having a systemd problem, try starting > bacula-sd directly from the command line and check whether it works then. > > HTH > Tilman > > Am 09.06.2019 um 10:21 schrieb preash raj: > > Hi, > > > > It is centos 7 and bacula- sd started and enabled before but it got > > stopped once I test run a remote backup, then it doesn't get started > > again. Please shed some light on this. > > > > > > On Fri, Jun 7, 2019, 7:01 PM Martin Simmons > <mailto:mar...@lispworks.com> wrote: > > > > That looks like a normal start to me. > > > > Which OS is this? How is the service started? Is the service > > enabled? Check > > the syslog (or service-specific logs) for error messages. > > > >
Re: [Bacula-users] Bacula 9.4.3: bacula-sd not starting
Hi, I've checked and corrected the issue with bacula and the backups are working fine, thank you for the effort Tilman :) Can you guys guide me to enable the snapshot management in 9.4.3? On Mon, Jun 10, 2019 at 5:49 PM Tilman Schmidt wrote: > Ok, you have several problems here involving all three Bacula services, > not just bacula-sd. > > Am 10.06.2019 um 08:07 schrieb preash raj: > > 10-Jun 01:49 bacula-dir JobId 208: Start Backup JobId 208, > Job=BackupCorp.client.in.2019-06-10_01.49.34_04 > > 10-Jun 01:49 bacula-dir JobId 208: Fatal error: bdb.h:142 bdb.h:142 > query SELECT > MediaId,VolumeName,VolJobs,VolFiles,VolBlocks,VolBytes,VolMounts,VolErrors,VolWrites,MaxVolBytes,VolCapacityBytes,MediaType,VolStatus,PoolId,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,Recycle,Slot,FirstWritten,LastWritten,InChanger,EndFile,EndBlock,VolType,VolParts,VolCloudParts,LastPartBytes,LabelType,LabelDate,StorageId,Enabled,LocationId,RecycleCount,InitialWrite,ScratchPoolId,RecyclePoolId,VolReadTime,VolWriteTime,ActionOnPurge,CacheRetention > FROM Media WHERE PoolId=4 AND MediaType='File' AND Enabled=1 AND > VolStatus='Append' AND VolType IN (0,1) ORDER BY LastWritten IS > NULL,LastWritten DESC,MediaId LIMIT 1 failed: > > Unknown column 'VolType' in 'field list' > > This is a problem with your Bacula database. > It prevents the director bacula-dir from doing anything useful so you'll > have to fix that first. > > Has this installation ever worked? > If so, what happened between then and now? > Did you perhaps upgrade the director to a newer version and neglected to > run the update_bacula_tables script? > > > 10-Jun 01:49 bacula-dir JobId 208: Using Device "FileStorage" to write. > > 10-Jun 01:49 bacula-dir JobId 208: Fatal error: No Job status returned > from FD. > > This seems to indicate that the director bacula-dir was unable to > contact the file daemon on corp.client.in-fd. > However it might also be a consecutive fault of the database problem, so > fix the database problem first and see whether that makes the "No Job > status" problem go away, too. > > > Jun 10 01:49:08 bacula.server.in <http://bacula.server.in> systemd[1]: > > Started Bacula Storage Daemon service. > > Jun 10 01:49:08 bacula.server.in <http://bacula.server.in> > > bacula-sd[10655]: bacula-sd: ERROR TERMINATION at parse_conf.c:1021 > > This seems to indicate a problem with the configuration file of your > storage daemon, bacula-sd.conf. > Try running the command line reported by systemd > > /opt/bacula/bin/bacula-sd -fP -c /opt/bacula/etc/bacula-sd.conf > > from the command line to see whether the error reproduces. > If so, try adding -v (verbose) and -d (debug) options to get more > information on what is going wrong. > Otherwise you have a systemd problem. > Try to find out what systemd does differently from manual start. > A frequent problem with systemd is that it is starting services under a > different user, so check the unit file > /usr/lib/systemd/system/bacula-sd.service > for "User=" and "Group=" lines. > > > Jun 09 23:06:06 bacula.server.in <http://bacula.server.in> > > bacula-dir[8561]: 09-Jun 23:06 Message delivery ERROR: Mail program > > terminated in error. > > Jun 09 23:06:06 bacula.server.in <http://bacula.server.in> > > bacula-dir[8561]: CMD=/usr/sbin/bsmtp -h localhost -f "(Bacula) > > " -s "Bacula: Backup Fatal Error of cor...localhost > > This is probably the easiest problem to fix. > Regrettably systemd has once again cut out the important part of the > message, but it appears in full later on: > > > Jun 09 23:10:03 bacula.server.in <http://bacula.server.in> > > bacula-dir[8561]: 09-Jun 23:10 Message delivery ERROR: Mail prog: > > bsmtp: bsmtp.c:488-0 Failed to connect to mailhost localhost > > So you configured Bacula so send mail notifications through the mail > server running on the same machine as the director, but there is no mail > server running on that machine. Either start a mail server listening on > localhost port 25, or configure Bacula to use a different server. > > As an aside, given the number and nature of problems you have, I would > urgently recommend you spend some time with the Bacula documentation. > > Btw, would you mind not using HTML format in your mailing list posts? > It does funny things to the log snippets you quote and makes it > generally difficult to read and reply to your post. > > HTH > Tilman > > > ___ > 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
