- a. AMANDA can optionally make use of the following packages to back up
- different types of clients or clients with different filesystem dumping
- programs. If you wish to use GNU-tar to back up filesystems, it is
- recommended to use GNU-tar 1.13.25. Plain GNU-tar 1.12 needs to be patched
- to handle large files (> 2GB). Plain GNU-tar 1.13 creates bad index-lists
- which amrecover cannot handle, as does the rarely used GNU-tar 1.13.9x,
- which changed the index-format again in an incompatible way.
- If you need to use GNU-tar 1.12, get it at
- ftp://ftp.gnu.org/pub/gnu/tar/tar-1.12.tar.gz
- and apply the patch from patches/tar-1.12.patch. The first hunk may be
- enough, unless it's a SunOS4 host. Read more about the patches in the
- patch file itself.
- GNU-tar 1.13.25 can be found at:
- ftp://alpha.gnu.org/pub/gnu/tar/tar-1.13.25.tar.gz
- Samba allows Unix systems to talk to PC clients. AMANDA can back up
- Microsoft Windows clients using Samba:
- http://www.samba.org
- Read Backup_PC_hosts_using_Samba for configuration tips and known
- limitations.
- Look at http://www.amanda.org/patches.html for up to date information on
- patches.
- b. If you wish to make use of some of the scripts that come with AMANDA, you
- will need to install Perl. You can get Perl from any CPAN site. ftp://
- ftp.cpan.org/pub/CPAN/src/perl-5.6.1.tar.gz
- c. One of the programs included in this package is amplot, which reads a data
- file that AMANDA generates for each dump and translates that information
- in it into a nice picture that can be used to determine how your
- installation is doing and if any parameters need to be changed. To use
- amplot, you need a version of awk that understands command line variable
- substitutions, such as nawk or gawk, which is available from
- ftp://ftp.gnu.org/pub/gnu/gawk/gawk-3.1.1.tar.gz
- Amplot also required that gnuplot be installed on your system. Gnuplot is
- available at
- http://www.gnuplot.org/ ftp://ftp.gnuplot.org/pub/gnuplot
- d. The process of building AMANDA requires that some other packages be
- installed on your system. The following packages are used:
- ftp://ftp.gnu.org/pub/gnu/readline/readline-4.2.tar.gz amrecover
- optionally uses the readline library for its command-line edition
- mechanisms. This library itself requires either termcap, curses or
- ncurses. termcap is preferred, and it may be obtained from: ftp://
- ftp.gnu.org/pub/gnu/termcap/termcap-1.3.tar.gz
- If you wish to edit and enhance AMANDA, you may need to install the
- following tools. Autoconf and automake are required if you are going to
- rebuild the Makefiles and auto configuration scripts. Bison is only needed
- if you are going to work on the index server and client code.
- ftp://ftp.gnu.org/pub/gnu/autoconf/autoconf-2.53.tar.gz ftp://ftp.gnu.org/
- pub/gnu/automake/automake-1.6.3.tar.gz ftp://ftp.gnu.org/pub/gnu/bison/
- bison-1.27.tar.gz ftp://ftp.gnu.org/pub/gnu/flex/flex-2.5.4a.tar.gz
- e. Read about the different configuration options available for building and
- running AMANDA. To see the options, do both:
-
- a. Run
-
- ./configure --help
-
- to see the available options that configure takes.
- b. Read the example/config.site file which gives longer descriptions to
- the same options as in step a).
-
- f. Choose which user and group you will run the dumps under. Common choices
- for user are `bin' or another user specifically created for AMANDA, such
- as `amanda'; common choices for group are `operator' or `disk'. If you do
- not specify --with-user=<username> and --with-group=<groupname>, configure
- will abort. Also choose the default name for your configuration, such as
- `csd' or `DailySet1'). This name is used by the AMANDA commands to choose
- one of multiple possible configurations. You may specify it using the --
- with-config=<confgname>.
- g. Decide where AMANDA will live. You need to choose a root directory for
- AMANDA. Let this root directory be called $prefix. Unless you change the
- default behavior with the appropriate command line options, AMANDA will
- install itself as. Listed below each directory is the appropriate
- configure option to change the location of this part of AMANDA.
-
- --sbindir=$prefix/sbin AMANDA server side programs
- --libexecdir=$prefix/libexec AMANDA backup client programs
- --libdir=$prefix/lib AMANDA dynamic libraries
- --with-configdir=$prefix/etc/amanda Runtime configuration files
- --with-gnutar-listdir=$prefix/var/amanda/gnutar-lists Directory for
- GNUtar lists (client)
- --mandir=$prefix/man Directory for manual pages
-
- Note that the GNU-tar listdir should be a local filesystem on each client
- that is going to be backed up with GNU tar. If it really must be NFS-
- mounted, make sure the filesystem is exported so that the client has root
- access to it.
- h. Decide if you are compiling AMANDA on a server only or a client only
- platform. If you have a particular operating system that will only be a
- AMANDA client and will never run as the master tape host, then add the --
- without-server option to configure. In the unlikely case that you have a
- particular operating system that will serve as the tape host and you do
- not wish to back up any machines that run this operating system, add the -
- -without-client option to the configure options. There are many other
- configuration switches for amanda. You may learn more about them by
- running `configure --help' and by reading examples/config.site.
- i. Now configure AMANDA. There are two ways of doing this. If you are running
- AMANDA on a single OS, then probably the first method works better for
- you. If you need to support multiple platforms, then the second method
- will work better.
-
- a. Run configure as non-root-user with the appropriate command line
- options. You will probably want to remember the command line options
- for future builds of AMANDA.
- b. Edit example/config.site and install it in the directory $prefix/etc
- or $prefix/share. When `configure' runs the next time it will look
- for this file and use it to configure AMANDA.
+* Amanda can optionally make use of the following packages to back up different
+ types of clients or clients with different filesystem dumping programs.
+
+ o GNU-tar:
+ If you wish to use GNU-tar to back up filesystems, it is recommended to use
+ GNU-tar 1.13.25. Plain GNU-tar 1.12 needs to be patched to handle large
+ files (> 2GB). Plain GNU-tar 1.13 creates bad index-lists which amrecover
+ cannot handle, as does the rarely used GNU-tar 1.13.9x, which changed the
+ index-format again in an incompatible way.
+ Refer to the Amanda_FAQ for more information about issues with the various
+ releases of GNU-tar.
+ If you need to use GNU-tar 1.12, get it at
+ ftp://ftp.gnu.org/pub/gnu/tar/tar-1.12.tar.gz
+ and apply the patch from patches/tar-1.12.patch. The first hunk may be
+ enough, unless it's a SunOS4 host. Read more about the patches in the patch
+ file itself.
+ GNU-tar 1.13.25 can be found at:
+ ftp://alpha.gnu.org/pub/gnu/tar/tar-1.13.25.tar.gz
+ o Samba:
+ Samba allows Unix systems to talk to PC clients. Amanda can back up
+ Microsoft Windows clients using Samba:
+ http://www.samba.org
+ Read Backup_PC_hosts_using_Samba for configuration tips and known
+ limitations.
+ Look at http://www.amanda.org/patches/ for up to date information on
+ patches.
+ o Perl:
+ If you wish to make use of some of the scripts that come with Amanda, you
+ will need to install Perl. You can get Perl from any CPAN site.
+ ftp://ftp.cpan.org/pub/CPAN/src/perl-5.6.1.tar.gz
+ o Awk:
+ One of the programs included in this package is amplot, which reads a data
+ file that Amanda generates for each dump and translates that information in
+ it into a nice picture that can be used to determine how your installation
+ is doing and if any parameters need to be changed. To use amplot, you need
+ a version of awk that understands command line variable substitutions, such
+ as nawk or gawk, which is available from
+ ftp://ftp.gnu.org/pub/gnu/gawk/gawk-3.1.1.tar.gz
+ o GNUplot:
+ Amplot also required that gnuplot be installed on your system. Gnuplot is
+ available at
+ http://www.gnuplot.org/ ftp://ftp.gnuplot.org/pub/gnuplot
+ o Other packages:
+ The process of building Amanda requires that some other packages be
+ installed on your system. The following packages are used:
+ ftp://ftp.gnu.org/pub/gnu/readline/readline-5.0.tar.gz
+ amrecover optionally uses the readline library for its command-line edition
+ mechanisms. (If you use a package-based distribution, check for the package
+ readline-devel-X.Y.rpm.) This library itself requires either termcap,
+ curses or ncurses. termcap is preferred, and it may be obtained from:
+ ftp://ftp.gnu.org/pub/gnu/termcap/termcap-1.3.1.tar.gz.
+ If you wish to edit and enhance Amanda, you may need to install the
+ following tools. Autoconf and automake are required if you are going to
+ rebuild the Makefiles and auto configuration scripts. Bison is only needed
+ if you are going to work on the index server and client code.
+ ftp://ftp.gnu.org/pub/gnu/autoconf/autoconf-2.53.tar.gz ftp://ftp.gnu.org/
+ pub/gnu/automake/automake-1.6.3.tar.gz ftp://ftp.gnu.org/pub/gnu/bison/
+ bison-1.27.tar.gz ftp://ftp.gnu.org/pub/gnu/flex/flex-2.5.4a.tar.gz
+
+* Read about the different configuration options available for building and
+ running Amanda. To see the options, do both:
+
+ o Run ./configure --help to see the available options that configure takes.
+ o Read the file example/config.site which gives longer descriptions to the
+ same options.
+
+* Choose which user and group you will run the dumps under. Common choices for
+ user are `bin' or another user specifically created for Amanda, such as
+ `amanda'; common choices for group are `operator' or `disk'. If you do not
+ specify --with-user=<username> and --with-group=<groupname>, configure will
+ abort. Also choose the default name for your configuration, such as `csd' or
+ `DailySet1'). This name is used by the Amanda commands to choose one of
+ multiple possible configurations. You may specify it using the --with-
+ config=<confgname>.
+* Decide where Amanda will live. You need to choose a root directory for
+ Amanda. Let this root directory be called $prefix. Unless you change the
+ default behavior with the appropriate command line options, Amanda will
+ install itself as. Listed below you find the appropriate configure-option for
+ each directory to change the location of this part of Amanda.
+
+ --sbindir=$prefix/sbin Amanda server side programs
+ --libexecdir=$prefix/libexec Amanda backup client programs
+ --libdir=$prefix/lib Amanda dynamic libraries
+ --with-configdir=$prefix/etc/amanda Runtime configuration files
+ --with-gnutar-listdir=$prefix/var/amanda/gnutar-lists Directory for GNU-tar
+ lists (client)
+ --mandir=$prefix/man Directory for manual pages
+
+ Note that the GNU-tar listdir should be a local filesystem on each client
+ that is going to be backed up with GNU-tar. If it really must be NFS-mounted,
+ make sure the filesystem is exported so that the client has root access to
+ it.
+* Decide if you are compiling Amanda on a server only or a client only
+ platform. If you have a particular operating system that will only be a
+ Amanda client and will never run as the master tape host, then add the --
+ without-server option to configure. In the unlikely case that you have a
+ particular operating system that will serve as the tape host and you do not
+ wish to back up any machines that run this operating system, add the --
+ without-client option to the configure options. There are many other
+ configuration switches for Amanda. You may learn more about them by running
+ configure --help and by reading examples/config.site.
+* Now configure Amanda. There are two ways of doing this. If you are running
+ Amanda on a single OS, then probably the first method works better for you.
+ If you need to support multiple platforms, then the second method will work
+ better.
+
+ o Run configure as non-root-user with the appropriate command line options.
+ You will probably want to remember the command line options for future
+ builds of Amanda.
+ o Edit examples/config.site and install it in the directory $prefix/etc or
+ $prefix/share. When configure runs the next time it will look for this file
+ and use it to configure Amanda.