This MindTouch Deki has expired; please contact your system administrator. Visit MindTouch.com for activation information.
Project: Amanda Enterprise 4.0 > Zmanda Client for Linux Manual

Zmanda Client for Linux Manual

Table of contents
No headers
 

 

 

Amanda Enterprise Edition Linux Client is a certified Amanda network backup software, tested and supported by Zmanda. This document has been prepared in conjunction with the Amanda Enterprise Edition Linux client 4.0 release. 

Amanda Enterprise Edition Linux client packages are available for the following distributions from the Zmanda network: 

·         Red Hat Enterprise 

·         CentOS 

·         Fedora 

·         Oracle Enterprise Linux 

·         Debian 

·         Ubuntu 

·         SLES  

·         Open Suse 

Please see supported platforms matrix for exact versions of above distributions that are supported by 4.0 release. 

This document confers about the Amanda Enterprise Edition Linux client installation, configuration and verification procedures. 

Installation 

Amanda Enterprise Edition Linux client packages are available from the Zmanda network download page. 

There are two packages - Amanda Enterprise Backup Client package and Amanda Enterprise Extensions Client package. Both packages are necessary. 

Pre-installation checklist 

Following packages should be installed on the client

 

·         Basic Utilities/Libraries 

o    Bash >= 4.2,  Coreutils,  Gawk,  

o    Glibc >= 2.17, zlib >= 1.2.2 

o    Libgcc >= 4.8, Libstdc++ >= 4.8 

·         System Utilities: [Systemd required] 

o    Logrotate, Cronie or Cron with /usr/bin/crontab 

o    Systemd >= 219,  

o    Libselinux >= 2.3 (with SELinux not active) 

·         Required components 

o    GnuPG2,  

o    Libexpat >= 2.1 

o    Libmount >= 2.19 

o    GNUtar >= 1.23 

 

These packages are installed by default on most Linux distributions. If you need to add them, you can use yumapt-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 the new package and to keep the SLES distribution updated (which is recommended). 

Client installation 

·         Amanda client installation must be performed as super user (in other words, the root user). 

·         Download the Amanda Enterprise Edition 4.0 Linux client package from the Zmanda network download page. There are two packages - amanda-enterprise-backup-client and amanda-enterprise-extensions-client. Both packages are required. 

·         Install the packages (amanda-enterprise-backup-client followed by amanda-enterprise-extensions-client)  

 

Yum install –y ./<package name> 

-- Or —- 

Apt-get install –y ./<package name> 

·         Amanda client configuration files are created during Amanda client package installation. The list of files that are modified during installation can be seen in the above installation command output. 

·         The logs for Amanda client package installation can be found in /var/log/amanda/install.log. If there are installation errors, messages are logged to the /var/log/amanda/install.err file. 

·         During the install, the amandabackup user is created, if it does not exist. Please assign a password for the amandabackup user. 

Post-installation checklist 

Note: These tasks must be performed as super user (the root user). 

·         Check installation log files 

The Amanda installation log can be found in /var/log/amanda/install.log and errors (if any) in /var/log/amanda/install.err.
Make sure there are no errors in the log files. 

·         Perform the post installation steps common to all Amanda clients. These steps are required for backup and recovery operations. 

Adding Client file systems in ZMC 

You can add the Linux file systems/folders using Zmanda Management Console. Use the Sources page in the Zmanda management console, to add folders from the Linux client (Select File systems from the menu). You will need to specify the Client NameHost Name and the Directory to back up. 

Amanda does not cross file system boundaries and thus each file system/partition should be entered as its own entry (separate DLE object). 

 

You can exclude files, specify data deduplication, encryption and compression to be used for the directory. Special files such as device files, named pipes, sockets, etc. can cause errors from the native backup and restore tools and they should be excluded from the backup. 

Linux file systems can be backed up using different Amanda methods (Amanda Backup Client Application). The default method is using gtar (GNU tar). Another method that is available is Schily tar (star). 

Schily tar allows the backup of extended POSIX attributes (such as SE Linux MAC labels). This application can be selected by checking Extended Attributes under Amanda Backup Client Application. In order to select this application requires starcommand to be installed on the Amanda client. 

You can specify different estimate algorithms and number of client backups that can happen in parallel (Client Max Backups). You can specify if you want only full or incremental or skip the backups of a Linux directory using Strategy field. 

Restoring Linux files 

Linux file systems can be restored using Zmanda Management Console Restore pages or using amrecover command. 

The restoration process begins at ZMC Restore What page. You can select the Backup Date entering the value or you can click the date stamp from ZMC Report Summary page. 

You can select the backup image's Host Name and Directory to be restored. If the Amanda indexes are available on the server, ZMC can provide the possible values (click the Edit button).  You can perform Restore All files from the image. 

Next step is specifying the conflict resolution policies and selecting where to restore to - Restore What page.

The possible Conflict Resolution Settings as shown above. If the Destination Directory is empty, you select  Overwrite Existing files/directories as conflict resolution.  You should specify the Destination Host Name, where backups will be restored to the Destination Directory.  The Destination Directory must be writable by amandabackup user and must have sufficient space to hold the whole backup image.  

If the Destination Host is not running Amanda client, ssh will be used for restoration. The ssh user and password will be required. The Destination User Name is used as the ssh user. 

After verifying the entered information, use the navigation to go to ZMC Restore Now page. 

 

Start the Restore process by clicking Restore button. The restore process will involve transferring the data to the Destination Host and extracting the specific files. 

 

 

 

 

 

 

 

 

 
Powered by MindTouch Deki v.8.08.2