See below -->> On Jan 6, 2007, at 10:25 PM, Charles Galpin wrote:
> Hi > >> On Jan 1, 2007, at 9:45 PM, Charles Galpin wrote: > >>> I keep getting a network error when trying to do a full backup of my >>> mac. This is over wireless, but I don't get any network errors doing >>> anything else. > > > On Jan 2, 2007, at 12:33 AM, Charles Galpin wrote: > >> Well, I tried backing up a Windows XP laptop (bacula 1.38.10) over >> both wireless and wired (100Mbs) and it fails too. So I guess I need >> to test the server's network connection, but I'm not showing any >> interface errors and haven't seen any networking problems with it >> before. > > > On Jan 2, 2007, at 12:49 AM, Erich Prinz wrote: >> Sounds like an issue with your switch/router/wireless access point >> dumping the connection. >> >> Can you drop a simple switch in place and by-pass the existing >> unit to test? > > After replacing the switch I can backup both laptops with a wired > connection, thanks. That's good news. > > I'm still concerned that bacula doesn't seem to handle network > errors that well. Even after replacing the switch, I still couldn't > backup over wireless, and thats how these machines access the > network. They won't get backed up very often if I have to plug them > into a wired connection. Bacula handles it quite nicely actually. It sends an email to warn of an issue, waits patiently for the alloted period of time while making attempts to contact the client, then exits without a hitch when the time is up. We can't expect Bacula to resolve our networking issues! > > Are there any configuration options that might help it handle > whatever network problem it's exposing? Maybe longer timeouts or > additional retries? YES! Two things: 1. Set the Heartbeat option in the client section for the laptops in the bacula-dir configuration file and in the SD config file. Bacula's default is set to time out based on a LAN environment. When the FD <--> SD is talking over a WAN segment, it is too slow for the default setting and the jobs terminate. I had this very issue when first setting up Bacula - 99% of what I backup are remote clients over a WAN. Adding the Heartbeat option completely cleared that issue up. The only times there is an issue now is when a client is off line. I've not even had so much as a FD hang - it's been bullet proof. 2. One other thing to check is your DNS/IP configuration. If you're not running DNS in your environment, make sure the client machines have fixed IP addresses in the TCP/IP settings for Airport. Those obviously need to match each client config settings in the bacula- dir.conf file. HTH > > thanks > charles > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
