date:20180115

Re: [Bacula-users] Number of files mismatch!

2018-01-15 Thread krashoverride

Hi again,

Quick feedback, yesterday while I was writing this mail, i started again my 
bscan + change volume status process, then started again my differential backup 
on the same Q003 tape. Backup is successful this morning.

- Mail original -
De: krashoverr...@free.fr
À: bacula-users@lists.sourceforge.net
Envoyé: Lundi 15 Janvier 2018 21:47:11
Objet: [Bacula-users] Number of files mismatch!

Good evening here,

I'm having an issue with the number of files that does not match between the 
tape and the DB
Number of files on the tape is zero, while the tape isn't empty.
I'm using bacula-dir / bacula-sd 7.4.4 on a virtualized debian 9 server (SQLite 
database)

15-Jan 21:00 xxx-dir JobId 54: Using Device "Lecteur_LTO6" to write.
15-Jan 21:00 xxx-sd JobId 54: Volume "Q003" previously written, moving to end 
of data.
15-Jan 21:01 xxx-sd JobId 54: Error: Bacula cannot write on tape Volume "Q003" 
because:
The number of files mismatch! Volume=0 Catalog=132
15-Jan 21:01 xxx-sd JobId 54: Marking Volume "Q003" in Error in Catalog.

I've had this error yesterday evening, that i thought i fixed with a bscan 
command, that listed me jobs / files on tape correctly
After this bscan, i've changed the status of the volume from Error to Append, 
and started a catalog backup job, that ran successfully on tape Q003. Then, 
this evening, error again.

Knowing that I have for now a total of 5 tapes in my bacula, and i've had no 
problems for any other tape but Q003, do I have to consider that the tape is 
faulty ?

Also, i've read topics about the two directives "BSF at EOM" and "TWO EOF" that 
seemed to fix this problem for other persons. What do you think?
--
Device {
  Name = Lecteur_LTO6
  Archive Device = /dev/nst0
  Media Type = LTO-6
  LabelMedia = no
  Random Access = yes
  AutomaticMount = yes;
  RemovableMedia = no
  AlwaysOpen = no
}

Thank you,

Thibault.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Number of files mismatch!

2018-01-15 Thread krashoverride

Good evening here,

I'm having an issue with the number of files that does not match between the 
tape and the DB
Number of files on the tape is zero, while the tape isn't empty.
I'm using bacula-dir / bacula-sd 7.4.4 on a virtualized debian 9 server (SQLite 
database)

15-Jan 21:00 xxx-dir JobId 54: Using Device "Lecteur_LTO6" to write.
15-Jan 21:00 xxx-sd JobId 54: Volume "Q003" previously written, moving to end 
of data.
15-Jan 21:01 xxx-sd JobId 54: Error: Bacula cannot write on tape Volume "Q003" 
because:
The number of files mismatch! Volume=0 Catalog=132
15-Jan 21:01 xxx-sd JobId 54: Marking Volume "Q003" in Error in Catalog.

I've had this error yesterday evening, that i thought i fixed with a bscan 
command, that listed me jobs / files on tape correctly
After this bscan, i've changed the status of the volume from Error to Append, 
and started a catalog backup job, that ran successfully on tape Q003. Then, 
this evening, error again.

Knowing that I have for now a total of 5 tapes in my bacula, and i've had no 
problems for any other tape but Q003, do I have to consider that the tape is 
faulty ?

Also, i've read topics about the two directives "BSF at EOM" and "TWO EOF" that 
seemed to fix this problem for other persons. What do you think?
--
Device {
  Name = Lecteur_LTO6
  Archive Device = /dev/nst0
  Media Type = LTO-6
  LabelMedia = no
  Random Access = yes
  AutomaticMount = yes;
  RemovableMedia = no
  AlwaysOpen = no
}

Thank you,

Thibault.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] problems with storage daemon

2018-01-15 Thread Jerry Lowry

Martin,

Yeah, I forgot to create a new output file for the second run.  The first
run the client info scrolled off the window buffer, so I ran it again.

Yes it does affect all of the clients, the only thing that runs is the
catalog backup.
Yes, 10.10.10.3 is the correct IP.
No, firewall, well I checked and apparently the kernel update turned on the
firewall service.  I did not check because I have never had this happen
before after an update. Did not even think to check.

Thank you much,



On Mon, Jan 15, 2018 at 3:07 AM, Martin Simmons 
wrote:

