Re: [Bacula-users] Problems with FD connection to SD
Hi, 22.06.2007 13:04,, Llistes Saccharine wrote:: > Hi, > > I have 'Director' and 'Storage' in a server with two ranges of LAN ip's > (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in > 192.168.2.0 range. When I run a Job, the communications with the > 'Director' and the 'client' are OK, but when the 'Client' tries to > connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0 > range. > > Do I have to define in the config files any resource to determine the > route of the connection between 'FD' and 'SD'? I am surprised because > there isn't any problem with the connection between 'Director' and 'FD' > with range 192.168.2.0. That sounds like a 'normal' routing problem. The FD contacts the SD. For that to work, it needs route to the 192.168.1.0 network. Is that set up? Also, it's possible that a firewall on your router blocks these accesses. In case your server is dual-homed in both networks, you will have to try to set up a storage device in the DIR pointing the FDs to the 192.168.1.0 address of your SD. I'm unsure if that works, though - I haven't worked with dual-homed Bacula installations recently. In fact, never :-) Arno Arno > Thanks, > > David > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
En/na tomasz ha escrit: > Llistes Saccharine wrote: > >> Hi, >> >> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's >> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in >> 192.168.2.0 range. When I run a Job, the communications with the >> 'Director' and the 'client' are OK, but when the 'Client' tries to >> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0 >> range. >> >> Do I have to define in the config files any resource to determine the >> route of the connection between 'FD' and 'SD'? I am surprised because >> there isn't any problem with the connection between 'Director' and 'FD' >> with range 192.168.2.0. >> >> Thanks, >> >> David >> > > are you sure sd and dir are listening on IPs from both nets? > ` > > Yes, 'SD'&'DIR' server is listening all interfaces (192.168.1.0/24 and 192.168.2.0/24) and I can connect to Bacula PORT s(9101-9103) using telnet in the 'FD' client. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
Llistes Saccharine wrote: > Hi, > > I have 'Director' and 'Storage' in a server with two ranges of LAN ip's > (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in > 192.168.2.0 range. When I run a Job, the communications with the > 'Director' and the 'client' are OK, but when the 'Client' tries to > connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0 > range. > > Do I have to define in the config files any resource to determine the > route of the connection between 'FD' and 'SD'? I am surprised because > there isn't any problem with the connection between 'Director' and 'FD' > with range 192.168.2.0. > > Thanks, > > David are you sure sd and dir are listening on IPs from both nets? ` -- bEsT rEgArDs| "Confidence is what you have before you tomasz dereszynski | understand the problem." -- Woody Allen TD840-RIPE | - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
David wrote:
> En/na Arno Lehmann ha escrit:
>> Hi,
>>
>> 22.06.2007 13:04,, Llistes Saccharine wrote::
>>
>>> Hi,
>>>
>>> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's
>>> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in
>>> 192.168.2.0 range. When I run a Job, the communications with the
>>> 'Director' and the 'client' are OK, but when the 'Client' tries to
>>> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0
>>> range.
>>>
>>> Do I have to define in the config files any resource to determine the
>>> route of the connection between 'FD' and 'SD'? I am surprised because
>>> there isn't any problem with the connection between 'Director' and 'FD'
>>> with range 192.168.2.0.
>>>
>> Thanks Arno
>>
>>
>>
>> The server in problems only works on 192.168.2.0 range. I could not add
>> a route to 192.168.1.0 because it must be 2 different LAN without
>> connection between them.
>> That sounds like a 'normal' routing problem. The FD contacts the SD.
>> For that to work, it needs route to the 192.168.1.0 network. Is that
>> set up?
>>
>>
> Thanks Arno
>
> The server in problems only works on 192.168.2.0 range. I could not add
> a route to 192.168.1.0 because it must be 2 different LAN without
> connection between them.
>
>> Also, it's possible that a firewall on your router blocks these accesses.
>>
>> In case your server is dual-homed in both networks, you will have to
>> try to set up a storage device in the DIR pointing the FDs to the
>> 192.168.1.0 address of your SD. I'm unsure if that works, though - I
>> haven't worked with dual-homed Bacula installations recently. In fact,
>> never :-)
>>
>>
> I will try this solution, thanks ;) I hope it works.
>
> If anybody have worked with this solution, tell me if it's effective.
>
> Thanks to everyone
>
> David
u need in bacula-sd.conf some like
SDAddresses = {
ip = { addr = 192.168.1.20; port = 9103;}
ip = { addr = 192.168.2.20; port = 9103;}
}
and the same for DIRAddresses in bacula-dir.conf
it works
regards
--
bEsT rEgArDs| "Confidence is what you have before you
tomasz dereszynski | understand the problem." -- Woody Allen
TD840-RIPE |
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
En/na Arno Lehmann ha escrit: > Hi, > > 22.06.2007 13:04,, Llistes Saccharine wrote:: > >> Hi, >> >> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's >> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in >> 192.168.2.0 range. When I run a Job, the communications with the >> 'Director' and the 'client' are OK, but when the 'Client' tries to >> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0 >> range. >> >> Do I have to define in the config files any resource to determine the >> route of the connection between 'FD' and 'SD'? I am surprised because >> there isn't any problem with the connection between 'Director' and 'FD' >> with range 192.168.2.0. >> > Thanks Arno > > > > The server in problems only works on 192.168.2.0 range. I could not add > a route to 192.168.1.0 because it must be 2 different LAN without > connection between them. > That sounds like a 'normal' routing problem. The FD contacts the SD. > For that to work, it needs route to the 192.168.1.0 network. Is that > set up? > > Thanks Arno The server in problems only works on 192.168.2.0 range. I could not add a route to 192.168.1.0 because it must be 2 different LAN without connection between them. > Also, it's possible that a firewall on your router blocks these accesses. > > In case your server is dual-homed in both networks, you will have to > try to set up a storage device in the DIR pointing the FDs to the > 192.168.1.0 address of your SD. I'm unsure if that works, though - I > haven't worked with dual-homed Bacula installations recently. In fact, > never :-) > > I will try this solution, thanks ;) I hope it works. If anybody have worked with this solution, tell me if it's effective. Thanks to everyone David > Arno > > > Arno > > >> Thanks, >> >> David >> >> - >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> ___ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
En/na tomasz ha escrit:
> David wrote:
>
>> En/na Arno Lehmann ha escrit:
>>
>>> Hi,
>>>
>>> 22.06.2007 13:04,, Llistes Saccharine wrote::
>>>
>>>
Hi,
I have 'Director' and 'Storage' in a server with two ranges of LAN ip's
(192.168.1.0/24 and 192.168.2.0/24). The client with problems is in
192.168.2.0 range. When I run a Job, the communications with the
'Director' and the 'client' are OK, but when the 'Client' tries to
connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0
range.
Do I have to define in the config files any resource to determine the
route of the connection between 'FD' and 'SD'? I am surprised because
there isn't any problem with the connection between 'Director' and 'FD'
with range 192.168.2.0.
>>> Thanks Arno
>>>
>>>
>>>
>>> The server in problems only works on 192.168.2.0 range. I could not add
>>> a route to 192.168.1.0 because it must be 2 different LAN without
>>> connection between them.
>>> That sounds like a 'normal' routing problem. The FD contacts the SD.
>>> For that to work, it needs route to the 192.168.1.0 network. Is that
>>> set up?
>>>
>>>
>>>
>> Thanks Arno
>>
>> The server in problems only works on 192.168.2.0 range. I could not add
>> a route to 192.168.1.0 because it must be 2 different LAN without
>> connection between them.
>>
>>
>>> Also, it's possible that a firewall on your router blocks these accesses.
>>>
>>> In case your server is dual-homed in both networks, you will have to
>>> try to set up a storage device in the DIR pointing the FDs to the
>>> 192.168.1.0 address of your SD. I'm unsure if that works, though - I
>>> haven't worked with dual-homed Bacula installations recently. In fact,
>>> never :-)
>>>
>>>
>>>
>> I will try this solution, thanks ;) I hope it works.
>>
>> If anybody have worked with this solution, tell me if it's effective.
>>
>> Thanks to everyone
>>
>> David
>>
>
>
> u need in bacula-sd.conf some like
>
> SDAddresses = {
> ip = { addr = 192.168.1.20; port = 9103;}
> ip = { addr = 192.168.2.20; port = 9103;}
> }
>
> and the same for DIRAddresses in bacula-dir.conf
>
> it works
>
> regards
>
>
>
Thanks Tomas.
I put this new resources in 'DIR' conf and 'SD' conf but when I reload
the configuration I obtain this error:
22-Jun 13:48 bacula-dir: ERROR TERMINATION at address_conf.c:506
Config error: Can't add hostname(192.168.1.250) and port() to addrlist
(the old style addresses cannot be mixed with new style)
'SD' and 'DIR' version are 2.0.3. I search in the manual for the correct
syntax but I obtain the same syntax I put in conf files.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
David wrote:
> En/na tomasz ha escrit:
>> David wrote:
>>
>>> En/na Arno Lehmann ha escrit:
>>>
Hi,
22.06.2007 13:04,, Llistes Saccharine wrote::
> Hi,
>
> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's
> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in
> 192.168.2.0 range. When I run a Job, the communications with the
> 'Director' and the 'client' are OK, but when the 'Client' tries to
> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0
> range.
>
> Do I have to define in the config files any resource to determine the
> route of the connection between 'FD' and 'SD'? I am surprised because
> there isn't any problem with the connection between 'Director' and 'FD'
> with range 192.168.2.0.
>
>
Thanks Arno
The server in problems only works on 192.168.2.0 range. I could not add
a route to 192.168.1.0 because it must be 2 different LAN without
connection between them.
That sounds like a 'normal' routing problem. The FD contacts the SD.
For that to work, it needs route to the 192.168.1.0 network. Is that
set up?
>>> Thanks Arno
>>>
>>> The server in problems only works on 192.168.2.0 range. I could not add
>>> a route to 192.168.1.0 because it must be 2 different LAN without
>>> connection between them.
>>>
>>>
Also, it's possible that a firewall on your router blocks these accesses.
In case your server is dual-homed in both networks, you will have to
try to set up a storage device in the DIR pointing the FDs to the
192.168.1.0 address of your SD. I'm unsure if that works, though - I
haven't worked with dual-homed Bacula installations recently. In fact,
never :-)
>>> I will try this solution, thanks ;) I hope it works.
>>>
>>> If anybody have worked with this solution, tell me if it's effective.
>>>
>>> Thanks to everyone
>>>
>>> David
>>>
>>
>> u need in bacula-sd.conf some like
>>
>> SDAddresses = {
>> ip = { addr = 192.168.1.20; port = 9103;}
>> ip = { addr = 192.168.2.20; port = 9103;}
>> }
>>
>> and the same for DIRAddresses in bacula-dir.conf
>>
>> it works
>>
>> regards
>>
>>
>>
> Thanks Tomas.
>
> I put this new resources in 'DIR' conf and 'SD' conf but when I reload
> the configuration I obtain this error:
> 22-Jun 13:48 bacula-dir: ERROR TERMINATION at address_conf.c:506
> Config error: Can't add hostname(192.168.1.250) and port() to addrlist
> (the old style addresses cannot be mixed with new style)
>
> 'SD' and 'DIR' version are 2.0.3. I search in the manual for the correct
> syntax but I obtain the same syntax I put in conf files.
>
>
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
Director {# define myself
Name = myserver-dir
DIRAddresses = {
ip = { addr = 192.168.1.250; port = 9101;}
ip = { addr = 192.168.2.250; port = 9101;}}
QueryFile = "/usr/local/share/bacula/query.sql"
WorkingDirectory = "/var/db/bacula"
PidDirectory = "/var/run"
Maximum Concurrent Jobs = 1
Password = "xx" # Console password
Messages = Daemon
}
this is my part of this config (with your IPs)
im running bacula 2.0.3 without problem at all
and SD
Storage { # definition of myself
Name = myserver-sd
SDAddresses = {
ip = { addr = 192.168.1.250; port = 9101;}
ip = { addr = 192.168.2.250; port = 9101;}}
}
WorkingDirectory = "/var/db/bacula"
Pid Directory = "/var/run"
Maximum Concurrent Jobs = 20
}
are u sure u r not filtering this traffic or something??
--
bEsT rEgArDs| "Confidence is what you have before you
tomasz dereszynski | understand the problem." -- Woody Allen
TD840-RIPE |
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with FD connection to SD
tomasz wrote:
> David wrote:
>> En/na tomasz ha escrit:
>>> David wrote:
>>>
En/na Arno Lehmann ha escrit:
> Hi,
>
> 22.06.2007 13:04,, Llistes Saccharine wrote::
>
>
>> Hi,
>>
>> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's
>> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in
>> 192.168.2.0 range. When I run a Job, the communications with the
>> 'Director' and the 'client' are OK, but when the 'Client' tries to
>> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0
>> range.
>>
>> Do I have to define in the config files any resource to determine the
>> route of the connection between 'FD' and 'SD'? I am surprised because
>> there isn't any problem with the connection between 'Director' and 'FD'
>> with range 192.168.2.0.
>>
>>
> Thanks Arno
>
>
>
> The server in problems only works on 192.168.2.0 range. I could not add
> a route to 192.168.1.0 because it must be 2 different LAN without
> connection between them.
> That sounds like a 'normal' routing problem. The FD contacts the SD.
> For that to work, it needs route to the 192.168.1.0 network. Is that
> set up?
>
>
>
Thanks Arno
The server in problems only works on 192.168.2.0 range. I could not add
a route to 192.168.1.0 because it must be 2 different LAN without
connection between them.
> Also, it's possible that a firewall on your router blocks these accesses.
>
> In case your server is dual-homed in both networks, you will have to
> try to set up a storage device in the DIR pointing the FDs to the
> 192.168.1.0 address of your SD. I'm unsure if that works, though - I
> haven't worked with dual-homed Bacula installations recently. In fact,
> never :-)
>
>
>
I will try this solution, thanks ;) I hope it works.
If anybody have worked with this solution, tell me if it's effective.
Thanks to everyone
David
>>> u need in bacula-sd.conf some like
>>>
>>> SDAddresses = {
>>> ip = { addr = 192.168.1.20; port = 9103;}
>>> ip = { addr = 192.168.2.20; port = 9103;}
>>> }
>>>
>>> and the same for DIRAddresses in bacula-dir.conf
>>>
>>> it works
>>>
>>> regards
>>>
>>>
>>>
>> Thanks Tomas.
>>
>> I put this new resources in 'DIR' conf and 'SD' conf but when I reload
>> the configuration I obtain this error:
>> 22-Jun 13:48 bacula-dir: ERROR TERMINATION at address_conf.c:506
>> Config error: Can't add hostname(192.168.1.250) and port() to addrlist
>> (the old style addresses cannot be mixed with new style)
>>
>> 'SD' and 'DIR' version are 2.0.3. I search in the manual for the correct
>> syntax but I obtain the same syntax I put in conf files.
>>
>>
>> -
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>
> Director {# define myself
> Name = myserver-dir
> DIRAddresses = {
> ip = { addr = 192.168.1.250; port = 9101;}
> ip = { addr = 192.168.2.250; port = 9101;}}
> QueryFile = "/usr/local/share/bacula/query.sql"
> WorkingDirectory = "/var/db/bacula"
> PidDirectory = "/var/run"
> Maximum Concurrent Jobs = 1
> Password = "xx" # Console password
> Messages = Daemon
> }
>
>
>
> this is my part of this config (with your IPs)
> im running bacula 2.0.3 without problem at all
>
> and SD
>
>
> Storage { # definition of myself
> Name = myserver-sd
> SDAddresses = {
> ip = { addr = 192.168.1.250; port = 9101;}
> ip = { addr = 192.168.2.250; port = 9101;}}
> }
> WorkingDirectory = "/var/db/bacula"
> Pid Directory = "/var/run"
> Maximum Concurrent Jobs = 20
> }
>
>
>
> are u sure u r not filtering this traffic or something??
>
of course ports for SD should be 9103
sorry
--
bEsT rEgArDs| "Confidence is what you have before you
tomasz dereszynski | understand the problem." -- Woody Allen
TD840-RIPE |
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://source
Re: [Bacula-users] Problems with FD connection to SD
En/na tomasz ha escrit:
> tomasz wrote:
>
>> David wrote:
>>
>>> En/na tomasz ha escrit:
>>>
David wrote:
> En/na Arno Lehmann ha escrit:
>
>
>> Hi,
>>
>> 22.06.2007 13:04,, Llistes Saccharine wrote::
>>
>>
>>
>>> Hi,
>>>
>>> I have 'Director' and 'Storage' in a server with two ranges of LAN ip's
>>> (192.168.1.0/24 and 192.168.2.0/24). The client with problems is in
>>> 192.168.2.0 range. When I run a Job, the communications with the
>>> 'Director' and the 'client' are OK, but when the 'Client' tries to
>>> connect to the 'SD' it tries it with the 'SD' server IP on 192.168.1.0
>>> range.
>>>
>>> Do I have to define in the config files any resource to determine the
>>> route of the connection between 'FD' and 'SD'? I am surprised because
>>> there isn't any problem with the connection between 'Director' and 'FD'
>>> with range 192.168.2.0.
>>>
>>>
>>>
>> Thanks Arno
>>
>>
>>
>> The server in problems only works on 192.168.2.0 range. I could not add
>> a route to 192.168.1.0 because it must be 2 different LAN without
>> connection between them.
>> That sounds like a 'normal' routing problem. The FD contacts the SD.
>> For that to work, it needs route to the 192.168.1.0 network. Is that
>> set up?
>>
>>
>>
>>
> Thanks Arno
>
> The server in problems only works on 192.168.2.0 range. I could not add
> a route to 192.168.1.0 because it must be 2 different LAN without
> connection between them.
>
>
>
>> Also, it's possible that a firewall on your router blocks these accesses.
>>
>> In case your server is dual-homed in both networks, you will have to
>> try to set up a storage device in the DIR pointing the FDs to the
>> 192.168.1.0 address of your SD. I'm unsure if that works, though - I
>> haven't worked with dual-homed Bacula installations recently. In fact,
>> never :-)
>>
>>
>>
>>
> I will try this solution, thanks ;) I hope it works.
>
> If anybody have worked with this solution, tell me if it's effective.
>
> Thanks to everyone
>
> David
>
>
u need in bacula-sd.conf some like
SDAddresses = {
ip = { addr = 192.168.1.20; port = 9103;}
ip = { addr = 192.168.2.20; port = 9103;}
}
and the same for DIRAddresses in bacula-dir.conf
it works
regards
>>> Thanks Tomas.
>>>
>>> I put this new resources in 'DIR' conf and 'SD' conf but when I reload
>>> the configuration I obtain this error:
>>> 22-Jun 13:48 bacula-dir: ERROR TERMINATION at address_conf.c:506
>>> Config error: Can't add hostname(192.168.1.250) and port() to addrlist
>>> (the old style addresses cannot be mixed with new style)
>>>
>>> 'SD' and 'DIR' version are 2.0.3. I search in the manual for the correct
>>> syntax but I obtain the same syntax I put in conf files.
>>>
>>>
>>> -
>>> This SF.net email is sponsored by DB2 Express
>>> Download DB2 Express C - the FREE version of DB2 express and take
>>> control of your XML. No limits. Just data. Click to get it now.
>>> http://sourceforge.net/powerbar/db2/
>>> ___
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>>>
>>>
>>
>> Director {# define myself
>> Name = myserver-dir
>> DIRAddresses = {
>> ip = { addr = 192.168.1.250; port = 9101;}
>> ip = { addr = 192.168.2.250; port = 9101;}}
>> QueryFile = "/usr/local/share/bacula/query.sql"
>> WorkingDirectory = "/var/db/bacula"
>> PidDirectory = "/var/run"
>> Maximum Concurrent Jobs = 1
>> Password = "xx" # Console password
>> Messages = Daemon
>> }
>>
>>
>>
>> this is my part of this config (with your IPs)
>> im running bacula 2.0.3 without problem at all
>>
>> and SD
>>
>>
>> Storage { # definition of myself
>> Name = myserver-sd
>> SDAddresses = {
>> ip = { addr = 192.168.1.250; port = 9101;}
>> ip = { addr = 192.168.2.250; port = 9101;}}
>> }
>> WorkingDirectory = "/var/db/bacula"
>> Pid Directory = "/var/run"
>> Maximum Concurrent Jobs = 20
>> }
>>
>>
>>
>> are u sure u r not filtering this traffic or something??
>>
>>
> of course ports for SD should be 9103
> sorry
>
>
It is solved!
It was my fault. I still had the PORT resource (Di
