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@lis
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 5
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 c
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 volum
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
Stora
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
Stora
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 a
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!
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 9
