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
> 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
> 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).
Than you.
-------------------------------------------------------------------------
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
