Good morning, my fine Bacula-using friends!  ;)

I recently replaced a dying hard drive in my Bacula backup server. (Got warnings from SMART, and it seemed prudent to replace it before it died completely.) I went from Fedora Core 3 for the old install to CentOS 4 on the new install. I rebuilt an RPM from source RPM, like so:
* Install a basic CentOS 4.0
* Install the dependencies:
% yum install mysql-devel atk-devel pango-devel gtk2-devel libgnomeui-devel ORBit2-devel libart_lgpl-devel libbonobo-devel libbonoboui-devel bonobo-activation-devel GConf2-devel freetype-devel
* Build the Bacula RPM:
% rpmbuild --rebuild --define "build_centos4 1" --define "build_mysql 1" --define "build_mysql4 1" bacula-1.36.2-4.src.rpm
* Copy in my old config files and start it up!


I am now getting an error from one of the client systems I'm trying to back up. All other systems still work okay, except this one. Can anyone help me figure this one out?

Here's what the errors say:
15-Apr 09:27 backupserver-dir: Intranet_Server.2005-04-15_09.15.22 Fatal error: Network error with FD during Backup: ERR=Connection reset by peer
15-Apr 09:27 backupserver-dir: Intranet_Server.2005-04-15_09.15.22 Fatal error: No Job status returned from FD.
15-Apr 09:27 backupserver-dir: Intranet_Server.2005-04-15_09.15.22 Error: Bacula 1.36.2 (28Feb05):


My backup server is on a private NAT IP. Most clients systems are also on private IPs. Two of these systems are on public IPs. I can back up one of those systems with no problem, but the other one gives me the errors.

The port forwarding was already set up in our router, and I know that works since I can back up one of the two public IP systems with no problem. The firewall was already correctly set on the server that is failing, and even after I disabled it things still didn't work.

I checked to make sure name resolution was working okay for this host. I upgraded Bacula on the client, in case that mattered. (I believe it had 1.36, and I now have 1.36.2, but I doubt that matters, right?)

I have searched for this error through the mail archives, and I don't find much. I've tried looking for debugging and troubleshooting info in the manual, and I haven't found much there either.

Would starting the director with the -d99 debug switch help me here? What am I missing? How can I fix this?

Thanks for any help you can offer!!

Relevant portions of /etc/bacula/bacula-dir.conf:
------------------------------------------------
Job {
  Name = "Intranet Server"
  Type = Backup
  Client = intranet-fd
  FileSet = "Unix Full Set"
  Schedule = "WeeklyCycle"
  Storage = DLT8000-ext
  Messages = Standard
  Pool = Default
  Write Bootstrap = "/var/bacula/intranet.bsr"
}

# Intranet Client (File Services) to backup
Client {
  Name = intranet-fd
  Address = intranet.microlnk.com
  FDPort = 9102
  Catalog = MyCatalog
  Password = "********************************************"
  File Retention = 1 week
  Job Retention = 1 week
  AutoPrune = yes                     # Prune expired Jobs/Files
}

--
Jason Byrns
Production Manager
System Administrator
http://www.MicroLnk.com/
402-328-8600 ext. 653


------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to