Building Amanda on CentOS or Redhat.

This is a modern interpretation of some work I did some time ago with version 2.6.1.  I’m just now working with 3.3.1 and documenting as I work so you may find that it’s not complete today if I get interrupted.

Jay – 27 July 2011.

IN A NUTSHELL

  1. Install the OS
  2. Patch the OS
  3. Load AMANDA Server Software
  4. Configure AMANDA
  5. Verify the Install

PREREQUISITES
We will need a system with gigabit interfaces, a large (1TB) drive space to act as virtual tapes, USB 2.0 capable ports and at least 2GB of RAM.  While the backup server does not strictly need to be a high powered server it doesn’t hurt to give it some guts as the remote servers are often not powerful enough to do the compression/encryption of the data before transmission.  A powerful backup server can easily handle task of building tar.gz files.

STEP-BY-STEP
These are the steps mentioned above and while you may want to vary from them I would not recommend skipping steps like “Patch the OS” as this is the sort of thing that can come back and bit you. Patching can take some time, but don’t skip this step. For the most part patching is an unattended step so you can do other things.

### Install the OS ###
I would recommend using a CentOS install for this as there are RPMs available which will facilitate later steps. When building try to keep the install minimal You don’t need that much to make AMANDA work, however, you should setup a few things:

  • Operate on the CLI (init 3) rather then with a GUI.  Just change the /etc/inittab so that the first uncommented line is id:3:initdefault: instead of id:5:initdefault:
  • Firewall with 10080-10083 tcp/udp open. – Let me know if you need firewall settings.
  • NO SELINUX – Unless you want to help me define these?

### Patch the OS ###
Do not skip this step. Even though it may take an hour to load the updates it it well worth the time. Running on unpatched code is just begging for a weird, time consuming problem later in this process. While this is happening you can work on the path statement below and also cleaning up the start up files.

# Load Updates
 yum -y upgrade
 reboot
 

While you are waiting for yum to finish you can work on a few other things as well.

# Path Changes
for d in /usr/local/bin /usr/local/sbin
do
 case :$PATH: in
 *:$d:*) : ;;
 *) PATH=$d:$PATH ;;
 esac
done
# Turn off extraneous processes (NB: there are plenty of new processes in RHEL6)
chkconfig autofs off
chkconfig cups off
chkconfig ip6tables off
chkconfig bluetooth off

### Load AMANDA Server Software ###
Grab the latest Amanda software from the RPM repository here and install it. Don’t be too worried about the fact that the version don’t match. Assuming the config file doesn’t change the location of the binaries… which we double-check later… there should not be a problem. Your only issue is you may be missing a feature that makes your AMANDA experience “better”:

http://www.zmanda.com/download-amanda.php

Something like this:

mkdir -pv ~/addon_software; cd ~/addon_software
wget http://www.zmanda.com/downloads/community/Amanda/3.3.0/Redhat_Enterprise_4.0/amanda-backup_server-3.3.0-1.rhel4.x86_64.rpm
wget http://www.zmanda.com/downloads/community/Amanda/3.3.0/Redhat_Enterprise_5.0/amanda-backup_client-3.3.0-1.rhel5.x86_64.rpm
wget http://www.zmanda.com/downloads/community/Amanda/3.3.0/Redhat_Enterprise_4.0/amanda-backup_client-3.3.0-1.rhel4.i386.rpm
 yum localinstall --nogpgcheck amanda-backup_server*.rpm

 # Check for errors
 cat /var/log/amanda/install.err
# Set the amandabackup user password and unlock the account
 passwd amandabackup
 passwd -u amandabackup

# You may also want to get ntpd setup and running - not discussed here
# but having accurate time will most certainly help things along.

—–

### Amanda Admin Information
Because any newer version of the Amanda Server RPM could make changes to the usernames, groups and default directories you may want to check these with the amadmin command. This command will display what your current installation has set for users, groups, and directories. If there is a difference when you recover the amanda configuration files from the backups you will need to make the appropriate changes. I have included the expected responses in the comment lines:

# Amanda User - amandabackup
 /usr/sbin/amadmin xx version | grep CLIENT_LOGIN
# Amanda Configuration Directory - /etc/amanda
 /usr/sbin/amadmin xx version | grep CONFIG_DIR
# Amanda Debug Log Dir - /tmp/amanda
 /usr/sbin/amadmin xx version | grep AMANDA_DBGDIR
