Zmanda Client For Mac
You may want to look at which condenses documentation on Amanda for Mac OS X from a few sources, including locnar's. I have a few questions/suggestions. Are you running Mac OS X Panther (10.3) or Tiger (10.4)? If Tiger, you'll need to add your service to launchd instead of xinetd (see the wiki page).
Once that's resolved, try running netstat -ap grep 10080 on the mac to see if it's listening on that port. You should see something like udp4 0 0.10080.
By default, the Mac firewall does not block any UDP packets, but this may be different in your configuration. Check the firewall settings (under 'Sharing' in System Settings). EDITED TO ADD: Note that the above netstat output will appear even if the firewall is blocking that port.
Unfortunately, with UDP, it's difficult to distinguish a failure to receive a packet from a successful receipt with a failure to reply. There are several reasons such a failure may occur. Check /tmp/amanda/amandad on the mac to see if amandad is creating any interesting logfiles. Please post the results of the above, and we'll see where they point us. Thanks for your replies guys - excellent information! I'm out of the office over the weekend so can't check server-client connectivity but have made changes to the OSX client.
Zmanda Recovery Manager for MySQL Download - Zmanda Recovery Manager (ZRM) for MySQL is a robust backup and recovery solution. I am tyring to use amanda backup on mac os 10.6. Amanda server is on linux box. I could able to install client on mac os 10. But when I check.
Basically, I've left my OSX amanda client users as 'amandabackup' but made sure this user has group 'wheel' access and appropriate permissions as per the wiki instructions. I then recompiled and installed from source using the basic configuration flags in the wiki instructions. I edited the Username and ProgramArgument strings in the plist file to 'amandabackup' and '/usr/local/libexec/amandad' and copied as per instructions. Launchtl gave the following message after running: 'nothing found to load' netstat -na grep 10080 provided this output: udp4 0 0.10080. So, no udp6 entry.
Is all this looking good to go so far or is something missing? BTW, I installed the client overtop of the old instal without deleting any part of the old iinstall (if this might make a difference). Thanks again, for your help, Matt. OK back at work and unfortunately no luck. I built the OSX client from source as per Wiki with configure directives:./configure -with-user=amandabackup -with-group=wheel Then restarted the machine. Found no.debug file in /tmp/amanda so ran: sudo launchctl load /Library/LaunchDaemons/org.amanda.amandad.plist Reponse: 'Nothing found to run'.
Still no.debug file in /tmp/amanda. Also no output from 'netstat -na grep 10080'.
Ran service xinetd restart then netstat command again and got: udp4 0 0.10080. I guess this is picking up the original xinetd configuration I used before trying the OSX wiki notes used xinetd. So, ran make uninstall and am deleting the 'amandabackup' user on the client. Will try a clean reinstall on the OSX client as per the Wiki notes.
Couple of questions: Does it matter that the amanda user on the client and server have different usernames(s:amandabackup, c:amanda)? Does it matter that the amanda user on the client and server belong to different groups(s:disk, c:wheel)? If I follow the RedHat QuickStart configuration here (and the Wiki OSX client configuration for Tiger, shouldthese configurations play together nicely? OK, the clean install went well. I had to use a '-w' switch with launchctl load to get the amanda client to load successfully. Now the netstat grep shows correct results: udp4 0 0.10080. udp6 0 0.10080.
I'm still getting the same results when I run amcheck on the server though ('Connection refused'). No amandad.debug files are being generated on the client.
Installed a port scanner on the server machine and tried scanning a few ports to check status.:80 and others are working ok but with:10080 I get: 10080/tcp closed unknown The client machine firewall is definately disabled and I'm definately hitting the IP address of the client. As the server is running SELinux I also used 'setenforce 0' to switch it into permissive mode just in case but made no difference. Also tried substituting IP addresses in the client and server.amandahosts files (my LAN dns creates domains of the form hostname.domain - are these considered fully qualified/should they work with Amanda?). Re: launchctl load -w - this basically edits the.plist file in place to remove 'disabled'. It's a strange feature on Apple's part, but we might as well play along. I just edited the wiki to add it.
Re: mismatched usernames/groups: that should be fine, although it takes some thinking about which username should appear where. The.amandahosts should have the username from the.server.
in it. Re: compatibility of Linux and Mac OS X configurations - that shouldn't cause any trouble at all. Finally, it looks like you're using BSDTCP authentication, but the launchd script sets up for UDP/BSDUDP communication (specifically, it listens on UDP port 10080, not TCP port 10080). I suspect that just changing the dumptype to specify 'auth bsd' will get things working for you. I haven't gotten BSDTCP working with my mac just yet, but I haven't tried too hard, either.
Zmanda Client For Mac Free
Well my client.amandahosts file reads: 192.168.2.5 amandabackup amdump And the disklist entry for the client reads: 192.168.2.11 /testamanda/anotherdir comp-user-tar No auth scheme was defined for this dumptype but the config notes suggest auth bsd is the default. After explicitly entering auth 'bsd' for comp-user-tar I now get this when running amcheck: ERROR: NAK 192.168.2.11: user amandabackup from morpheus is not allowed to execute the service noop: /Users/amanda/.amandahosts: incorrect permissions; file must be accessible only by its owner.
So chmod'ed.amandahosts to 600 - check completes successfully! Many thanks to all of the above for their assistance.