Re: FreeBSD Port: bacula-client-3.0.0_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Hughes wrote: 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 suspect you've seen the reply. In short: don't do that. The service component can be used with older clients, but not newer clients with older servers. The solution is to use the 2.4.4 client, from ports. Yes, you'll have to use 'magic' to get a 2.4.4 client from ports. Others can help you figure out how to get a snapshot of the FreeBSD ports tree to get that version. 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 Those two links are identical. :) The answer in that link sums it up: You cannot use a version X client with anything *LESS* than a version X server. In general, the project strives to allow you to upgrade the server without upgrading the client. - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoALhUACgkQCgsXFM/7nTykjACg6Vp7zk3Ayr+3h/GZ81aj+75p ZGUAnR73MaINyFJUrxegd8VPyy08CB5H =b8QL -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: bacula-client-3.0.0_1
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
FreeBSD Port: bacula-client-3.0.0_1
Where did the 2.x series ports go? We currently use bacula-dir v. 2.4.4 on a linux host to backup our fbsd file servers, but some web research and our own testing on our fbsd test file server found that bacula-client v. 3.x is completely incompatible with bacula-dir 2.5.x. Currently our production file servers have the bacula-client v. 2.4.4 port installed, but we would like to be able to port upgrade them and still maintain a 2.4.x series bacula-client. I have searched through the cvs commits using the online FreeBSD ports search tool, but I found that there is a version jump from bacula-client v. 1.38.x to version 3.x. Yet, we originally installed the 2.4.4 client on our fbsd file servers using a port, so clearly at some point there was a 2.4.4 port. -- 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
Re: FreeBSD Port: bacula-client-3.0.0_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Hughes wrote: Where did the 2.x series ports go? We currently use bacula-dir v. 2.4.4 on a linux host to backup our fbsd file servers, but some web research and our own testing on our fbsd test file server found that bacula-client v. 3.x is completely incompatible with bacula-dir 2.5.x. Have you raised this issue on the bacula users mailing list? If so, what is the URL into the archives so we can investigate. Currently our production file servers have the bacula-client v. 2.4.4 port installed, but we would like to be able to port upgrade them and still maintain a 2.4.x series bacula-client. I'm sure that's possible, not trivial, but possible. I have searched through the cvs commits using the online FreeBSD ports search tool, but I found that there is a version jump from bacula-client v. 1.38.x to version 3.x. Yet, we originally installed the 2.4.4 client on our fbsd file servers using a port, so clearly at some point there was a 2.4.4 port. bacula-client is a slave port of bacula-server. Thus, changes to baucla-client version numbers can be gleaned from bacula-server. If you need the 2.x branch, get it from CVS. You'll need both the slave and the master. Perhaps a 2.x port is a good idea. A PR would be useful. And perhaps a repo copy. I'd love to help, but I'm busy until the end of May. - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn7WMYACgkQCgsXFM/7nTy4MgCgmvB8HU6VjxXuDRkWC/xF18rL Z3wAnA6XKu9rNsjzrNfy9eD47/i117rZ =c2j8 -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: bacula-client-3.0.0_1
On Fri, May 01, 2009 at 04:17:10PM -0400, Dan Langille wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Hughes wrote: Where did the 2.x series ports go? We currently use bacula-dir v. 2.4.4 on a linux host to backup our fbsd file servers, but some web research and our own testing on our fbsd test file server found that bacula-client v. 3.x is completely incompatible with bacula-dir 2.5.x. Have you raised this issue on the bacula users mailing list? If so, what is the URL into the archives so we can investigate. Currently our production file servers have the bacula-client v. 2.4.4 port installed, but we would like to be able to port upgrade them and still maintain a 2.4.x series bacula-client. I'm sure that's possible, not trivial, but possible. I have searched through the cvs commits using the online FreeBSD ports search tool, but I found that there is a version jump from bacula-client v. 1.38.x to version 3.x. Yet, we originally installed the 2.4.4 client on our fbsd file servers using a port, so clearly at some point there was a 2.4.4 port. bacula-client is a slave port of bacula-server. Thus, changes to baucla-client version numbers can be gleaned from bacula-server. sysutils/bacula-server is currently 3.0.0 and sysutils/bacula-server-devel is 2.5.42.b2. If you need the 2.x branch, get it from CVS. You'll need both the slave and the master. The latest in the 2.x line of development is actually in bacula-server-devel right now. Perhaps a 2.x port is a good idea. A PR would be useful. And perhaps a repo copy. The versions are backwards for now, but I imagine -devel will be updated in the future to be the latest development release. At that time we can prepare the bacula2 ports which will track the 2.x line of development. -- WXS ___ 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