# Amanda Executables - /var/lib/amanda
 /usr/sbin/amadmin xx version | grep libexecdir
# Amanda GNUTAR Lists - /var/lib/amanda/gnutar-lists
 /usr/sbin/amadmin xx version | grep listed_incr_dir

# Create the Holding Disk
You may want place your holding disk on a high-speed drive that is separated from the OS drive. This will speed things up a bit.

# Setup a Holding Disk.  Why? Well if you have tapes that are slower
 # than your hard drive a holding disk will grab the data faster. Also,
 # holdingdisks will continue to grab incremental backups if you fail to
 # change the tapes.  Kind of a cool thing that.
 #
 # For this specific install I have a HUGE 12TB array that I can use.
 # Gadzooks!  I called it /storage 
mkdir -pv /storage/holdingdisk
 mkdir -pv /storage/vtape
 chown -R amandabackup:disk /storage/holdingdisk /storage/vtape
# Setup the amanda permissions in the "secret file"
 # it's really not a secret, but lots of people forget this step.  If
 # you add in all the servers and give them permissions to interact with
 # amanda 
vi /var/lib/amanda/.amandahosts
 
servername.domain.com    root amandabackup amandad amindexd amidxtaped
servername.domain.com    amandad amidxtaped
# This gives two different sets of permission.  One for the root user
 # and the other for the amanda daemon.
# Setup the /etc/amanda/amanda-client.conf with a valid tape device
 # in my case tapedev         "file:/storage/vtape"   # your tape device

# Build your tapes
Note that your backups will appear in one or more of the slots which represent both the full and the incremental backups located inside /storage/vtape. You’ll want to create all the tapes.  I believe there is a nice clean way to create these labels. but you can also us this lovely DO LOOP:

cd /storage/vtape
for ((i=1; $i<=15; i++)); do mkdir slot$i; done
for ((i=1; $i<=15; i++)); do /usr/sbin/amlabel daily daily-$i slot $i; done

I had some difficulty here where even though I labeled my tapes I was getting messages about ‘unlabeled volume’ on all my tapes.  So I ended up setting the permissions so that amandabackup:disk owned the vtapes/slots and then ran things as amandabackup  Suddenly the results of my “amtape daily show” where no longer “unlabeled volume” but label daily-nn.

# Reset the tapes
amtape daily reset

#### Configuration #####
Skipped for now, please contact me and i’ll share my config and any of the intricacies that I have found over the years.

Setup Crontab

# Amanda check and dump
0 16 * * 1-7 /usr/sbin/amcheck -m daily
05 21 * * 1-7 /usr/sbin/amdump daily
0 8 * * * find /etc/amanda/daily/log.20* -type f -mtime +25 -exec rm {} \;

.
#### Test Amanda #####
Login as amandabackup and run amcheck daily.  This will generate some errors with specific messages about changes you need to make to the .amandahost files of your clients.

### Other Tips ####

yum localinstall –nogpgcheck pigz-2.1.6-1.el5.rf.x86_64.rpm

amservice engineer.serverdomain.com bsdtcp noop < /dev/null

 

m

Measuring Drive Speed in Linux

Benchmarking drive speed is made a lot easier in Linux by the presence of a tool, hdparm.  On IDE style drives and ATA running with the arbitrator they produce pretty good results:

#hdparm -t /partition/totest

Some Original Results prior to messing with the strip sizes:

PowerEdge 2950 -> 20 to 90 mb/sec
PowerEdge 6800 -> 25 to 30 mb/sec

hdparm _only_ works when the Integrated Drive Electronics (IDE) are talking directly to the system over the AT Attachment (ATA) arbitrator.  So see if you are running the libata module by using the lsmod command. If you see it is running… but remember it could be running for one set of diskc and not another.

YOUR BEST BET: Use “modinfo -p” on the vendor’s SCSI driver to see what options are supported at load time.

Other note to measure Random access times… use seeker.c and compile it. it will run a series of random seeks and report the times.  After some rebuilds I have done some benchmarking along with some changes to increase RAID5 stripe sizes in the PE2950 systems:

# New Results After Increasing the Strip Size
Backup Server PowerEdge 2950 – 319.06 MB/sec
PowerEdge 6800 - 92.16 MB/sec

This is by no means a comprehensive discussion of benchmarking, but it’s a good way to start the conversation and it only takes a few moments

