Re: [Bacula-users] client connect to storage daemon problem

My bacula-dir, bacula-fd and bacula-sd is on a 1G network. The server I am trying to backup is on a 10G network but both the bacula server and client is connected to a private zone (private vlan) to a switch (10G). I want to be able to use the private network to back-up the client because it will be faster (10G). Looks like my server is able to contact the client on port 9102 but the client is unable to talk to the sd on the bacula server on port 9103 through the private network probably because my sd daemon is on a different network (1G).

How do I have my sd daemon listen to two networks (1G and Private) to make this work?

Any help is appreciated.

Thank you.

URao

From: Radosław Korzeniewski [mailto:radoslaw AT korzeniewski DOT net]
Sent: Monday, September 16, 2013 10:05 AM
To: Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC]
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] client connect to storage daemon problem

Hello,

2013/9/13 Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC] <uthra.r.rao AT nasa DOT gov>

I am trying to back-up a client on a 10G private network. The storage daemon is on 1G network and works with other clients on that network. I am now trying to add a client on a 10G network. I was able to connect to the client from the bconsole on the server. Port 9103 is open on the server and port 9102 is open on the client.

Could you show us your Storage Resource definitions in bacula-dir.conf file and your IP addresses of your "private" and "public" networks interfaces, please.

When I try to schedule a full backup I see the following message in the bsonsole:

“7827 Full ****.2013-09-13_16.30.23_03 is waiting for Client ***-fd to connect to Storage jukebox”

Then the job fails with this report:

13-Sep 15:31 **** JobId 7823: Fatal error: Authorization key rejected by Storage daemon.

Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000 for help.

13-Sep 15:31 ***-fd JobId 7823: Fatal error: Failed to authenticate Storage daemon.

So looks like I am having problems with the client talking to the storage daemon that is not on the private 10G network. In other words how do I get the storage daemon talk to two different networks?

If anybody has any solution to this I would really appreciate it.

The solution depends on what is your current Storage configuration and what are your requirements.

It is plausible that you will need to define another Storage resource pointed to the current SD.

best regards

--
Radosław Korzeniewski
radoslaw AT korzeniewski DOT net

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users