> 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-us...@lists.sourceforge.net/msg34494.html and http://www.mail-archive.com/bacula-us...@lists.sourceforge.net/msg34494.html Michael Hughes SSLI/MTML Labs Student System Administrator _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"