About Jay Farschman - Jay currently works as a Senior Systems Administrator for an asset management company in Colorado where he works with companies that produce hardware, telecommunications software and financial services.  Jay previously owned a consulting company and provided training and consulting services for three Fortune 500 companies and numerous small businesses where he leveraged Linux to provided exceptional value.

Swapping Tapes in Amanda

I just read a forum post over at the Zmanda forums where a fellow wanted to know if he should park the heads before unmounting.  The answer was that typing “man amanda-changer” will tell you everything you need to know.  Well, I wrote a tape changer script a long time ago for those days when we need to change the tapes, but I’m not around.

My tapes run on a 7-day cycle and I use the linked script. There is a lot of confusion about tape rotation with Amanda.  For that reason I recommend that the truly hopeless n00b purchase Zmanda or get some help from an experienced Amanda user admin.

About Jay Farschman - Jay currently works as a Senior Systems Administrator for an asset management company in Colorado where he works with companies that produce hardware, telecommunications software and financial services.  Jay previously owned a consulting company and provided training and consulting services for three Fortune 500 companies and numerous small businesses where he leveraged Linux to provided exceptional value.

Amanda – Restoring a Disklist Entry Manually

Quickly, how do you manually extract all of the data from a disklist entry (DLE)?  Use a script.  In my example I’m going to restore a copy of the /etc/amanda directory.  This could very well be part of the restore for a barebones restore.

So, change the first line so that it identifies where all the tapes are.  Mine are in /vtape.  You will not that it’s going to look in all the slots for the data and run through the DO LOOP for each slot that it finds.  Name the disklist entry (DLE) also in the first line.  Then navigate to the directory where you want to expand everything and run it.

for tape in `ls /vtape/slot*/*.backup.domain.com._etc_amanda.*`
do
    dd if=$tape bs=32k skip=1 | tar zxvf - 
    echo $tape
done

That’s it.  There is also an amrestore command that gives you the ability to selectively restore things.  It’s a nice feature allowing you to navigate in a FTP-style CLI interface and select items or directories or even the entire system.  This isn’t going to do you any good though with a barebones restore.

NOTE BENE: I posted the above information on the zmanda forums and swrowland pointed out that I’m not restoring things on chronological order.  That’s been fine for my previous testing which was all about restoring the /etc/amanda directory as a part of a barebones recovery, but it’s rather lacking if you unpack things in the wrong order.  He proposed the following:

