Preserving backup and restore third-party installation across host failover

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn how to preserve backup and restore third-party installation across host failover.

Procedure

Install the Tivoli Storage Manager third-party client on ipshost1.
You can find the Tivoli Storage Manager 8.1 installation guide at https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/b_srv_install_guide_linux2.pdf.

Verify that the client is installed.

nzbnrver

Example:

[root@e1n1 nz]# nzbnrver
tsm32=8.1
tsm64=8.1
nb32=not installed
nb64=not installed
nw32=not installed
nw64=not installed

In the example, Tivoli Storage Manager 8.1 is installed on the ipshost.

Redeploy the ipshost1 container on e1n2 and e1n3.

Note: Make sure that the database is not running. If it is running, enter the ipshost1 container and stop the engine.

e1n1# docker exec -it ipshost1 bash
ipshost# su - nz
ipshost$ nzstate
ipshost$ nzstop
ipshost$ exit
ipshost# exit

Commit the current state of the container on e1n1.
```
e1n1# docker commit ipshost1 ipshost:custom
```

Save the ipshos1 container image to a file.

e1n1# docker save -o /opt/ibm/appliance/storage/ips/ips1_deployment/ipshost1_image_custom.tar ipshost:custom

Load the ipshost1 container image: e1n2 and e1n3.

e1n1# for dev in e1n{2..3}; do ssh $dev docker load -i /opt/ibm/appliance/storage/ips/ips1_deployment/ipshost1_image_custom.tar; done

Remove the container when it exits.

e1n1# for dev in e1n{2..3}; do ssh $dev docker rm ipshost1; done

Run the ipshost1 container image on e1n2.

e1n1# ssh e1n2 docker run -d -it -v /opt/ibm/appliance/platform/onecli/:/opt/ibm/OneCli:ro -v /etc/selinux/config:/etc/selinux/config:ro -v /etc/localtime:/etc/localtime:ro -v /opt/ibm/appliance/storage/ips/ipshost1/nz:/nz -v /opt/ibm/appliance/storage/ips/ipshost1/nzscratch:/nzscratch -v /opt/ibm/appliance/storage/ips/ipshost1/export_home:/export/home -v /opt/ibm/appliance/storage/ips/ipshost1/sedsupport:/var/lib/sedsupport -v /opt/ibm/appliance/storage/external_mnt/NFS:/external_mnt/NFS --privileged --cap-add=SYS_ADMIN --net=host --name=ipshost1 --dns=10.11.0.17 --dns-search=npsdomain --shm-size=152292m ipshost:custom

Run the ipshost1 container image on e1n3.

e1n1# ssh e1n3 docker run -d -it -v /opt/ibm/appliance/platform/onecli/:/opt/ibm/OneCli:ro -v /etc/selinux/config:/etc/selinux/config:ro -v /etc/localtime:/etc/localtime:ro -v /opt/ibm/appliance/storage/ips/ipshost1/nz:/nz -v /opt/ibm/appliance/storage/ips/ipshost1/nzscratch:/nzscratch -v /opt/ibm/appliance/storage/ips/ipshost1/export_home:/export/home -v /opt/ibm/appliance/storage/ips/ipshost1/sedsupport:/var/lib/sedsupport -v /opt/ibm/appliance/storage/external_mnt/NFS:/external_mnt/NFS --privileged --cap-add=SYS_ADMIN --net=host --name=ipshost1 --dns=10.11.0.18 --dns-search=npsdomain --shm-size=152292m ipshost:custom

Run the command.

e1n1# for dev in e1n{2..3}; do ssh $dev docker stop ipshost1; done

Start the database.

Note: After a host failover, you must update the /etc/hosts file for BNR third-party server manually.