This page describes the environmental requirements you should verify before running the install program. The Amanda Enterprise 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 Server, which also called the Amanda Server or backup server.
Backup server performs various CPU, Memory, Network, and Disk intensive operations. While hardware requirements will vary based on your backup environment, we recommend a server with at least 4GB of memory and a modern quad-core server-class CPU. The bandwidth of the network link between backup server and your network switch is also very critical. If network bonding is supported by your switch, we recommend providing a bonded connection to the backup server.
setsebool -P allow_execstack on
The following packages are required on the Amanda backup server and clients:
Program Dependencies: The following programs are needed for Linux backup server and client
These additional programs are required on the Linux backup server
Library Dependencies: The server packages are 32bit, so 32bit libraries are required. Native 32bit systems already have the required libraries. 64bit systems require the 32bit compatibility libraries. They are available for RHEL/CentOS/SLES/Oracle Enterprise/Fedora/Open Suse Linux platforms. On Ubuntu/Debian platforms, they may not be available for older platforms. On Ubuntu/Debian platforms, they may not be available for older platforms. See Linux Debian/Ubuntu for more details.
These packages are installed by default on most Linux distributions. If you need to add them, you can use yum, apt-get, or yast. Packages can be obtained from the distribution media or from a distribution repository (run either as root):
#yum install package_name
or
#apt-get install package_name
or
#yast -i package_name
In the case of yast on SLES, you can also use the YaST Online Update (YOU) to install new package and to keep the SLES distribution updated (which is recommended).
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
The Amanda backup server requires following additional 32-bit Debian package:
Note for 64bit Debian/Ubuntu Amanda servers: The best way to install 32-bit version library packages on 64bit Debian/Ubuntu platforms is with getlibs, which is described in more detail in this Zmanda Knowledgebase article. Alternatively, libreadline5 and libreadline6 32bit version can be obtained by installing lib32readline5 package and lib32readline6 package respectively.
The Amanda backup client requires the following 32-bit packages; AE 64-bit backup client requires the following 64-bit packages
To run the Amanda Enterprise Backup Server (or a 32-bit Amanda client) on 64-bit RedHat/CentOS/Oracle Linux/Fedora/Open Suse requires these same packages in 32-bit versions (please note that these packages might depend on other packages and so use tools such as yum, apt-get to install these packages).
ncurses.i686
64bit RHEL6/Oracle Enterprise Linux 6 requires additional packages
On 64bit SLES 11 platforms, these packages are called
64-bit packages are required for Amanda Servers running Solaris10/Sparc; 32-bit packages are required for all Amanda clients, and servers running on Solaris/Intel and OpenSolaris. To account for inter-package dependencies, they should be installed in the order as listed. The following dependencies required on both client and server. The package names (i.e., what you specify when installing) are in boldface type. This dependency list is an attempt to document all direct Amanda dependencies and indirect dependencies (Amanda depends on a package that in turn depends on other packages).
SUNW packages can be found as part of Solaris distribution. Zmanda recommends that you install the CSW packages from http://www.opencsw.org/. Some package dependencies are pre-bundled for your convenience and are available at Zmanda network downloads page. Some packages mentioned below have other dependencies. It is easier to install other dependencies by using pkgutil tool available at the http://www.opencsw.org/get-it/pkgutil/
These dependencies are required on both server and client:
The installation order for dependencies for the common packages:
CSWcommon CSWiconv CSWlibidn CSWlibnet CSWsunmath CSWzlib CSWgdbm CSWbdb44 CSWexpat CSWgfile CSWgcc3corert CSWgcc3g++rt CSWggettext CSWgtar CSWmtx CSWreadline CSWfindutils CSWosslrt CSWosslutils CSWossldevel CSWossl CSWsasl CSWoldaprt CSWcurlrt CSWcurl
The following dependencies required only on the server:
The following dependency is required only on the client:
The dependencies are the same as listed above for Solaris 10, with the following addition:
Instructions for using pkgutil on Solaris 8 and 9 is different. Please see blastwave site for instructions.
Download and install the package dependencies available from the Zmanda Network download page when you select Mac OSX as the client platform.
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.
The amandabackup user must exist, and be added to the Users, Backup 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.
If you are installing on a system that doesn't have an amandabackup user, the installation will create the user with the correct rights (roles). If the user already exists, you may have to make these changes manually. Log in to the system as root, and type the following commands:
${BASEDIR}/usr/sbin/usermod -P "Media Backup,ZFS File System Management,ZFS Storage Management" ${amandabackup} >>${TMPFILE} 2>&1 zfs allow -ldu amandabackup mount,create,rename,snapshot,destroy,send,receive FILESYSTEM
On systems that do not support zfs allow, you can give the amandabackup user permission to manipulate ZFS filesystems by using the following command:
usermod -P "ZFS File System Management,ZFS Storage Management" amandabackup
index_server "localhost" # your amindexd server tape_server "localhost" # your amidxtaped server
Change "localhost" to match to the hostname of the Amanda backup server.
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.