for tape in $(ls -rt $BACKUP/slot*/*.linux.*)
do
  echo tape = $tape
  dir=${tape#*_}
  dir=${dir#_}
  dir=${dir%.?}
  dir=${dir/_/\/}
  echo dir = $dir
  mkdir -p $dir
  cd $dir
  dd if=$tape bs=32k skip=1 | tar xzvf -
  cd -
done

So, $BACKUP is the location of the backups and *.linux.* is the string used to find the exact set(s) of backup.  Much better.  Thanks.

About Jay Farschman - Jay currently works as a Senior Systems Administrator for an asset management company in Colorado where he works with companies that produce hardware, telecommunications software and financial services.  Jay previously owned a consulting company and provided training and consulting services for three Fortune 500 companies and numerous small businesses where he leveraged Linux to provided exceptional value.

 

 

Backup Server – Amanda – Concepts

This article is simply a collection of key concepts that you need to know before yo begin working on AMANDA which is a network-based backup utility that with the capability of load-balancing backups based on available space, bandwidth. Additionally, AMANDA is pretty forgiving for lazy administrators who forget to swap tapes.

Continue reading

Backup Server – Amanda – Barebones Recovery

Barebones recovery means starting fresh on a different system with different hardware and perhaps with different versions of the OS and, yes even the AMANDA client and server software. I had an opportunity to test this recently, and these notes are the result. They should take you through the process in a reliable fashion from start to finish. The actual time is largely dependent on your OS installation time.

IN A NUTSHELL

  1. Install the OS
  2. Patch the OS
  3. Load AMANDA Server Software
  4. Recover Your Configuration
  5. Verify the Install

PREREQUISITES
We will need a system with two interfaces, preferably gigabit interfaces, a large (1T drive space, USB 2.0 capable ports and 2GB of RAM.

STEP-BY-STEP

These are the steps mentioned above and while you may want to vary from them I would not recommend skipping steps like “Patch the OS” as this is the sort of thing that can come back and bit you. Patching can take some time, but don’t skip this step. For the most part patching is an unattended step so you can do other things.

### Install the OS ###
I would recommend using a CentOS install for this as there are RPMs available which will facilitate later steps. When building try to keep the install minimal You don’t need that much to make AMANDA work, however, you should setup a few things:

Second Interface – 111.111.111.14/28 with no gateway
Firewall with 10080-10083 tcp/udp open.
NO SELINUX – Optional
### Patch the OS ###
Do not skip this step. Even though it may take an hour to load the updates it it well worth the time. Running on unpatched code is just begging for a weird, time consuming problem later in this process. While this is happening you can work on the path statement below and also cleaning up the start up files.

# Build the encryption public/private key for root
ssh-keygen -trsa
cd .ssh
scp root@cacti.nettraffic.net:/root/files/Primary/html/authorized_keys .

# Load Updates
yum -y upgrade
yum -y install vim-enhanced
reboot

While you are waiting for yum to finish you can work on a few other things as well.

# Path Changes
for d in /usr/local/bin /usr/local/sbin
do
case :$PATH: in
*:$d:*) : ;;
*) PATH=$d:$PATH ;;
esac
done

# Turn off extraneous processes
chkconfig autofs off
chkconfig cups off
chkconfig ip6tables off
chkconfig bluetooth off

### Load AMANDA Server Software ###
Grab the latest Amanda software from the RPM repository here and install it. Don’t be too worried about the fact that the version don’t match. Assuming the config file doesn’t change the location of the binaries… which we double-check later… there should not be a problem. Your only issue is you may be missing a feature that makes your AMANDA experience “better”:

http://www.zmanda.com/download-amanda.php

Something like this:

cd ~
wget http://www.zmanda.com/downloads/community/Amanda/2.6.1p1/Redhat_Enterprise_5.0/amanda-backup_server-2.6.1p1-1.rhel5.i386.rpm
rpm -ihv amanda-backup_server*.rpm

# Check for errors
cat /var/log/amanda/install.err

# Set the amandabackup user password and unlock the account
passwd amandabackup
passwd -u amandabackup

# Update the locate command the the time
ntpdate ntp.pool.org
updatedb &

—–

### Amanda Admin Information
Because any newer version of the Amanda Server RPM could make changes to the usernames, groups and default directories you may want to check these with the amadmin command. This command will display what your current installation has set for users, groups, and directories. If there is a difference when you recover the amanda configuration files from the backups you will need to make the appropriate changes. I have included the expected responses in the comment lines:

# Amanda User – amandabackup
/usr/sbin/amadmin xx version | grep CLIENT_LOGIN

# Amanda Configuration Directory – /etc/amanda
/usr/sbin/amadmin xx version | grep CONFIG_DIR

# Amanda Debug Log Dir – /tmp/amanda
/usr/sbin/amadmin xx version | grep AMANDA_DBGDIR

# Amanda Executables – /var/lib/amanda
/usr/sbin/amadmin xx version | grep libexecdir

# Amanda GNUTAR Lists – /var/lib/amanda/gnutar-lists
/usr/sbin/amadmin xx version | grep listed_incr_dir

# Create the Holding Disk
You may want place your holding disk on a high-speed drive that is separated from the OS drive. This will speed things up a bit.

mkdir -p /holdingdisk
chown -R amandabackup:disk /holdingdisk

### Recover Your Configuration ###
Now lets recover some data from the USB drive (tape). This process is fairly straight forward and begins with figuring out what the USB device is called by the system. If you waited to plug the USB drive until after the last reboot it will be easier. Simply use the command dmesg | grep sd and look for the last entries. you should see something like this

dmesg | grep sd
…..
sdb: Spinning up disk….ready
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
….

That tells me we are working with a 1TB drive called sdb and our data will be on sdb1. Let’s mount it

mkdir vtape
mount /dev/sdb1 /vtape

Create a /etc/fstab entry so this mount continues to work after a reboot.

Note that your backups will appear in one or more of the slots which represent both the full and the incremental backups located inside vtape1. You’ll need to grab all of them to be sure you have all the data. They will look like this 00002.backup.server.com._etc_amanda.0 with the label etc_amanda in the name. The DO LOOP below will automatically expand the appropriate backup tape into your /etc/amanda directory and remember, since we have placed other critical files there we will be able to pull these into position now as well.

cd /etc/amanda
for tape in `ls /vtape1/tape/slot*/*.backup.server.com._etc_amanda.*`
do
dd if=$tape bs=32k skip=1 | tar zxvf -
echo $tape
done

# Replace all the hand configured files
These are the files that were not properly handled by the RPM install. We diligently keep them in the amandarecovery directory, but information on setting these files up is pretty much boiler plate and available on the amanda wiki site.

cd /etc/amanda/amandarecovery/
cp services /etc/
cp resolv.conf /etc/
cp /etc/hosts /etc/
cp zz-ps1.sh /etc/profile.d/
cp iptables /etc/sysconfig/
cp authorized_keys /root/.ssh/

########### crontab —- insert crontab info here.

### Verify Your Installation ###
Almost all useful commands need to be run as the amandabackup user so for this portion of the installation you need to su and become that user. Root is just going to issue errors.

su – amandabackup
amcleanup daily    # cleanup before your first run.
amcheck daily

If you can run an amcheck daily and thing come out without errors then you’ve accomplished something. Otherwise, work the error messages one at a time with a search engine.

Backup Server – Using Amanda

AMANDA works predictably, checking every afternoon at 4 PM to see that is has proper tapes loaded and then beginning backups in the evening. Amanda is forgiving if you forget to make the weekly tape swap continuing to do incremental backups for an additional 7 days. Unfortunately, AMANDA does not have a GUI, but that should not slow you down. There are just a handful of commands and set of simple concepts that you need to manage things

OVERVIEW
Amanda reads from a disklist that has single line entries describing which system to back, and what methods to use. The disk list is invoked by cron which calls the main configuration file amanda.conf. Amanda.conf contains most, if not all of the configuration so this is where you would describe how large the tapes are what the rotation rules are etc…. So, nearly everything is controlled by the crontab, the disklist and the amanda.conf file. For more details on concepts and vocabulary see the TERMS and CONCEPTS DOCUMENT.

Backup Operators need to swap out the hard drive (virtual tape) every week taking one drive offsite for disaster recovery.

Continue reading

Backup Server – Amanda – Selective File Restore

Restoring is accomplished with the amrecover command. You may choose to expand the files on the Amanda Server’s holding disk…. it’s big enough, or perhaps you’d rather run amrecover command directly from the Amanda client system. This is not the proper procedure for recovery of an entire system. amrecover digs in to the tarballs and pulls out files selectively. If you need the full restore then use amrestore which is faster because it allows the system to bypass the step of finding all of the files in the tarball before expanding them… amrestore assumes they are all there.

OTHER ARTICLES IN THIS SERIES
These are links to all the core Amanda articles:

  • CONCEPTS AND VOCABULARY
  • HOWTO – Backup Files with Amanda
  • HOWTO – Recover Some files with Amanda
  • HOWTO – Barebones Recover the Amanda Backup Server
  • HOWTO – Restore Entire Systems With Amanda

EXTRACTION
amrecover -C daily -s backup.servername.com
listhost – lists the hosts in the daily backup config
sethost servername – sets the host to servername.
listdisk – list the disks we backup on servername
setdisk /restore_directory – sets the directory to /restore_directory on servername.
setdate —10 [optional] – Let’s pull our backup from the 10th of this month.
ls / cd / pwd / help – Navigate around.
add restore_directory/ – Add the entire path or a single file. Do this repeatedly.
clear or delete restore_directory/ – Clear the entire extraction list or just delete a single path or item.
extract – extracts the files. Be patient. This may require referencing multiple backup and pulling date from very large files.
exit – exit out of amrestore.
Once you get to the extract exercise a little patience and just go away for a time. Gzip is gong to dominate the CPU and disk reads for a time, but you’ll also see tar, amandad, amrecover and amidxtaped running. A system load of two or three is typical. It looks like the more files, even if they are tiny, the higher the load. Larger files seems to extract much faster.

MOVE THESE FILES TO THE DESTINATION
I’ve always said that rsync is powerful, but the problem is people has difficulty using is. We use it here because if the transfer of files is interrupted you can start it again and it will pick up where it left off. Also.. if does some nice work statusing you while the files move.

OPTS=”-v -u -a –rsh=ssh –stats”
USER=root
DEST=monroe
DESTDIR=/root/vgupta
RESTOREDIR=vgupta/
rsync $OPTS $RESTOREDIR $USER@$DEST:$DESTDIR

Take a note of the backslashes in the DIR variables… Destination is NOT terminated with a / while RESTOREDIR IS terminated with a /.

Expect around 20Mbytes/sec on these transfers.

HOWTO – Restore Entire Systems With Amanda

Okay first the bad news…. because of the way the amanda client currently work, recovering a single file is only possible by bringing back the entire DLE. So you expand the whole thing just for a single file  With that said…. ti’s not that difficult

WINDOWS RESTORE/RECOVERY

# Pull MyServer’s Dumps from the tape
cd /holdingdisk/
amfetchdump daily myserver.domain.com D:/mydestination_drive

Now copy these to the windows system and use pkzip or winzip to restore them.

Backup Server – Loading Amanda Client on Mac leopard

Amanda runs as a daemon on the Mac so that it’s available, but not using much in the way of resources while it’s waiting for the server to request the next backup. I had a nice opportunity to learn about how Leopard handles these daemons and that is detailed below…. but first a few notes about Amanda on Macs.

Compile it – Ouch… we have to compile it to make it run. There is not simple installer.
Native Tools – Backups are accomplished using native tool. Meaning, the compression, and transport/copy tools on OS X are going to be used. This is important because Non-native applications have a devil of a time preserving the extended ACLs.
Version Specific Notes – Leopard is pretty good, but Tiger and Panther are reported to have defective TAR applications that do not preserve ACLs properly. There is a nice application called ‘backup bouncer’ written by a grad student to force Apple to fix these bugs…. and the result is clean functionality in Leopard.
INSTALLING THE CLIENT – PREREQUISITES
Before installing you are going to need to download and install xcode from Apple’s web site. This includes a compiler that you really need. When done installing xcode install the glib2 package with this command:

sudo port install glib2

You will either have to reboot after the xcode install or re-source your path. Rebooting is easier to describe

INSTALLING THE CLIENT – DO IT!!!
First create the amandabackup user and group and set the password.

Code:

sudo dscl localhost -create /Local/Default/Users/amandabackup
sudo dscl localhost -create /Local/Default/Users/amandabackup RecordName amandabackup
sudo dscl localhost -create /Local/Default/Users/amandabackup UserShell /bin/bash
sudo dscl localhost -create /Local/Default/Users/amandabackup RealName “Backup User”
sudo dscl localhost -create /Local/Default/Users/amandabackup UniqueID 5000
sudo dscl localhost -create /Local/Default/Users/amandabackup PrimaryGroupID 0
sudo dscl localhost -append /Local/Default/Groups/admin GroupMembership amandabackup
sudo dscl localhost -create /Local/Default/Users/amandabackup NFSHomeDirectory /Users/amandabackup
sudo ditto -rsrcFork ‘/System/Library/User Template/English.lproj/’ /Users/amandabackup
sudo sh -c “echo ‘amandabackup_server.example.com amandabackup’ > /Users/amandabackup/.amandahosts”
sudo chown -R amandabackup:wheel /Users/amandabackup
sudo passwd amandabackup
Download the source code and expand it with the tar -zxvf amanda.tar.gz command. Then in the directory run the following:

# Configure it with bsdtcp transport
sudo ./configure –with-user=amandabackup \
–with-group=admin –with-bsdtcp-security \
–without-server

# Make it and install it
sudo make
sudo make install

It’s now installed, but the daemon is not running yet. You need to add a plist to the LaunchDaemon. That Plist entry below should be placed in the file /Library/LaunchDaemons/org.amanda.amandad.bsdtcp.plist

Code:

Label
org.amanda.amandad.bsdtcp
UserName
amandabackup
GroupName
wheel
InitGroups

ProgramArguments

/usr/local/libexec/amanda/amandad
-auth=bsdtcp
amdump
amindexd
amidxtaped

Sockets

ipv4

SockFamily
IPv4
SockServiceName
amanda
SockType
stream

ipv6

SockFamily
IPv6
SockServiceName
amanda
SockType
stream

inetdCompatibility

Wait

Good… every time you reboot the daemon will launch and be ready. But just now it’s still not running. Let’s launch it:

sudo launchctl load -w /Library/LaunchDaemons/org.amanda.amandad.bsdtcp.plist

CHECK OUR WORK
You know it’s running with netstat shows 10080 listening.

$ netstat -na | grep 10080
tcp6 0 0 *.10080 *.* LISTEN
tcp4 0 0 *.10080 *.* LISTEN

The real test is to work from the server and noop your Mac.

amservice mac.domainname.com bsdtcp noop