Hi Gary,
I think I misunderstood your issue because of "Most of my other storage
servers are 5.0.3 (one is 5.0.0)".
I was unable to find 5.X Bacula rpms for Fedora 21, just 7.X.
One possibility is to build Bacula from source for this Fedora 21 host.
Also, you could try a post to this list with "5.
Hi Ana
Thank you for this. However, initialy the opposite seems to have been the
case. The storage daemons at 5.0.x were working fine, while the one at 5.2.13
was not. However, changing the client has fixed this specific client.
While looking into this, and trying to find out how to install 5.
Hello Gary,
If your director is running 5.2.13, you should have all your storage
daemons in this version too. Also If you have a client in the director
host, this client should be the same version of director. About your client
problems, you should have your client versions at most equal to direct
Hi all,
I'm replacing a old (Fedora 14) server with a Centos 7 one. I've copied
the /etc/bacula/bacula-[sf]d.conf files and everything looks fine.
Both the client and storage services are running and talk to the director
without problems. However, some of the clients fail to connect with the
s
On 7/13/2015 8:29 AM, Florian Schnabel wrote:
>
> I'm trying to use hostnames everywhere now so I changed the Storage
> definition for bacula-director to a FQN (host.domain.com) that is
> resolvably at least for my servers. Now the bacula-director got two IPs
> .. one in the old segment, one in th
> *messages
> 13-Jul 12:01 bacula-dir JobId 16580: Fatal error: Network error with FD during
> Backup: ERR=Connection reset by peer
> 13-Jul 12:01 bacula-dir JobId 16580: Fatal error: No Job status returned from
> FD.
> 13-Jul 12:01 bacula-dir JobId 16580: Error: Bacula bacula-dir 5.2.6 (21Feb12):
Hi,
I got a bacula setup running for several years now, sadly I hit a snag
and was hoping someone here can help me.
The setup is as follows:
* bacula-director and bacula-sd running on one box (v. 5.2.6, Debian wheezy)
* several bacula-sd (v. 5.2.6, Debian wheezy)
* one bacula-sd (v. 5.2.6, Debian
Hi,
I do not really understand why this back is failing (this is the only
back that never works), I have other machines in the same configuration
(bacula is in internal network and it makes the back through a firewall
port forwarding) and so many other on the same internal network.
ii bacula
5.
