Re: [Bacula-users] Problem Bacula windows binarys

2013-08-16 Thread Kern Sibbald
Hello, The Bacula Enterprise Demo binaries are not meant for production use and they only work as a part of the demo, which means that they are not compatible with any Bacula component whether it be a community version or an Enterprise version. Kern On 07/31/2013 11:53 AM, Felix Geschwindner wr

Re: [Bacula-users] Problem Bacula windows binarys

2013-07-31 Thread Martin Simmons
> On Wed, 31 Jul 2013 11:53:28 +0200, Felix Geschwindner said: > ... > bconsole.conf (Linux client) > > Director { > Name = backup02-dir > address = backup02 > Password = "1234" > } > > > bacula-dir.conf > > Director { > Name = backup02-dir > QueryFile = "/etc/bacula/scripts/query

Re: [Bacula-users] Problem Bacula windows binarys

2013-07-31 Thread Téïcée Bacula
Hello Felix Actually you didn't get the right packages. The demo version of Bacula Enterprise is not compatible with the community version (neither with the real Bacula Enterprise version itself). Demo packages are just for demo purposes. You may either buy the Windows binary packages on Bacula

Re: [Bacula-users] Problem Bacula windows binarys

2013-07-31 Thread Kevin B. Zimmerman
I'm running v5.2.5 on my server, and ran into a similar problem when setting up my Windows clients. Installing v5.2.10 of the Bacula client on the Windows box resolved it for me. Are you sure you've listed the right client version? I don't see it on the list of Win files at Sourceforge. Where

[Bacula-users] Problem Bacula windows binarys

2013-07-31 Thread Felix Geschwindner
Hey Guys, I'm close to getting nuts on my bacula deployment. Hopefully someone of you can pull me out of it! Bacula Version: 5.2.6 Our environment consists of 3 Linux Servers that are backed up on a nightly basis. Server1 and Server2 copy their files via FD to Server3 which runs the DIR and SD