Your presumption was absolutely right choogendyk.

I changed the ownership of the file back to amanda:disk on my client alpha and it started working fine.

I am not sure how to find this out however I checked the same by using service xinetd status and it said xinetd is running......

Final result:

-bash-3.2$ /usr/sbin/amcheck intra
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps/amanda: 58927428 KB disk space available, using 58745788 KB
WARNING: skipping tape test because amdump or amflush seem to be running
WARNING: if they are not, you must run amcleanup
Server check took 0.007 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.143 seconds, 0 problems found.

Now I am wondering where my backup is stored and how I can view that on my backup(gamma) server.

I did this again referring to http://www.howtoforge.com/centralize...anda-on-centos on a different machine.

Sorry I was out for a while. You seem to have it working. You do need to look at your backups and test that you know how to get them back.

According to your amanda.conf posted on 4/27, your backup location is defined by:

tapedev "file:/backup/intra/slots"

Look there to see what they look like. However, what you see there has to be extracted. The label gives instructions for extraction using native linux commands, or you can use amrecover or amrestore. See the man pages for those, or follow http://wiki.zmanda.com/index.php/Qui...sting_recovery.