FTR: On many, many Windows machines I've had to add port 9102 (and 9101
depending) to the Exceptions under Windows Firewall, in order to
circumvent this type of bug with bacula-fd.
--
Shawn Qureshi
Artemide, Inc.
IT Specialist
On Sun, 2010-01-03 at 21:04 -0500, Dan Langille wrote:
> Kevin Ke
Kevin Keane wrote:
> Oh yes, that was me. Ultimately, it's a bug in bacula; it has some
> inconsistent default values: by default, the director tries to connect on
> IPv6 when the machine has an record listed. But the FD does not listen
> on IPv6 (in Linux, you can turn it on to make it wo
#x27;t check to see if the firewall on
32 bit had the same problem.
> -Original Message-
> From: Bruno Friedmann [mailto:br...@ioda-net.ch]
> Sent: Saturday, January 02, 2010 1:16 PM
> To: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Windows 2008/Vista
There was a thread some week ago (two or three) about firewall in windows64bits
which cause trouble (also related to ipv6)
I think you can find some info by searching the ML.
Sorry to not be more precise.
On 12/31/2009 11:03 AM, Carlo Filippetto wrote:
> Hi,
> there are 2 different clients in the
Hi,
there are 2 different clients in the 3.0.3, one for 64bit and one for 32bit.
(good for Winzoz 2008).
I have both, and they work well with VSS..
The problem that I have, and I'm trying to torubleshoot is that the 64bit
fail in full backup after some hours of work, instead if I tried to run a
li
What version of the client are you running? I'm running the 64-bit 3.0.3
client as 64bit VSS is not supported by the 32 bit client.
Michael Da Cova wrote:
>
> Hi all
>
> Has anyone got Bacula windows client supporting VSS on Windows 2008/Vista
> 64
> bit Bacula
>
> Reminder I get
>
> Warni
Hi all
Has anyone got Bacula windows client supporting VSS on Windows 2008/Vista 64
bit Bacula
Reminder I get
Warning: VSS was not initialized
properly. VSS support is disabled. ERR=An attempt was made to reference a
token that does not exist.
Michael
--
