FreeBSD Port: bacula-client-3.0.0_1

Michael Hughes michael.hughes at gmx.com
Mon May 4 16:51:30 UTC 2009


> Have you raised this issue on the bacula users mailing list?  If so,
> what is the URL into the archives so we can investigate.

In response to your question, I have raised the issue on the bacula-users mailing list, although I
haven't had any responses yet. I came to the conclusion about the client and director
incompatibility through our own testing and a couple forum threads I found web searching.

We upgraded the bacula client port which upgraded the bacula-fd daemon running from 2.4.4 to 3.0.1.
No configuration files were changed, and backups ran properly prior to the port upgrade. I have
checked the obvious, such as the port being closed by a firewall or the network interface not being
up. Which left me testing for incompatibilities between the director and client because of the major
version number change.

I did find these related threads in the bacula-users archive
http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg34494.html
and
http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg34494.html

Michael Hughes
SSLI/MTML Labs
Student System Administrator


More information about the freebsd-ports mailing list