Hi, Under amanda 3.1.0beta1 with a server multihomed to two networks, when disklist only contains entries for clients multihomed to networks 1 and 2 - all backups succeed. When disklist contains any entries connected to only network 2 - all backups fail. The amanda disklist and amanda-client.conf are configured to only use dns/ip addresses from network 2.
errors that I've found include: driver: FATAL schedule line 7: syntax error (bad dump date) line number does not seem relevant amdump.9:driver: schedule line 13: syntax error (bad nsize) Running amcleanup does not help. Hosts on both networks are configured almost identically (cloned VM's with minor changes). The firewall will allow hosts on network 1 to connect to network 2, but not vice versa. I do not see any unusual log entries for denied traffic in the firewall. Amanda was deployed using a combination of my own shell script + the public rpms for beta1. All log entries show connections only to/from network 2 and I have turned off ssh authentication and am using bsdtcp. Stumped. We deployed network 2 to be a layer 2 private vlan that only the amanda server would be promiscuous on. Clients can not send/receive traffic from other clients - they can only initiate or reply to traffic from/to the amanda server. I would think this would be a configuration that a lot of enterprises are experimenting with now that vmware and most switch hardware vendors implement private vlans reliably. All hosts and clients are RHEL5.4 or 5.5 running on x86_64.. Let me know if there is some bug entry I should submit... Regards, M. Marlowe -- Matthew Marlowe - http://www.deploylinux.net/ CEO @ DeployLinux Consulting, Inc [email protected], 858-400-7430 http://www.twitter.com/deploylinux
