This user guide explains how to use the Bulk deployment of Zmanda Linux Clients. Using this feature, you can automate Zmanda Linux client installation for numerous connected Linux systems.
Last updated
Was this helpful?
Source machine: Any CentOS/Fedora machine with internet access.
Destination machine(s): Any Linux machine(s) wherein the user(s) belongs to a sudo group like a wheel with the ‘NOPASSWD’ attribute enabled.
All the destination machines should share the same credentials.
A file(.txt format) listing the IP addresses of all the destination machines where the Zmanda Linux client/agent needs to be installed.
The source machine user enters sudo mode.
When the repository is cloned, a number of files are copied from the kit. The user just needs to run the main.sh file. git clone <repo_name>
The user will then execute the script by entering ./main.sh.
Firstly, the source machine OS is identified and displayed on the terminal.
The script will check if SSHpass is installed on the source machine or not. If installed, ‘sshpass was already installed' is displayed; else, the script will start to install SSHpass. If the installation fails for some reason, then ‘Failure in installing sshpass, please find this log log_sshpass.txt’ is displayed. The user can check the file to determine the reason for the failure and resolve it accordingly.
The script will prompt the user to specify whether the IP version being used is IPv4 or IPv6. Enter the correct option (ipv4 or ipv6) to proceed with the installation. If anything wrong is entered, the script exits from the installation immediately. Note: Highlighted lines are where the user needs to respond
The script will ask you to enter the Zmanda backup server IP address according to the version of the IP specified in the last step. If anything wrong is entered, the script exits from the installation immediately.
The script will then check for the Ip.txt file on the source machine. If the IP file is not found, the script will exit from the installation immediately. And if the file exists on the source machine, then the script will display ‘<directory path of the IP.txt> exists’. Note: The IP addresses can also be passed on via other file formats like CSV with a slight modification to the script. The modified script can be obtained from the support team if needed.
The script will then ask for the destination machine credentials, i.e., username and password.
The credentials are then passed on by the script for verification. If the verification is successful, the script will display the total number of IP addresses present in the Ip.txt file.
The script will start to connect to each of the destination machines sequentially. The script will attempt to ssh into the destination machine. If the ssh fails, then the script will display ‘cannot connect to the <IP address> host, please find this log_cannot_connect_”<IP address>”,txt’.
Once the connection is successfully, the script will identify the distribution of Linux and the version running on the particular destination machine.
The script will then download the binaries from the Network Zmanda on the source machine.
The script will then begin to install the Zmanda backup client and Zmanda backup extensions in the following sequence:
Check whether the corresponding Zmanda backup client and Zmanda backup extension packages are installed on the destination machine or not. If they are installed, the script will display ‘packages already exists’.
If the packages are not installed, they will be first copied from the source machine onto the destination machine.
The packages are then extracted to obtain the run files.
The Zmanda backup client and Zmanda backup extensions are lastly installed on the destination machine
Step 14 is repeated sequentially for all the destination machines whose IP addresses are listed on the IP.txt file. After installing the packages, the script will then add the Zmanda backup server IP to /var/lib/amanda/.amandahosts and /etc/amanda/amanda-client.conf files.
