On 9/9/07, Arno Lehmann <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> 10.09.2007 05:12,, Hydro Meteor wrote::
> > Hello,
> >
> > In Chapter 6.3.4 of the Bacula User's Guide, with regard to naming
> > resources, the Guide states that:
> >
> >     Each of your Bacula components must have a unique name.
> >
> >
> > This is especially necessary when backing up a fleet machines.
> >
> > I didn't see any similar requirements that the Address fields of
> > resources also be unique. Can anyone confirm this? For example, would
> > the following (in the bacula-dir.conf file) have any conflicts?
> >
> >     # Client (File Services) to backup
> >     Client {
> >       Name = myunique-machine-name-1
> >       Address = 192.168.1.25 <http://192.168.1.25>
> >       FDPort = 9102
> >       Catalog = MyCatalog
> >       Password = "YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY"
> >     # password for FileDaemon
> >       File Retention = 30 days            # 30 days
> >       Job Retention = 6 months            # six months
> >       AutoPrune = yes                     # Prune expired Jobs/Files
> >     }
> >
> >
> > and
> >
> >     # Client (File Services) to backup
> >     Client {
> >       Name = myunique-machine-name-2
> >       Address = 192.168.1.25 <http://192.168.1.25>
> >       FDPort = 9102
> >       Catalog = MyCatalog
> >       Password = "YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY"
> >     # password for FileDaemon
> >       File Retention = 30 days            # 30 days
> >       Job Retention = 6 months            # six months
> >       AutoPrune = yes                     # Prune expired Jobs/Files
> >     }
> >
> >
> > As much as it would be ideal to use a FQDN for the Address fields, there
> > are some scenarios where this isn't possible and there is a concern from
> > my colleague, about a collision in the Address fields. Hopefully as
> > interpreted from the User's Guid, the uniqueness of the Name fields is
> > all that's required (but better to check ahead of time to be safe than
> > sorry later).
>
> I think what you intend to do would work. It's even a procedure I
> suggested a few times, and nobody complained that it didn't work :-)
>
> Although, in most cases, I suspect you won't need this sort of setup.
>
> Would yo mind explaining why you think you need this?


Hi Arno,

Thank you for your helpful response to my question. No worries, I don't mind
explaining. There are situations where, among a fleet of machines that are
distributed physically, these machines may be sitting behind their routers
(with stateful firewalls) whereby the machines need to have their own static
IP address issued by the router on the subnet of their LAN (e.g.,
192.168.0.25) but the routers themselves may have WAN addresses that are
dynamic. Using a dynamic DNS service, the routers can be reached globally
and then since the machines on their LAN have a static IP address, we can
use Network Address Translation (NAT) and port forwarding to reach these
machines (e.g., run a Bacula Director on a machine in Brussels and speak to
a Bacula File Daemon running on a machine in Montreal where the machine in
Montreal courtesy of NAT / Port forwarding). The machine in Montreal will
not be capable of true reverse DNS since its IP address is static but in the
router's LAN's subnet. And this is the problem since Bacula uses the
gethostbyname() function that requires a true reverse DNS lookup. There may
be more sophisticated routers now that can do some tricks to work around
this problem but I haven't had time to look into that yet and I have to
allow for a lower common denominator that some machines in given locations
may not always have a more sophisticated DNS system to then work around the
gethostbyname() function of Bacula that wants true reverse DNS to work on
that machine! In this scenario, it would be possible for two different
physical machines to have, conceivably, the same LAN-based IP address (such
as 192.168.0.25 as given in the example above) and therefore my concern
about  uniqueness in the Address field. The Name field most certainly can be
unique (there are many ways to create a global namespace that virtually
eliminates the odds of a namespace collision).

Cheers,

-H




Arno
>
> --
> Arno Lehmann
> IT-Service Lehmann
> www.its-lehmann.de
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to