Backup client (old)

Simple Backup Client configuration

• When using BSD-style security (enabled by default), set up your ~dumpuser/.amandahosts (or ~dumpuser/.rhosts and/or /etc/hosts.equiv, if you have configured --without-amandahosts) so that the dumpuser is allowed in from the server host. Only canonical host names will be accepted in .amandahosts, and usernames must be present in every line, because this is safer.
• Set up your raw disk devices so that the dumpuser can read them, and /etc/dumpdates so that the dumpuser can write to it. Normally this is done by making the disk devices readable by (and dumpdates read/writable by) group `operator', and putting the dumpuser into that group.
• Put the AMANDA service into your /etc/services file. Add entry like:

/etc/services

amanda		10080/udp
amandaidx	10082/tcp
amidxtape	10083/tcp

You may choose a different port number if you like, but it must match that in the services file on the tape server host too.

If you are running NIS (aka YP), you have to enter the AMANDA service into your NIS services database. Consult your NIS documentation for details.

You may use the `patch-system' script, from client-src, in order to modify this file. Run it with a `-h' argument for usage.

• Follow one of the following steps to set up the AMANDA client service:
  • If your AMANDA client uses inetd, put the AMANDA client service into inetd's config file. This file is usually found in /etc/inetd.conf, but on older systems it is /etc/servers. The format is different on different OSes, so you must consult the inetd man page for your site. Here is an example from our site, again from SunOS 4.x:

/etc/inetd.conf

amanda dgram udp wait USER AMANDAD_PATH amandad

You may use the `patch-system' script, from client-src, in order to modify this file. Run it with a `-h' argument for usage.

• If your AMANDA client uses xinetd, you have to add the following file to your xinetd-configuration (usually /etc/xinetd.d) and edit it to reflect your settings and paths:

/etc/xinetd.d/amanda

service amanda
{
     socket_type		= dgram
     protocol		        = udp
     wait			= yes
     user			= $USER
     group			= $GROUP
     groups 			= yes
     server			= $AMANDAD_PATH/amandad 
}

• If your AMANDA client uses Dan Bernstein's daemontools (http://cr.yp.to/daemontools.html) instead of (x)inetd, you have to create the amanda service by hand. You will need also an UDP super-server (netcat in this example).
  • Create service directory:

mkdir -p /etc/amanda/supervise/amanda

• • Create service startup file and make it executable:

/etc/amanda/supervise/amanda/run

#!/bin/sh
exec /usr/local/bin/setuidgid amanda \
 /usr/bin/netcat -l -u -p 10080 -q 0 \
 -e /usr/local/libexec/amandad >/dev/null 2>/dev/null

The netcat-binary used in this run-file might also be called /usr/bin/nc on your system, depending on the OS-distribution you use.
Refer to http://netcat.sourceforge.net for details of netcat.

• • Link service directory into your svscan directory:

cd /service
ln -s /etc/amanda/supervise/amanda .

• • • If you are using (x)inetd, kick inetd/xinetd to make it read its config file. On most systems you can just execute kill -HUP inetd (or xinetd). On older systems you may have to kill it completely and restart it. Note that killing/restarting (x)inetd is not safe to do unless you are sure that no (x)inetd services (like rlogin) are currently in use, otherwise (x)inetd will not be able to bind that port and that service will be unavailable.
    • If you are using the daemontools, svscan should detect and start your new services automatically.
    • If you intend to back up xfs filesystems on hosts running IRIX, you must create the directory /var/xfsdump/inventory, otherwise xfsdump will not work.

• GNU tar
• dump
• Windows client - Samba
• Client side encryption
• pre and post- backup scripts