Re: [Bacula-users] Windows 2008/Vista 64 bit bacula

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 AAAA record listed. But the FD does not listen on IPv6 (in 
Linux, you can turn it on to make it work, in Windows, IPv6 is not yet 
implemented in the FD). With the Windows firewall turned on, this leads to a 
timeout. With the Windows firewall turned off, bacula finds out about the 
failure of the IPv6 connection quickly, and switches to IPv4.

Four workarounds:

- Turn off the Windows firewall. That will at least verify that we are looking 
at the same problem.
- create alternate DNS name for the client that has just an A record but no 
AAAA record.
- use the IPv4 address instead of a DNS name in the director's Client resource.
- turn off IPv6 everywhere.

My problem also was on 64-bit Windows. I didn't check to see if the firewall on 
32 bit had the same problem.

> -----Original Message-----
> From: Bruno Friedmann [mailto:bruno AT ioda-net DOT ch]
> Sent: Saturday, January 02, 2010 1:16 PM
> To: bacula-users AT lists.sourceforge DOT net
> Subject: Re: [Bacula-users] Windows 2008/Vista 64 bit bacula
> 
> 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 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
> > little job it works fine.
> >
> > The 32bit work always well
> >
> > CIAO
> >
> > 2009/12/30 Firestrm <firestrm AT sonic DOT net>
> >
> >>
> >> 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
> >>>
> >>> Warning: VSS was not initialized
> >>> properly. VSS support is disabled. ERR=An attempt was made to
> reference a
> >>> token that does not exist.
> >>>
> >>>
> >>> Michael
> 
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 
> --
> 
>      Bruno Friedmann
> 
> 
> -----------------------------------------------------------------------
> -------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users