Setting up the Tivoli Storage Manager client for backups
Deployment options: Netezza Performance Server for Cloud Pak for Data System
Learn how to set up the Tivoli Storage Manager (TSM) client for a backup.
Before you begin
- The client must be installed on the system, inside the container where Netezza Performance Server is installed.
- Make sure that Tivoli Storage Manager is installed as described in Installing the Tivoli Storage Manager (TSM) server on Linux .
Note: If you have any issues when you're installing and or setting up TSM, contact TSM
Support.
Procedure
-
Download the TSM client installation package from Fix Central. For example,
8.1.10.0-TIV-TSMBAC-LinuxX86.tar
- As
root
, unpack the package inside the container:
Example:tar -xvf <installation_package>
# tar -xvf 8.1.10.0-TIV-TSMBAC-LinuxX86.tar GSKit.pub.pgp README.htm README_api.htm RPM-GPG-KEY-ibmpkg TIVsm-API64.x86_64.rpm TIVsm-APIcit.x86_64.rpm TIVsm-BA.x86_64.rpm TIVsm-BAcit.x86_64.rpm TIVsm-BAhdw.x86_64.rpm TIVsm-JBB.x86_64.rpm TIVsm-WEBGUI.x86_64.rpm TIVsm-filepath-source.tar.gz gskcrypt64-8.0.55.14.linux.x86_64.rpm gskssl64-8.0.55.14.linux.x86_64.rpm update.txt
- Install the contents of the package as
root
, inside the container:
Example:rpm -ivh gskcrypt64-8.0.55.14.linux.x86_64.rpm
# rpm -ivh gskcrypt64-8.0.55.14.linux.x86_64.rpm warning: gskcrypt64-8.0.55.14.linux.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fbbfca9c: NOKEY Preparing... ################################# [100%] Updating / installing... 1:gskcrypt64-8.0-55.14 ################################# [100%]
Example:rpm -ivh gskssl64-8.0.55.14.linux.x86_64.rpm
# rpm -ivh gskssl64-8.0.55.14.linux.x86_64.rpm warning: gskssl64-8.0.55.14.linux.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fbbfca9c: NOKEY Preparing... ################################# [100%] Updating / installing... 1:gskssl64-8.0-55.14 ################################# [100%]
Example:rpm -ivh TIVsm-API64.x86_64.rpm
# rpm -ivh TIVsm-API64.x86_64.rpm warning: TIVsm-API64.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID be1d0ddb: NOKEY Preparing... ################################# [100%] Updating / installing... 1:TIVsm-API64-8.1.10-0 ################################# [100%]
Example:rpm -ivh TIVsm-APIcit.x86_64.rpm
# rpm -ivh TIVsm-APIcit.x86_64.rpm warning: TIVsm-APIcit.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID be1d0ddb: NOKEY Preparing... ################################# [100%] Updating / installing... 1:TIVsm-APIcit-8.1.10-0 ################################# [100%]
Example:rpm -ivh TIVsm-BA.x86_64.rpm
# rpm -ivh TIVsm-BA.x86_64.rpm warning: TIVsm-BA.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID be1d0ddb: NOKEY Preparing... ################################# [100%] Updating / installing... 1:TIVsm-BA-8.1.10-0 rpm -ivh TIVsm-BAcit.x86_################################# [100%]
Example:rpm -ivh TIVsm-BAcit.x86_64.rpm
# rpm -ivh TIVsm-BAcit.x86_64.rpm warning: TIVsm-BAcit.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID be1d0ddb: NOKEY Preparing... ################################# [100%] Updating / installing... 1:TIVsm-BAcit-8.1.10-0 ################################# [100%]
Example:rpm -ivh TIVsm-BAhdw.x86_64.rpm
# rpm -ivh TIVsm-BAhdw.x86_64.rpm warning: TIVsm-BAhdw.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID be1d0ddb: NOKEY Preparing... ################################# [100%] Updating / installing... 1:TIVsm-BAhdw-8.1.10-0 ################################# [100%]
- Update the
dsm.sys
anddsm.opt
files at /opt/tivoli/tsm/client/api/bin64:- Copy the
dsm.sys
anddsm.opt
files:cd /opt/tivoli/tsm/client/api/bin64 # cp dsm.opt.smp dsm.opt # cp dsm.sys.smp dsm.sys
- Add server name and node name entries to the
dsm.sys
file:
Example:cat /opt/tivoli/tsm/client/api/bin64/dsm.sys
$ cat /opt/tivoli/tsm/client/api/bin64/dsm.sys ************************************************************************ * * * Sample Client System Options file for UNIX (dsm.sys.smp) * ************************************************************************ * This file contains the minimum options required to get started * using the Backup-Archive Client. Copy dsm.sys.smp to dsm.sys. * In the dsm.sys file, enter the appropriate values for each option * listed below and remove the leading asterisk (*) for each one. * If your client node communicates with multiple servers, be * sure to add a stanza, beginning with the SERVERNAME option, for * each additional server. ************************************************************************ SErvername 9.10.20.16 COMMMethod TCPip TCPPort 1500 TCPServeraddress 9.10.20.16 NODENAME 9.70.203.26_IPS
Where9.10.20.16
is the server where TSM server installed.9.70.203.26_IPS
is the node name that is registered for client when Installing the Tivoli Storage Manager (TSM) server on Linux.
- Add a server name entry to the
dsm.opt
file:
Example:cat /opt/tivoli/tsm/client/api/bin64/dsm.opt
$ cat /opt/tivoli/tsm/client/api/bin64/dsm.opt ************************************************************************ * * * Sample Client User Options file for UNIX (dsm.opt.smp) * ************************************************************************ * This file contains an option you can use to specify the * server to contact if more than one is defined in your client * system options file (dsm.sys). Copy dsm.opt.smp to dsm.opt. * If you enter a server name for the option below, remove the * leading asterisk (*). ************************************************************************ *SErvername A server name defined in the dsm.sys file SErvername 9.10.20.16
- Copy the
- Update the
dsm.sys
anddsm.opt
files at /opt/tivoli/tsm/client/ba/bin/.Ensure that you run the command with the correct file path; /opt/tivoli/tsm/client/ba/bin/ instead of /opt/tivoli/tsm/client/api/bin64. - Log in as the
nz
user and run the backup/restore commands:$ export DATASTORE_SERVER=9.10.20.16 $ export DATASTORE_POLICY=NETEZZA $ export TSM_PASSWD=netezza1
Example:nzbackup -db test1 -connector tsm
$ nzbackup -db test1 -connector tsm Backup of database test1 to backupset 20200619115620 completed successfully.
For parameters that can be used with the nzbackup command and the available -connector options, see Command syntax for nzbackup.
Note: 3rd party installations don't persist across upgrade. You must reinstall 3rd party software after Netezza Performance Server is upgraded.When the Netezza Performance Server host container is installed, you must redeploy it for HA purposes. For more information, see Redeploying the container to 11.0.X.X.