Re: [Bacula-users] no upgrade path for windows servers?
On 2/14/2011 7:25 PM, Dan Langille wrote: On 2/14/2011 4:52 PM, Bob Hetzel wrote: In summary, Dir and FD need to be at the same version, FD version should be really close if you want to be sure you can use newer features, bug fixes, etc. Did you mean Dir and SD? Dir and SD must be a the same level. FD can lag behind. In short: DIR = SD = FD Oops. But what I meant to say was that FD can only lag behind within certain limits. Unfortunately, nobody is testing and documenting those limits before each version is released, from what I can tell. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Jeff Shanholtz schrieb: ... Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) don't know about the other things, but newer clients can't connect to an older director. The other way is ok, new director and older clients. Ralf Recently, I've seen problems both ways. On my 5.0.3 version director I can no longer use v2.4.3 windows FD clients. The 5.0.x clients also won't work with older directors. Normally this hasn't been the case with every upgrade I've dealt with over the last 4 yrs or so, but a few changes were made to the protocol to add abilities in the 5.0.0 version. Additionally, you need the SD and Dir to be at the exact same version. In summary, Dir and FD need to be at the same version, FD version should be really close if you want to be sure you can use newer features, bug fixes, etc. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
On 2/14/2011 4:52 PM, Bob Hetzel wrote: In summary, Dir and FD need to be at the same version, FD version should be really close if you want to be sure you can use newer features, bug fixes, etc. Did you mean Dir and SD? Dir and SD must be a the same level. FD can lag behind. In short: DIR = SD = FD -- Dan Langille - http://langille.org/ -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Ever tried colinux in this configuration? Sent from my iPhone On 10/02/2011, at 18:43, Randy Katz rk...@simplicityhosting.com wrote: On 2/9/2011 3:49 PM, Jeff Shanholtz wrote: I see that server support has been pulled from the installer. I have 3.0.1 installed and configured on my windows 2003 server and it is working great. Even though there isn’t an installer for this configuration, is it possible to manually replace my 3.0.1 binaries with 5.0.3 binaries for storage and director services? I saw something about cross compiling but I don’t currently have a linux configuration in which to do this. Are the installerless binaries available anywhere for manual configuration or am I stuck with 3.0.1 forever? Has the storage and director code taken a step backwards with regard to the windows platform or was their removal done simply to remove a pain point for users and thus reduce support related inquiries? Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I’m crossing my fingers that the client “status” window will be a little more informative than just a big blank window like it is in 3.0.1. :) If you do not want to port and make a compilation of 5.0.3 on Windows it might be a good time for you to install VirtualBox http://www.virtualbox.org/ , create a virtual machine, and install a linux distro you like (debian is widely used by the bacula people, I use CentOS some libraries are a problem when it comes to gui stuff but the base install (fd,sd,dir,bconsole) work well), compile/install bacula and when you are comfortable with it deploy a Linux machine. Regards, Randy -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
On 2/9/2011 11:40 PM, Marcello Romani wrote: Il 10/02/2011 08:14, Ralf Gross ha scritto: Jeff Shanholtz schrieb: ... Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) don't know about the other things, but newer clients can't connect to an older director. The other way is ok, new director and older clients. Ralf -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users I have a 5.0.3 director and a mixture of 2.4.x and 5.0.x storage daemons, and all works fine. Being on debian, I had to enable lenny-backports to install bacula 5.0.x on the server, otherwise the 2.4.x version provided by the stable branch of debian wouldn't work with the 5.0.x client (i.e. file daemon) provided by ubuntu 10.04. Oh, I assumed all the debian based users were compiling from source. I am sure anyone new to bacula would want to run the latest version. At any rate easy enough to compile from source, right? Not sure about gui and library support though, I am sure someone can comment further, also ubuntu is essentially debian, right? Regards, Randy -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Il 10/02/2011 09:00, Randy Katz ha scritto: On 2/9/2011 11:40 PM, Marcello Romani wrote: Il 10/02/2011 08:14, Ralf Gross ha scritto: Jeff Shanholtz schrieb: ... Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) don't know about the other things, but newer clients can't connect to an older director. The other way is ok, new director and older clients. Ralf -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users I have a 5.0.3 director and a mixture of 2.4.x and 5.0.x storage daemons, and all works fine. Being on debian, I had to enable lenny-backports to install bacula 5.0.x on the server, otherwise the 2.4.x version provided by the stable branch of debian wouldn't work with the 5.0.x client (i.e. file daemon) provided by ubuntu 10.04. Oh, I assumed all the debian based users were compiling from source. I I prefer to stay with distro packages unless some important features exist in newer versions. Even then, I assume backports are better integrated with the OS than any self-compiled package. am sure anyone new to bacula would want to run the latest version. At any rate easy enough to compile from source, right? Not sure about gui and library support Easy or not, compiling the package means IMHO adding unnecessary complexity to the task of learning bacula, which is challenging enough in and of itself. though, I am sure someone can comment further, also ubuntu is essentially debian, right? Yes, but much less conservative (they pull from unstable IIRC). That's why you get bacula 2.4.x with debian stable and 5.0.x with Ubuntu. Regards, Randy -- Marcello Romani -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Il 10/02/2011 08:59, James Harper ha scritto: Ever tried colinux in this configuration? http://www.colinux.org Amazing! Although I don't see why bother running a stable OS under an unstable one instead of the other way around... :-) -- Marcello Romani -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Il 10/02/2011 08:59, James Harper ha scritto: Ever tried colinux in this configuration? http://www.colinux.org Amazing! Although I don't see why bother running a stable OS under an unstable one instead of the other way around... :-) If you're already running windows in the first place then all bets are off :) James -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
I appreciate all the responses so far, but switching to linux is not currently a consideration. Again, are the director and storage windows 5.0.3 binaries inherently less stable/buggier/worse than they are in 3.0.x? I'm trying to understand if it would be a bad idea to even attempt to get these binaries in comparison to continuing to use 3.0.x binaries. I suppose, based on one reply, I ought to just contact Bacula Systems to see if they will provide binaries for me, although I don't see how to contact them (other than a sales inquiry). -Original Message- From: James Harper [mailto:james.har...@bendigoit.com.au] Sent: Thursday, February 10, 2011 1:45 AM To: Marcello Romani; bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] no upgrade path for windows servers? Il 10/02/2011 08:59, James Harper ha scritto: Ever tried colinux in this configuration? http://www.colinux.org Amazing! Although I don't see why bother running a stable OS under an unstable one instead of the other way around... :-) If you're already running windows in the first place then all bets are off :) James -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] no upgrade path for windows servers?
I see that server support has been pulled from the installer. I have 3.0.1 installed and configured on my windows 2003 server and it is working great. Even though there isn't an installer for this configuration, is it possible to manually replace my 3.0.1 binaries with 5.0.3 binaries for storage and director services? I saw something about cross compiling but I don't currently have a linux configuration in which to do this. Are the installerless binaries available anywhere for manual configuration or am I stuck with 3.0.1 forever? Has the storage and director code taken a step backwards with regard to the windows platform or was their removal done simply to remove a pain point for users and thus reduce support related inquiries? Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Jeff Shanholtz schrieb: ... Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) don't know about the other things, but newer clients can't connect to an older director. The other way is ok, new director and older clients. Ralf -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
On 2/9/2011 3:49 PM, Jeff Shanholtz wrote: I see that server support has been pulled from the installer. I have 3.0.1 installed and configured on my windows 2003 server and it is working great. Even though there isn't an installer for this configuration, is it possible to manually replace my 3.0.1 binaries with 5.0.3 binaries for storage and director services? I saw something about cross compiling but I don't currently have a linux configuration in which to do this. Are the installerless binaries available anywhere for manual configuration or am I stuck with 3.0.1 forever? Has the storage and director code taken a step backwards with regard to the windows platform or was their removal done simply to remove a pain point for users and thus reduce support related inquiries? Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) If you do not want to port and make a compilation of 5.0.3 on Windows it might be a good time for you to install VirtualBox http://www.virtualbox.org/ , create a virtual machine, and install a linux distro you like (debian is widely used by the bacula people, I use CentOS some libraries are a problem when it comes to gui stuff but the base install (fd,sd,dir,bconsole) work well), compile/install bacula and when you are comfortable with it deploy a Linux machine. Regards, Randy -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] no upgrade path for windows servers?
Il 10/02/2011 08:14, Ralf Gross ha scritto: Jeff Shanholtz schrieb: ... Finally, I assume that if I stay with 3.0.1 on the server, I can upgrade clients to 5.0.3, correct? I'm crossing my fingers that the client status window will be a little more informative than just a big blank window like it is in 3.0.1. :) don't know about the other things, but newer clients can't connect to an older director. The other way is ok, new director and older clients. Ralf -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users I have a 5.0.3 director and a mixture of 2.4.x and 5.0.x storage daemons, and all works fine. Being on debian, I had to enable lenny-backports to install bacula 5.0.x on the server, otherwise the 2.4.x version provided by the stable branch of debian wouldn't work with the 5.0.x client (i.e. file daemon) provided by ubuntu 10.04. -- Marcello Romani -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
