This MindTouch Deki has expired; please contact your system administrator. Visit MindTouch.com for activation information.
Template:Amanda Enterprise 3.4 Pre-installation Checks >

Template:Amanda Enterprise 3.4 Pre-installation Checks

This page describes the environmental requirements you should verify before running the install program. 

Throughout this document, The Amanda Client refers the system being backed up by the Amanda Enterprise 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.
  • Amanda backup server. The Amanda backup server should have access to the media (tape, disk, changers) where the Amanda client backups will be stored on tapes or the backup process is managed (in case of NDMP). Amanda backup server runs on the ZBA which is a virtual appliance.

Package Dependencies

The following packages are required on the Amanda clients:

Linux Debian/Ubuntu

The Amanda backup client requires 32-bit version of following Debian packages;  Amanda 64-bit backup client requires the following 64-bit version Debian packages

  • libcurl3-gnutls
  • libglib2.0-0
  • libpcre3
  • libidn11
  • libssh2-1
  • libcurl3 or libcurl4 version >=7.13.2
  • libreadline5 or libreadline6 (depending on the platform)
  • libswitch-perl
  • libjson-perl
  • libencode-locale-perl
Redhat/CentOS/Oracle Enterprise Linux/SLES/Fedora/OpenSuse

The AE 32bit client requires the following 32-bit packages;  AE 64-bit backup client requires the following 64-bit packages

  • curl
  • readline
  • xinetd
  • glib2
  • termcap (not required on SLES/OpenSuse and RHEL/CentOS 6)
  • perl-Switch
  • perl-JSON
  • perl-Encode-Locale
  • perl-Data-Dumper

For RHEL/CentOS 5 and earlier versions and Fedora, please install the following packages:

  • glib2.i386 or glib2.i686
  • curl.i386 or curl.i686
  • readline.i386 or readline.i686
  • termcap.noarch 
  • libidn.i386 or libidn.i686
  • openldap24-libs.i386
  • ncurses.i686

  • libgcc.i686 (for fedora platforms only)

For RHEL/CentOS 6, please install the following packages:

  • glib2.i686
  • xinetd
  • ncurses-libs.i686 
  • libstdc++.i686
  • readline.i686 
  • glibc.i686
  • zlib.i686
  • perl-Switch
  • perl-JSON
  • perl-Encode-Locale
  • perl-Data-Dumper

For example: In case of 64bit RHEL6/CentOS 6/Oracle Enterprise Linux, following yum command line should be used (this list includes direct Amanda Enterprise and indirect dependencies)

# yum install glibc.i686 xinetd nss-softokn-freebl.i686 glib2.i686 libselinux.i686 gamin.i686 readline.i686 ncurses-libs.i686 zlib.i686 libstdc++.i686 libgcc.i686 perl-Switch perl-JSON perl-Encode-Locale perl-Data-Dumper 

On 64bit SLES 11 platforms, these packages are called

  • glibc-32bit
  • glib2  (includes both 32 a 64-bit libraries)
  • libcurl4-32bit
  • libreadline5-32bit
  • libidn-32bit
  • libncurses5-32bit

Solaris 10/11 and Open Solaris

32-bit packages for dependencies are required for Solaris clients.

It is easier to install dependencies by using Solaris pkgutil tool available at the http://www.opencsw.org/get-it/pkgutil/ It automatically get all indirect dependencies. Use the following pkgutil command to install dependencies on Solaris server (you can install gnupg2 instead of gnupg):

pkgutil -i gtar gnupg gawk libgcc_s1 mtx

Use the following pkgutil command to install dependencies on Solaris Client (you can install gnupg2 instead of gnupg):

pkgutil -i perl gtar gnupg libcurl4

Mac OSX 

Download and install the package dependencies available from the Zmanda Network download page when you select Mac OSX as the client platform.

Windows 

The amandabackup user must exist, and be added to the UsersBackup Operators, and Administrators groups. Windows clients must open inbound TCP ports 10080 and 10081, and outbound TCP ports 700:800. Windows application backups (licensed as separate agents) require that the Volume Shadow Copy Service be enabled and started. To prevent excessive memory consumption on application backup clients, Zmanda also recommends that you install the following VSS hotfix from Microsoft:

Link to Microsoft Knowledgebase

See the The Zmanda Windows Client User's Manual for further details on Windows client installation.

Post installation changes on Linux/Mac OS X/Solaris Amanda Clients

  • This section is not applicable for Windows clients.
  • Make sure there is a reverse name lookup record in the DNS for the Amanda server (FQDN if FQDN is used in the Amanda configuration files).
  • The .amandahosts file for the amandabackup user (~amandabackup/.amandahosts) on the client must authorize the Amanda server to run a backup.
  • The /etc/amanda/amanda-client.conf file must be edited on the client (if the client and server do not reside on the same machine). Specifically, the following entries must be edited:
index_server "localhost"        # your amindexd server
tape_server  "localhost"        # your amidxtaped server

Change "localhost" to match to the hostname of the  Amanda backup server.

  • If secure communication is required for restoration, ssh must be used for restoration. ssh is also required when restoring to a a MacOS X/Unix/Linux system that is not running the Zmanda Client software. To force the restore process to use ssh, edit /etc/xinetd.d/zmrecover on Linux systems to include the following line:
disable = yes

On MacOSX systems, run the following command: launchctl unload -w /Library/LaunchDaemons/org.amanda.zmrecover.plist. To re-enable the standard client restore mechanism, enter: launchctl load -w /Library/LaunchDaemons/org.amanda.zmrecover.plist.

Powered by MindTouch Deki v.8.08.2