>We are looking at a trival method of dividing up the amanda >disks - group 1) local to server, group 2) remote clients.
That will work very easily. No special (source code) work required. >Since one amanda will never actually touch the ethernet interface >is there another method or work-around we should know about ? Nope. Amanda does not do anything special for the "local" client. It still connects to inetd, etc. So you have to set up the server just like any other client (in addition to the server setup). Most OS's detect connections to the local host and shortstop the traffic to the loopback interface for you. >I've never had to compile with alternate ports before, assuming >its ./configure --with-port= or some equiv, if there a howto >on exactly what switches and other considerations ? You won't need alternate ports. You can do what you need to do with two Amanda configurations on the server. One has a disklist, etc, that refer to just the server. The other has all the other clients. Since the configurations are in separate directories, there won't be any crosstalk. >How do I choose ports without risking collision with anything else ? As above, you don't need to because you can just use two configurations. But for anyone else reading this that *does* want to use alternate ports, I just picked related numbers and had my local network guru register them. That's no guarantee some annoying program won't grab one of them at just the wrong time, but there's no guarantee that won't happen with the normal Amanda ports (or any other port, for that matter). Here are my amanda /etc/services entries: amanda 10080/tcp # CC - Amanda backup system amanda-alt1 11080/tcp # CC - Amanda backup system amanda-alt2 12080/tcp # CC - Amanda backup system amanda 10080/udp # CC - Amanda backup system amanda-alt1 11080/udp # CC - Amanda backup system amanda-alt2 12080/udp # CC - Amanda backup system Also, the "alternate port" patch I was talking about allows you to pick the port in the amanda.conf file -- no rebuild is needed (except once to apply the patch). > Brian John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
