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.
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
There are no special requirements for restoring files to a Linux/Solaris/MacOSX system that already has the Zmanda Client software installed, except when:
Under either of these circumstances, ssh is the preferred mechanism for executing restores. ssh is also required when restoring to a a MacOSX/Unix/Linux system that is not running the Zmanda Client software. To force the restore process to use ssh, edit /etc/xinetd.d/zmrecover to include the following line:
Or, 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.
The following packages are required on the Amanda backup server and any clients:
Solaris 10
Solaris 8 & 9
MacOSX
32-bit packages are required for 32-bit Linux. 64-bit packages are required for 64-bit Linux.
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
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. 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:
Zmanda recommends that you install these packages from Blastwave (http://www.blastwave.org/; detailed instructions are in the next section). For the most up-to-date package dependencies pre-bundled for your convenience, go to the Zmanda network downloads page and click Select your version->Select your OS, and then download the dependencies tar ball file.
These dependencies are required on both server and client:
The following dependencies required only on the server:
Instructions for Solaris package installation from Blastwave:
Install pkg-get. copy http://blastwave.network.com/csw/pkg_get.pkg into /tmp/
>pkgadd -d /tmp/pkg_get.pkg all
>copy http://blastwave.network.com/csw/wget-sparc.bin as /tmp/wget (Note: use wget-i386.bin for intel platforms) >chmod 755 /tmp/wget >PATH=/tmp:/opt/csw/bin:/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/usr/ccs/bin >export PATH
Edit the pkg-get configuration file
>vi /opt/csw/etc/pkg-get.conf
Enable http_proxy, ftp_proxy, export http_proxy ftp_proxy
Install the wget command
>pkg-get -i wget >rm /tmp/wget >PATH=/opt/csw/bin:/usr/sbin:/usr/bin:/usr/openwin/bin:/usr/dt/bin:/usr/ccs/bin >export PATH
Example command for installing gnu tar dependencies. Add all dependencies that are needed to the command line:
>/opt/csw/bin/pkg-get -i gtar
The dependencies are the same as listed above for Solaris 10, with the following addition:
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 Administrators, Users, and Backup Operators 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 hotfix from Microsoft:
Link to Microsoft Knowledgebase
See the The Zmanda Windows Client User's Manual for further details on Windows client installation.
If installing on system that doesn't have an amandabackup user, the installation will set up that 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
The following browsers have been tested and verified to work with the Zmanda Management Console:
In all cases you must have JavaScript enabled. Note that if JavaScript is enabled during a session either in the browser itself or in a plug-in such as NoScript, you must log out of the ZMC and then log in again to avoid potential problems with the interface.