Template:AAE Pre-installation Checks

Version as of 03:20, 13 May 2024

to this version.

Return to Version archive.

View current version

This page describes the environmental requirements you should verify before running the install program. The Amanda Enterprise Edition components required on each are described in Downloading and Installing Amanda Enterprise Components.

Throughout this document, The Amanda Client refers the system being backed up by the Amanda Enterprise Edition Server, which also called the Amanda Server or backup server.

  • Identify the hosts and filesystems to be protected using Amanda software. The list of hosts to be protected are the Amanda backup clients. The Amanda backup clients and the filesystems or directories to be backed up on each client will need to be specified during Amanda configuration.
  • Identify the Amanda backup server. The Amanda backup server should have access to the media (tape, disk, changers) where the Amanda client backups will be stored. Any Amanda client can also act as an Amanda server, and it is recommended that every Amanda server also be a backup client. In selecting your Amanda backup server machine, keep in mind that the server might use a significant amount of memory during backup runs, and that it must have good network connectivity to all Amanda clients.

Amanda Enterprise Edition backup server requirements

  • The Amanda server and clients must have the latest service packs or updates to the distribution installed.
  • Amanda server and client cannot be installed on an NFS-mounted file systems.
  • To run the Rapid Installer, the Amanda Server requires 256MB of free memory. You should have at least 500MB of disk space, and you should not install the ZMC itself (/opt/zmanda/amanda) on an NFS partition.
  • In addition to the space required for the software itself, you should ensure that there is always 10% free in the Zmanda installation and temporary directories. If Amanda Enterprise Edition runs out of space on either of these directories while a backup is in progress, the backup will fail with MySQL errors similar to the following:
System Error
DBD::mysql::db do failed: Incorrect key file for table
'/var/tmp/#sql_24b8_0.MYI'; try to repair it at
/opt/zmanda/zmc/bin/amreport_wrapper line 105.
    8:51:26, Mon Mar 17, 2008:ZMC Database Query failed: mysql query
failed:Incorrect key file for table '/var/tmp/#sql_24b8_0.MYI'; try to repair it
If you encounter messages like this, try increasing the amount of available disk space in the relevant directories.
  • The following TCP ports must be open:
    • Amanda server: must open inbound TCP ports 11000:11040.
    • Non-Windows Amanda clients must open inbound TCP port 10080 and outbound TCP ports 11000:11040.
    • Windows clients must open inbound TCP ports 10080 and 10081, and outbound TCP ports 700:800.
  • Internal firewalls and selinux policy must not prevent PHP processes from using HTTP over the loopback address 127.0.0.1

Backup Server Package Dependencies

The following packages are required on the Amanda backup server:

Linux

  • compat-libstdc++-33-3: The GNU C and GNU C++ Compiler runtime libraries

These packages are installed by default on most Linux distributions. If you need to add them, you can use yum or apt-get, either from the distribution media, or from a distribution repository (run either as root):

#yum install package_name

or

#apt-get install package_name

Solaris 10 (Both Sparc and Intel Architectures)

32-bit versions of the following packages are required.

  • perl
  • mailx: The mailx package can be found as part of the OS distribution. The mailx package must be configured to send mail from the Amanda server to the backup administrator.
  • gcc3g++rt: The GNU C++ Compiler runtime libraries
  • CSWgcc3corert: The GNU C Compiler runtime libraries

The Zmanda Network downloads page collects all of these packages in a downloadable tar archive (which is made available after you select a platform to download). If necessary, download the tar archive to the local system, extract it, and run pkgadd as the superuser to install it:

# pkgadd -d package_name

Backup/restore client requirements

For restores to work through the ZMC, the client (regardless of platform) must keep TCP port 10081 available for the Zmanda recovery process. Refer to your OS network configuration documentation for details on opening ports for applications.

Package dependencies for Backup Clients

Amanda Enterprise Edition requires the 32-bit versions of all packages.

Linux

  • perl
  • xinetd
  • openssh (required on clients being restored to)

These programs are installed by default on most Linux distributions. If you need to add them, you can use yum or apt-get to install them, either from the distribution media, or from a distribution repository (you run either as root):

#yum install package_name

or

#apt-get install package_name

Solaris 10 (both Sparc and Intel Architectures)

  • perl
  • SUNWcsu
  • SUNWsshcu
  • SUNWgzip
  • SMCtar (version 1.15.1 or greater)
  • SMCgpgme
  • SMCgrep
  • SMCcoreu

The Zmanda Network downloads page collects all of these packages in a downloadable tar archive (which is made available after you select a platform to download). If necessary, download the tar archive to the local system, extract it, and run pkgadd as the superuser to install it:

# pkgadd -d package_name
  • Clients being restored to must also have the SUNWsshcu package installed. In addition, the following entry must be added to the $HOME/.ssh/environment configuration file:
PATH="/opt/csw/bin:/opt/sfw/bin:/usr/csw/bin:/usr/sfw/bin:/usr/bin:/usr/local/bin:/usr/sbin"

Libraries installed in non-standard locations

Some of the dependency packages listed above may change the location of runtime libraries when installed or updated. If this happens, backups may fail with a message indicating that a required library or file could not be found. If this happens, you must update the system search path so that Amanda Enterprise can find the file(s). The Solaris crle (Configure Runtime Linking Environment) provides a simple way to do this:

1. Run crle without any parameters and pipe the output to a file to save the original configuration:

crle > ld.config.old

2. Run crle with the -c and -l options to update the path. For example:

crle -c /var/ld/ld.config -l /lib:/usr/lib:/lib/secure:/usr/lib/secure:/usr/local/lib

Will update the /var/ld/ld.config to use /lib:/usr/lib:/lib/secure:/usr/lib/secure:/usr/local/lib as the search path. Running crle without parameters will display the current search paths in effect. Refer to the Solaris documentation for further details on crle.

Windows (2003 Server, XP, and Vista)

Windows clients must open inbound TCP ports 10080 and 10081, and outbound TCP ports 700:800. Windows application backup (licensed separately) requires that the Volume Shadow Copy Service be enabled and started. See the The Zmanda Client for Windows User's Manual for details.