Bacula-users

Re: [Bacula-users] Different IP for the same SD

2008-11-05 15:12:51
Subject: Re: [Bacula-users] Different IP for the same SD
From: "Jose Ildefonso Camargo Tolosa" <ildefonso.camargo AT gmail DOT com>
To: "Dan Langille" <dan AT langille DOT org>
Date: Thu, 6 Nov 2008 15:39:28 +1930
Hi!

On Thu, Nov 6, 2008 at 8:16 AM, Dan Langille <dan AT langille DOT org> wrote:
On Nov 6, 2008, at 7:12 AM, Jose Ildefonso Camargo Tolosa wrote:

Hi!

On Thu, Nov 6, 2008 at 12:35 AM, Dan Langille <dan AT langille DOT org> wrote:
Here is how I do different IP for the same SD.  In my case, remote clients
access the SD via the gateway (public IP address which is forwarded
from my gateway to the SD) and local clients access the local IP address
(in the 192.168. block).

I have slightly altered this config from my actual, but it should illustrate how
to do this.

>>From bacula-dir.conf

Storage {
 Name       = DLTRemoteTLS
 Address    = storage1.example.org
 SDPort     = 9103
 Device     = DLT
 Media Type = DLT
}

# Definition of DLT tape storage device
Storage {
 Name       = DLT
 Address    = bacula.example.org
 SDPort     = 9103

 Device     = DLT
 Media Type = DLT
}

That's it.  Note that both Storage resources refer to the same Device.
Both Storage resources have different Address values.  Use FQDN
and point each to different IP addresses.

In my case, bacula.example.org points to 192.168.1.12 and
DLTRemoteTLD refers to storage1.example.org, which is a public IP address.

Then in bacula-sd.conf, I define the DLT device.

Device {
 Name                    = DLT
 Description             = QUANTUM DLT7000 1624
 Media Type              = DLT
 Archive Device          = /dev/nsa0
}

Nothing special.  But it's clever.  Someone else showed me how to do it.

Does that give you something to think about?

Sure it does: docs needs updating!

In what way?  I already stated this was documented. Here. I found it for you:

  http://www.bacula.org/en/rel-manual/Dealing_with_Firewalls.html

I just read it... it won't work, because I have all the servers en the same network.  The best bet is to "play around" with *local* name resolution (ie, /etc/hosts or lmhosts), which can prove to be annoying.

Also, according to the doc you just gave, it says that using two different Storage resources, no longer works:

"The following discussion was originally written by Jesse Guardiani because he has 'internal' and 'external' requiring the Director and the Client to use different IP addresses. His original solution was to define two different Storage resources in the Director's conf file each pointing to the same Storage daemon but with different IP addresses. In Bacula 1.38.x this no longer works, because Bacula makes a one-to-one association between a Storage daemon resource and a Device (such as an Autochanger). As a consequence, I have modified his original text to a method that I believe will work, but is as of yet untested (KES - July 2006)."

Duh....
 


The thing is: can you run two backup jobs at the same time, one on each storage address? (I think there should be no problem).

I'm sure you can.    It is merely a concurrent job.  Why ask when you can try?  :)

Because it is easier? :)  It was almost midnight by the time I wrote that.
 


--
Dan Langille
http://langille.org/


 Ildefonso Camargo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>