> The storage log shows no sign of any connection from the client (though it
> looks like you sent logs from two different jobs).
>
> Does the problem affect all clients?
>
> Is 10.10.10.3 the correct IP address of distress?
>
> Is distress running some firewall (iptables etc)?
>
> You could try
>
> telnet distress 9103
>
> on the client machine to see if that can connect (see
> https://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx).
>
> __Martin
>
> > On Fri, 12 Jan 2018 10:32:10 -0800, Jerry Lowry said:
> >
> > Well, I recompiled the source for bacula 9.0.6 on the offending server
> but
> > it is still failing to work.  I have started each of the processes with
> the
> > debug flag set at 100 and am attaching the output for each system (
> > director, storage,client).  It looks to me like the client gets started
> but
> > is not connecting to the storage daemon.  Not sure why because I can ping
> > it from the client, it is not blocked by a firewall because it's on the
> > same subnet.  The windows firewall is turned off as well.  Hopefully,
> this
> > information will help figure out the problem.
> > centos 7.3
> > mariadb 10.2.12
> > bacula 9.0.6
> >
> > thanks
> >
> > On Thu, Jan 11, 2018 at 2:08 PM, Jerry Lowry 
> wrote:
> >
> > > Dan,
> > > Yes, bacula did not change at all. This bacula server is both director
> and
> > > storage.  All of the clients are windows systems running the latest 64
> bit
> > > release of community client ( 5.2.10).
> > >
> > > I am getting ready to rebuild bacula based on the new kernel and hoping
> > > this will fix the problem.  I have already done a database check with
> the
> > > new version of MariaDB and the bacula database is fine for its point of
> > > view.
> > >
> > > jerry
> > >
> > > On Thu, Jan 11, 2018 at 11:51 AM, Dan Langille 
> wrote:
> > >
> > >> > On Jan 11, 2018, at 11:56 AM, Jerry Lowry 
> > >> wrote:
> > >> >
> > >> > Hi,  Last weekend I ran through a bunch of updates for my backup
> > >> server.  Of the many updates it updated the kernel and MariaDB (
> 10.2.8 ->
> > >> 10.2.12 ). I have recently upgraded bacula to 9.0.6.  The problem is
> that
> > >> the following error:
> > >> >  10-Jan 20:36 distress-dir JobId 34724: Fatal error: Bad response to
> > >> Storage command: wanted 2000 OK storage
> > >> > , got 2902 Bad storage
> > >> >
> > >> > I also get errors saying that the client can not connect to the
> storage
> > >> server:
> > >> >
> > >> > 11-Jan 01:37 Denial-fd: BackupDenial.2018-01-11_00.05.01_44 Fatal
> > >> error: ../../lib/bnet.c:870 Unable to connect to Storage daemon on
> > >> distress.ACCOUNTING.EDT.LOCAL:9103. ERR=No error
> > >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: Socket error on
> > >> Storage command: ERR=No data available
> > >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: No Job status
> > >> returned from FD.
> > >> >
> > >> > nothing was changed in the config files, just the updates were
> > >> installed. I can ping the storage server from all of the clients.
> > >> >
> > >> > The jobs get to the point where they display "waiting for client"
> but
> > >> the jobs never complete.
> > >> >
> > >>
> > >> When you did those update, did you keep all bacula-dir and all
> bacula-sd
> > >> on the same exact version?
> > >>
> > >> The general rule for software versions is:
> > >>
> > >> bacula-dir = bacula-sd >= bacula-fd
> > >>
> > >> --
> > >> Dan Langille - BSDCan / PGCon
> > >> d...@langille.org
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Procedure to remove properly client

2018-01-15 Thread Rolf Halmen

Hi John,

The database can correlate jobs to volume files.
I'm not at a workstation right now, but off the top of my head, I'd assume 
joining the jobs, media, and clients tables should let you get to the list of 
volumes that contain backup-data of the specified client.

Do keep in mind that volume files can contain data from multiple jobs, unless 
"use volume once = true".

Kind regards,
Rolf 

On January 15, 2018 2:10:00 PM UTC, John Naggets  
wrote:
>Hello,
>
>It happens that some clients on the network get removed and as such do
>not need to be backed up anymore. Now I would like to know what is the
>procedure on the bacula director in order to remove properly and
>entirely a bacula client?
>
>I checked the official documentation but could not find any procedure
>for that purpose.
>
>From my understanding I need to delete the jobs and files associated
>with them as well as the volumes and finally the physical volumes on
>the filesystem (backups are done on files on a partition of the backup
>server).
>
>My problem here is that the physical volumes on the filesystem all
>have the same label except for the number so how would I know which
>file I can delete?
>
>Thank you in advance for your help.
>
>Best regards,
>John
>
>--
>Check out the vibrant tech community on one of the world's most
>engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>___
>Bacula-users mailing list
>Bacula-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula fd authentication problem

2018-01-15 Thread Boris Petrovic

Hi everyone,

I’m experiencing strange problems on some of my bacula file daemons since I 
have pathed Ubuntu kernel for Meltdown/Spectre vulnerability.
I’m getting following error message in bconsole after job fails:

15-Jan 15:24 tools JobId 5963: Fatal error: Authorization key rejected by 
Storage daemon.
Please see 
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
 for help.
15-Jan 15:24 bacula-dir JobId 5963: Fatal error: Bad response to Storage 
command: wanted 2000 OK storage
, got 2902 Bad storage

15-Jan 15:24 bacula-dir JobId 5963: Error: Bacula bacula-dir 7.0.5 (28Jul14):
  Build OS:   x86_64-pc-linux-gnu ubuntu 16.04
  JobId:  5963
  Job:Tools-Backup.2018-01-15_15.24.27_06
  Backup Level:   Full
  Client: "tools" 7.0.5 (28Jul14) 
x86_64-pc-linux-gnu,ubuntu,16.04
  FileSet:"Full-Fileset" 2017-10-09 14:24:49
  Pool:   "Full-Backup-Pool" (From Command input)
  Catalog:"nvg-backup-catalog" (From Client resource)
  Storage:"backup-storage" (From Pool resource)
  Scheduled time: 15-Jan-2018 15:24:25
  Start time: 15-Jan-2018 15:24:29
  End time:   15-Jan-2018 15:24:40
  Elapsed time:   11 secs
  Priority:   10
  FD Files Written:   0
  SD Files Written:   0
  FD Bytes Written:   0 (0 B)
  SD Bytes Written:   0 (0 B)
  Rate:   0.0 KB/s
  Software Compression:   None
  VSS:no
  Encryption: no
  Accurate:   no
  Volume name(s):
  Volume Session Id:  2
  Volume Session Time:1516026063
  Last Volume Bytes:  1,674,336,771,120 (1.674 TB)
  Non-fatal FD errors:2
  SD Errors:  0
  FD termination status:  Error
  SD termination status:  Waiting on FD
  Termination:*** Backup Error ***

On client side, when bacula-fd is started as a foreground process with maximum 
debug output (bacula-fd -f -d 400 -c /etc/bacula/bacula-fd.conf) I see that 
file daemon menages to connect to bacula SD, but fails to authenticate. This is 
bacula-fd process output:

tools: job.c:1855-0 StorageCmd: storage address= baculaSD.my.domain port=9103 
ssl=0
tools: job.c:1883-0 Connect to storage: baculaSD.my.domain:9103 ssl=0
tools: bsock.c:208-0 Current 127.0.0.1:9103 All 127.0.0.1:9103
tools: bsock.c:137-0 who=Storage daemon host=baculaSD.my.domain port=9103
tools: bsock.c:310-0 OK connected to server  Storage daemon 
baculaSD.my.domain:9103.
tools: job.c:1899-0 Connection OK to SD.
tools: authenticate.c:237-0 Send to SD: Hello Bacula SD: Start Job 
Tools-Backup.2018-01-15_15.24.27_06 5
tools: authenticate.c:240-0  respond to SD challenge
tools: authenticate.c:247-0 cram_respond failed for SD: Storage daemon
tools: job.c:306-0 Quit command loop. Canceled=1
tools: runscript.c:96-0 runscript: running all RUNSCRIPT object 
(ClientAfterJob) JobStatus=f
tools: job.c:417-0 Calling term_find_files
tools: job.c:420-0 Done with term_find_files
tools: jcr.c:171-0 write_last_jobs seek to 192
tools: job.c:423-0 Done with free_jcr
tools: mem_pool.c:366-0 garbage collect memory pool

baculaSD.my.domain resolvs to localhost because this file daemon is on public 
server, and bacula server is behind NAT so I have ssh tunnel between server and 
client and it works perfectly fine for other hosts. And as you can see in 
client’s output it is able to connect to storage daemon so I belive networking 
is not the issue.
I also have duble-checked director name and password ant it matches on director 
and client’s side.


Bacula director version:
bacula-dir Version: 7.0.5 (28 July 2014) x86_64-pc-linux-gnu ubuntu 16.04
Bacula client version:
bacula-fd:
  Installed: 7.0.5+dfsg-4ubuntu0.1
  Candidate: 7.0.5+dfsg-4ubuntu0.1

I would appreciate any help since I’m bit stuck here.

Boris


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Badula-fd, SD authentication failed

2018-01-15 Thread Boris Petrovic

Hi everyone,

I’m experiencing strange problems on some of my bacula file daemons since I 
have pathed Ubuntu kernel for Meltdown/Spectre vulnerability.
I’m getting following error message in bconsole after job fails:

15-Jan 15:24 tools JobId 5963: Fatal error: Authorization key rejected by 
Storage daemon.
Please see 
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
 for help.
15-Jan 15:24 bacula-dir JobId 5963: Fatal error: Bad response to Storage 
command: wanted 2000 OK storage
, got 2902 Bad storage

15-Jan 15:24 bacula-dir JobId 5963: Error: Bacula bacula-dir 7.0.5 (28Jul14):
  Build OS:   x86_64-pc-linux-gnu ubuntu 16.04
  JobId:  5963
  Job:Tools-Backup.2018-01-15_15.24.27_06
  Backup Level:   Full
  Client: "tools" 7.0.5 (28Jul14) 
x86_64-pc-linux-gnu,ubuntu,16.04
  FileSet:"Full-Fileset" 2017-10-09 14:24:49
  Pool:   "Full-Backup-Pool" (From Command input)
  Catalog:"nvg-backup-catalog" (From Client resource)
  Storage:"backup-storage" (From Pool resource)
  Scheduled time: 15-Jan-2018 15:24:25
  Start time: 15-Jan-2018 15:24:29
  End time:   15-Jan-2018 15:24:40
  Elapsed time:   11 secs
  Priority:   10
  FD Files Written:   0
  SD Files Written:   0
  FD Bytes Written:   0 (0 B)
  SD Bytes Written:   0 (0 B)
  Rate:   0.0 KB/s
  Software Compression:   None
  VSS:no
  Encryption: no
  Accurate:   no
  Volume name(s):
  Volume Session Id:  2
  Volume Session Time:1516026063
  Last Volume Bytes:  1,674,336,771,120 (1.674 TB)
  Non-fatal FD errors:2
  SD Errors:  0
  FD termination status:  Error
  SD termination status:  Waiting on FD
  Termination:*** Backup Error ***

On client side, when bacula-fd is started as a foreground process with maximum 
debug output (bacula-fd -f -d 400 -c /etc/bacula/bacula-fd.conf) I see that 
file daemon menages to connect to bacula SD, but fails to authenticate. This is 
bacula-fd process output:

tools: job.c:1855-0 StorageCmd: storage address= baculaSD.my.domain port=9103 
ssl=0
tools: job.c:1883-0 Connect to storage: baculaSD.my.domain:9103 ssl=0
tools: bsock.c:208-0 Current 127.0.0.1:9103 All 127.0.0.1:9103
tools: bsock.c:137-0 who=Storage daemon host=baculaSD.my.domain port=9103
tools: bsock.c:310-0 OK connected to server  Storage daemon 
baculaSD.my.domain:9103.
tools: job.c:1899-0 Connection OK to SD.
tools: authenticate.c:237-0 Send to SD: Hello Bacula SD: Start Job 
Tools-Backup.2018-01-15_15.24.27_06 5
tools: authenticate.c:240-0  respond to SD challenge
tools: authenticate.c:247-0 cram_respond failed for SD: Storage daemon
tools: job.c:306-0 Quit command loop. Canceled=1
tools: runscript.c:96-0 runscript: running all RUNSCRIPT object 
(ClientAfterJob) JobStatus=f
tools: job.c:417-0 Calling term_find_files
tools: job.c:420-0 Done with term_find_files
tools: jcr.c:171-0 write_last_jobs seek to 192
tools: job.c:423-0 Done with free_jcr
tools: mem_pool.c:366-0 garbage collect memory pool

baculaSD.my.domain resolvs to localhost because this file daemon is on public 
server, and bacula server is behind NAT so I have ssh tunnel between server and 
client and it works perfectly fine for other hosts. And as you can see in 
client’s output it is able to connect to storage daemon so I belive networking 
is not the issue.
I also have duble-checked director name and password ant it matches on director 
and client’s side.

Bacula director version:
bacula-dir Version: 7.0.5 (28 July 2014) x86_64-pc-linux-gnu ubuntu 16.04
Bacula client version:
bacula-fd:
  Installed: 7.0.5+dfsg-4ubuntu0.1
  Candidate: 7.0.5+dfsg-4ubuntu0.1

I would appreciate any help since I’m bit stuck here.

Boris

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Procedure to remove properly client

2018-01-15 Thread John Naggets

Hello,

It happens that some clients on the network get removed and as such do
not need to be backed up anymore. Now I would like to know what is the
procedure on the bacula director in order to remove properly and
entirely a bacula client?

I checked the official documentation but could not find any procedure
for that purpose.

>From my understanding I need to delete the jobs and files associated
with them as well as the volumes and finally the physical volumes on
the filesystem (backups are done on files on a partition of the backup
server).

My problem here is that the physical volumes on the filesystem all
have the same label except for the number so how would I know which
file I can delete?

Thank you in advance for your help.

Best regards,
John

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] problems with storage daemon

