Scribd
Upload
144 views

Quick Start Guide For Data Backup: Backup Archive Client Installation For Linux

1. Download and extract the Backup Archive Client installation file for Linux. Delete the installation file and folder after setup. 2. Install required packages that depend on your Linux distribution being RPM or DEB based. This includes GSKit and Tivoli Storage Manager API packages. 3. Configure the BAclient using sample configuration files, specifying the backup node name and server address obtained from the management portal.

Uploaded by

skizoufri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
144 views

Quick Start Guide For Data Backup: Backup Archive Client Installation For Linux

1. Download and extract the Backup Archive Client installation file for Linux. Delete the installation file and folder after setup. 2. Install required packages that depend on your Linux distribution being RPM or DEB based. This includes GSKit and Tivoli Storage Manager API packages. 3. Configure the BAclient using sample configuration files, specifying the backup node name and server address obtained from the management portal.

Uploaded by

skizoufri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Quick start guide for data backup: Backup

Archive Client installation for Linux


1 STEP
To install the software, use the root user or sudo rights.
1.1. In order to install Backup Archive Client (BAclient) follow the link and proceed downloading of
installation. https://www.deac.eu/support/user-mannuals/installation-files/en/installation-files.html
From the list of files select the tar* format file without language abbreviation. Other files in the folder are interface
language files that may be used if necessary. The files with README in the name are additional documents and
more detailed information about the software.
1.2. Unzip the downloaded archive file.
tar xvf 7.x.x.x-TIV-TSMBAC-LinuxX86.tar
After the installation is finished, the folder and the downloaded installation file can be deleted.

2 STEP
Install the program that may vary to different Linux distributions. Installation packages are available in two
different formats: RPM (RHEL, SLES, Centos, etc.) and DEB (Ubuntu, Debian).
2.1. Steps to be taken when choosing the RPM-based installation packages.
2.1.1. Install GSKit packages.
rpm -Uvh gskcrypt64-8.x.x.x.linux.x86_64.rpm gskssl64-8.x.x.x.linux.x86_64.rpm
2.1.2. Install Tivoli Storage Manager API.
rpm -ivh TIVsm-API64.x86_64.rpm
2.1.3. Make a backup installation for Java client, command line client, web client and the
documentation*:
rpm -ivh TIVsm-BA.x86_64.rpm
* This document does not cover the configuration of Java web client.

2.2. Steps to be taken when choosing DEB-based installation packages.


2.2.1. Install GSKit packages.
sudo dpkg -i gskcrypt64_8.0-50.40.linux.x86_64.deb gskssl64_8.0-50.40.linux.x86_64.deb
2.2.2. Install Tivoli Storage Manager API.
sudo dpkg -i tivsm-api64.amd64.deb
2.2.3. Make a backup installation for Java client, command line client, web client and the
documentation*:
sudo dpkg -i tivsm-ba.amd64.deb
* This document does not cover the configuration of Java web client.
3 STEP
3.1. Configure BAclient by using prepared configuration file sample. Samples with name dsm.opt and dsm.sys
can be found here: ftp://ftp.backuppro.eu/Linux/BA/v7r1/.
3.2. Copy and save configuration file samples in BAclient folder: /opt/tivoli/tsm/client/ba/bin/
3.3. Configuration file dsm.opt can be left without changes.

3.4. Make the necessary corrections in dsm.sys configuration file sample. Fill in fields marked with “?” sign
in the Custom settings field:
a) NODENAME: specify the backup node name, which was automatically assigned in BaaS portal, in the
field TSM Node id.
b) TCPSERVERADDRESS: specify the backup node server address, which was automatically assigned in
BaaS portal, in the field TSM server address.
Quick Start Guide on using Management (Cloud) portal can be found here.

3.5. Additional Settings section is for additional configurations (ssl, cripts, compressions, other
“management class”). These settings can be left by default.
3.6. Default Include/Exclude settings section is for changing exclusion lists. These settings can be left by
default.
3.7. Default settings section is for default configuration parameters. These settings can be left by default.

4 STEP
In order to save the password locally and for creating automatic data backup it is necessary to connect to
the program. Also, for safety reasons, it is necessary to change default password.
4.1. When connecting for the first time enter user id and password.
a) User id: TSM Node id or node name. It was given in clause 3.4. so keep it unchanged.
b) Password: Node password that was generated automatically when creating new node in BaaS
portal.
Quick Start Guide on using Management (Cloud) portal can be found here.

4.2. Run tsm command line program, which provides information on the parameters of the session with the
server:
dsmc q ses
4.3. Change password by entering current password and then entering new password:
dsmc set password

5 STEP
5.1. Set and configure the setup for creating data backup schedule that may vary to different Linux
distributions.
5.2. Steps to be taken when configuring the system service “dsmcad”. We recommend using “dsmcad” in the
following cases:
a) when using Linux distributions with the RPM-based installation package.
b) when using configuration file sample.
c) when not using ssl for connection with the backup server.

5.2.1. Add service with default settings for those system services that are launched automatically.
chkconfig --add dsmcad
5.2.2. Restart the service.
service dsmcad restart
5.3. Steps to be taken when configuring data backup schedule with system process “dsmc sched”. We
recommend using “dsmc sched” in the following cases:
a) when using Linux distributions with DEB-based installation package.
b) when not using dsmcad service.
c) when using ssl for connection with backup server.
Execute the command:
dsmc sched

5.3.1. In case of using “dsmc schedule” process, it is necessary to delete or comment the default setting
“managedservices schedule” of the configuration file dsm.sys (see Step 3) by adding at the beginning of
the line * or by replacing it with “managedservices webclient”, in case of using tsm web client.
5.3.2. In order to run the process with its staring at the same time, several technique may be used:
a) by creating rc script.
b) by adding system startup file /etc/inittab.
TSM::once:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler
c) by adding system startup file /etc/rc.local.
/usr/bin/dsmc sched > /dev/null 2>&1 &

Warning. In order to activate changes, it is necessary to restart process “dsmc schedule” each time when
changing TSM client configurations.

6 STEP
6.1. Make a backup copy to random folder in order to check whether the system works correctly and to enter
and save the encryption key.
a) For successful creation of automated data backup with switched encryption, it is necessary to specify
the encryption key. Encryption key will be required at the first backup time.
b) Make a manual data backup by using the command line dsmc. For example, run the incremental
backup for folder /root/, its sub-folder and for their files by using Linux console:
dsmc Incremental /root/ -subdir=yes
6.2. Enter encryption key.
Warning. Keep the encryption key in a safe place, as no data will be available without a key!

7 STEP (optional)
Data restore by using command line dsmc
7.1. Possible action sequences:
a) To run BAclient and then execute commands.
b) To run BAclient with already defined parameters.

The discharge list of available backups in the directory "/root /".


The system will show only last actual versions.
dsmc query backup /root/
The discharge list of available backups in the directory "/root /".
The system will show also inactive (deleted, changes) actual versions.
dsmc query backup /root/ -inactive
The discharge list of available backups in the directory "/root /" and subdirectories.
The system will show only last actual versions.
dsmc query backup /root/ -subdir=yes
Restore the active version of a file.
The system will make a restore and will report about status changing.
dsmc restore /root/error.log
Open restoration interface, where all active and inactive files are available in the directory "/root/".
The necessary files can be selected and restored.
dsmc restore -pick -inactive /root/

More information in IBM documentation here.

You might also like