2018-01-15 Thread Vanush "Misha" Paturyan

On 12 January 2018 at 18:32, Jerry Lowry  wrote:

> centos 7.3
> mariadb 10.2.12
> bacula 9.0.6

CentOS == SELinux! Check that SELinux is not blocking bacula-sd from
properly starting. I don't have a CentOS host on hand to give exact
location where to look, but google should help you!

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] problems with storage daemon

2018-01-15 Thread Martin Simmons

The storage log shows no sign of any connection from the client (though it
looks like you sent logs from two different jobs).

Does the problem affect all clients?

Is 10.10.10.3 the correct IP address of distress?

Is distress running some firewall (iptables etc)?

You could try

telnet distress 9103

on the client machine to see if that can connect (see
https://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx).

__Martin

> On Fri, 12 Jan 2018 10:32:10 -0800, Jerry Lowry said:
> 
> Well, I recompiled the source for bacula 9.0.6 on the offending server but
> it is still failing to work.  I have started each of the processes with the
> debug flag set at 100 and am attaching the output for each system (
> director, storage,client).  It looks to me like the client gets started but
> is not connecting to the storage daemon.  Not sure why because I can ping
> it from the client, it is not blocked by a firewall because it's on the
> same subnet.  The windows firewall is turned off as well.  Hopefully, this
> information will help figure out the problem.
> centos 7.3
> mariadb 10.2.12
> bacula 9.0.6
> 
> thanks
> 
> On Thu, Jan 11, 2018 at 2:08 PM, Jerry Lowry  wrote:
> 
> > Dan,
> > Yes, bacula did not change at all. This bacula server is both director and
> > storage.  All of the clients are windows systems running the latest 64 bit
> > release of community client ( 5.2.10).
> >
> > I am getting ready to rebuild bacula based on the new kernel and hoping
> > this will fix the problem.  I have already done a database check with the
> > new version of MariaDB and the bacula database is fine for its point of
> > view.
> >
> > jerry
> >
> > On Thu, Jan 11, 2018 at 11:51 AM, Dan Langille  wrote:
> >
> >> > On Jan 11, 2018, at 11:56 AM, Jerry Lowry 
> >> wrote:
> >> >
> >> > Hi,  Last weekend I ran through a bunch of updates for my backup
> >> server.  Of the many updates it updated the kernel and MariaDB ( 10.2.8 ->
> >> 10.2.12 ). I have recently upgraded bacula to 9.0.6.  The problem is that
> >> the following error:
> >> >  10-Jan 20:36 distress-dir JobId 34724: Fatal error: Bad response to
> >> Storage command: wanted 2000 OK storage
> >> > , got 2902 Bad storage
> >> >
> >> > I also get errors saying that the client can not connect to the storage
> >> server:
> >> >
> >> > 11-Jan 01:37 Denial-fd: BackupDenial.2018-01-11_00.05.01_44 Fatal
> >> error: ../../lib/bnet.c:870 Unable to connect to Storage daemon on
> >> distress.ACCOUNTING.EDT.LOCAL:9103. ERR=No error
> >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: Socket error on
> >> Storage command: ERR=No data available
> >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: No Job status
> >> returned from FD.
> >> >
> >> > nothing was changed in the config files, just the updates were
> >> installed. I can ping the storage server from all of the clients.
> >> >
> >> > The jobs get to the point where they display "waiting for client"  but
> >> the jobs never complete.
> >> >
> >>
> >> When you did those update, did you keep all bacula-dir and all bacula-sd
> >> on the same exact version?
> >>
> >> The general rule for software versions is:
> >>
> >> bacula-dir = bacula-sd >= bacula-fd
> >>
> >> --
> >> Dan Langille - BSDCan / PGCon
> >> d...@langille.org
> >>
> >>
> >>
> >>
> >>
> >

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Number of files mismatch!

[Bacula-users] Number of files mismatch!

Re: [Bacula-users] problems with storage daemon

Re: [Bacula-users] Procedure to remove properly client

[Bacula-users] Bacula fd authentication problem

[Bacula-users] Badula-fd, SD authentication failed

[Bacula-users] Procedure to remove properly client

Re: [Bacula-users] problems with storage daemon

Re: [Bacula-users] problems with storage daemon

9 matches

Site Navigation

Mail list logo

Footer information