Installing IBM Spectrum Archive Enterprise Edition
This chapter provides information about the distribution and installation of IBM Spectrum Archive Enterprise Edition (EE). It describes the following main aspects:
This section describes how to install the IBM Spectrum Archive EE program on a Linux system (in our example, we use a Red Hat-based Linux server system). It describes the installation routine step-by-step and reviews the prerequisites.
This optional section provides some background information about how to upgrade the tape library or tape drive firmware for use with the IBM Spectrum Archive EE.
This chapter includes the following topics:
4.1 Installing IBM Spectrum Archive EE on a Linux system
The first part of this chapter describes how to install the IBM Spectrum Archive EE program on a Linux server system. In our lab setup for writing this book, we used a Red Hat-based Linux system. All the examples in this chapter are based on that release.
Although IBM Spectrum Archive EE is based on the IBM Linear Tape File System standard components as IBM Spectrum Archive and the IBM Spectrum Archive Library Edition (LE), these components are all included with the IBM Spectrum Archive EE installation package.
Before you can start with the installation routines, you must verify the following installation prerequisites:
This section describes the tasks that must be completed before installing IBM Spectrum Archive EE.
•Installing IBM Spectrum Archive EE on a Linux server (see 4.3, “Installing IBM Spectrum Archive EE” on page 75)
This section describes how to install the IBM Spectrum Archive EE package on a Linux server.
4.2 Installation prerequisites for IBM Spectrum Archive EE
This section describes the tasks that must be completed before installing IBM Spectrum Archive EE.
Ensure that the following prerequisites are met before IBM Spectrum Archive EE is installed. For more information, see the other topics in this section if needed.
•Verify that your computer meets the minimum hardware and software requirements for installing the product. For more information, see Chapter 3, “Planning for IBM Spectrum Archive Enterprise Edition” on page 39.
•Verify that your user ID meets the requirements for installing the product (such as you are working with the root user ID or have the root administration permissions).
•Ensure that you reviewed all of the planning information that is described in Chapter 3, “Planning for IBM Spectrum Archive Enterprise Edition” on page 39.
•If the standard IBM Spectrum Archive LE is already installed, it must be uninstalled before IBM Spectrum Archive EE is installed. For more information, see 10.4, “IBM Spectrum Archive EE interoperability with IBM Spectrum Archive products” on page 330.
•Ensure that all prerequisite software is installed, as described in 4.2.1, “Installing the host bus adapter and device driver” on page 75.
•Ensure that the host bus adapter (HBA) and device driver are installed, as described in 4.2.1, “Installing the host bus adapter and device driver” on page 75.
•Determine the distribution package for IBM Spectrum Archive EE that is required for your system.
•For IBM Spectrum Scale prerequisites, see 3.5, “Hardware and software setup” on page 56.
4.2.1 Installing the host bus adapter and device driver
This section describes how to install the HBA and its device driver for use with IBM Spectrum Archive EE.
To install the HBA and its device driver, see the documentation that is provided by the HBA manufacturer.
If the HBA attached to the tape library is an Emulex adapter, add the following line to the /etc/modprobe.d/lpfc.conf file:
options lpfc lpfc_sg_seg_cnt=256
Then, restart the server system for the change to take effect.
For more information about fixes and updates for your system’s software, hardware, and operating system, see IBM Support’s Fix Central web page.
For more information about HBA interoperability, see this IBM System Storage Interoperation Center (SSIC) web page.
4.3 Installing IBM Spectrum Archive EE
This section describes the process that is used to install IBM Spectrum Archive EE package. This installation package is provided by IBM to you on a DVD.
Consider the following points:
•Information that is contained in the readme file and installation file that are provided with the IBM Spectrum Archive EE distribution package supersedes information that is presented in this book and the online IBM Documentation.
•The IBM Spectrum Archive EE license does not entitle customers to use any other IBM IBM Spectrum Protect components or products. All components that are needed to migrate data to the LTFS file space are integrated into IBM Spectrum Archive EE. They also are part of the provided installation package and IBM Spectrum Archive EE license and are to be used only in this context.
•If IBM Spectrum Archive LE is already installed, it must be uninstalled before IBM Spectrum Archive EE is installed.
If IBM Spectrum Archive EE is installed (such as an older version), it must be uninstalled before the latest version of IBM Spectrum Archive EE is installed. To update the EE package, an installation script (ltfsee_install) is provided that does the automatic uninstallation during the software update. The next sections show you how to use this IBM Spectrum Archive EE installation script for different purposes and maintenance.
It also is possible to install, upgrade, or uninstall IBM Spectrum Archive EE manually. For more information, see 10.4, “IBM Spectrum Archive EE interoperability with IBM Spectrum Archive products” on page 330.
 
4.3.1 Extracting binary rpm files from an installation package
This first task lists the necessary steps to perform before binary rpm files are extracted. It also presents the available methods for extracting binary rpm files from an installation package for IBM Spectrum Archive EE on a Linux server system.
Interactive console mode is the method that is used for extracting binary rpm files from an installation package.
Before you use any of these methods to extract the IBM Spectrum Archive EE binary rpm files, you must confirm or set the run permission of the installation package.
 
Important: The ltfsee-[version]-[buildlevel].bin installation package includes rpm files for the revision and supported platforms.
Before the IBM Spectrum Archive EE binary rpm files are extracted from an installation package, complete the following steps:
1. Confirm the run permission of ltfsee-[version]-[buildlevel].bin by running the following command:
# ls -l ltfsee-[version]-[buildlevel].bin
2. If it is not already set, set the run permission by running the following command:
# chmod +x ltfsee-[version]-[buildlevel].bin
3. Proceed with the extraction of the binary IBM Spectrum Archive EE rpm files by selecting one of the procedures that are described next.
In the lab setup that was used for this book, we used the interactive console mode method, which is the option most users are likely to use.
Extracting binary rpm files in interactive console mode
This section describes how to extract binary rpm files from the IBM Spectrum Archive EE installation package by using the interactive console mode.
 
Important: The steps in this section extract binary rpm files to your local disk only. To complete the installation process, more steps are required. After you complete the extraction of the binary rpm files, see “Installing, upgrading, or uninstalling IBM Spectrum Archive EE automatically” on page 79 or 4.5, “Quick installation guide for IBM Spectrum Archive EE” on page 88 for more information.
To extract IBM Spectrum Archive EE binary rpm files in interactive console mode, complete the following steps:
1. Run IBM Spectrum Archive EE installation package on the system by running the appropriate command for your environment:
 – If your operating system is running on the command-line interface (CLI), run the following command:
#./ltfsee-[version]-[buildlevel].bin
 – If your operating system is running on the GUI (X Window System), run the following command:
#./ltfsee-[version]-[buildlevel].bin -i console
The messages that are shown in Example 4-1 are displayed.
Example 4-1 Extract binary rpm files in interactive console mode
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
 
Launching installer...
 
Important: You cannot select the installation and link folders with the console installer. They are created in the ~/LTFSEE/ directory, which is the default folder of the installer that extracts the required files.
The installation script ltfsee_install for the command-line installation is found under the ~/LTFSEE/rpm.[version]_[buildlevel] folder; for example, the ~/LTFSEE/rpm.1322_52823/ subfolder.
2. Read the International Program License Agreement. Enter 1 to accept the agreement and press Enter to continue, as shown in Example 4-2.
Example 4-2 IBM Spectrum Archive EE International Program License Agreement
===============================================================================
IBM Spectrum Archive Enterprise Edition (created with InstallAnywhere)
-------------------------------------------------------------------------------
 
Preparing CONSOLE Mode Installation...
 
===============================================================================
 
International License Agreement for Early Release of Programs
Part 1 - General Terms
BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN
"ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO
THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON
BEHALF OF LICENSEE, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL
AUTHORITY TO BIND LICENSEE TO THESE TERMS. IF YOU DO NOT AGREE TO
THESE TERMS,
* DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON,
OR USE THE PROGRAM; AND
* PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND PROOF OF
ENTITLEMENT TO THE PARTY FROM WHOM IT WAS OBTAINED FOR A REFUND OF THE
AMOUNT PAID. IF THE PROGRAM WAS DOWNLOADED, DESTROY ALL COPIES OF THE
PROGRAM.
 
1. Definitions
 
Press Enter to continue viewing the license agreement, or enter "1" to
accept the agreement, "2" to decline it, "3" to print it, or "99" to go back
to the previous screen.:
3. An Installing... message displays while the files are extracted to the ~/LTFSEE/ installation folder, as shown in Example 4-3. You can monitor the progress by watching the text-animated progress bars.
Example 4-3 IBM Spectrum Archive EE installation of the binary files
===============================================================================
Installing...
-------------
 
[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]
When the files are successfully extracted, the text-based installer completes.
 
Important: The following symbolic links are created in your home directory:
•A link to the rpm folder that keeps the extracted rpm files.
•A link to the “Change IBM Linear Tape File System Enterprise Edition Installation” executable file that uninstalls IBM Spectrum Archive EE.
4. Go to the ~/LTFSEE/rpm.[version]_[buildlevel] to find the rpms. If you created symbolic links, click the rpm symbolic link or use the Linux operating system cd ~/rpm command to open the rpm folder.
 
Important: Two files, INSTALL_EE.[version]_[buildlevel] and README_EE.[version]_[buildlevel], are placed in the rpm folder. Folders that correspond to the supported platforms are created in the rpm folder as well. The specific rpm files for the supported platform are in the platform subdirectory.
When you successfully finish, continue to “Installing, upgrading, or uninstalling IBM Spectrum Archive EE automatically” on page 79 to complete the installation. If you prefer to install manually, see 4.5, “Quick installation guide for IBM Spectrum Archive EE” on page 88.
4.3.2 Installing, upgrading, or uninstalling IBM Spectrum Archive EE
This section describes how to install, upgrade, or uninstall binary rpm files for IBM Spectrum Archive EE after extracting them from the installation package, as described in 4.3.1, “Extracting binary rpm files from an installation package” on page 76.
IBM Spectrum Archive EE can be automatically installed, upgraded, or uninstalled.
IBM Spectrum Archive EE nodes communicate by using several TCP/UDP ports. Because some ports are assigned dynamically within a wide range, you must disable any firewall program that runs on these nodes.
 
Important: On Red Hat Enterprise Linux 7 and 8, managing system services are done by using the systemctl command.
To stop the firewall service, run the systemctl stop firewalld command.
To prevent the firewall service from being automatically started at start time, run the systemctl disable firewalld command.
In addition, you can mask the firewalld service to prevent it from being started manually or by another service by running the systemctl mask firewalld command.
During this installation for the IBM Spectrum Archive EE rpm files, there is also an MIB file that is provided if you plan to use SNMP for monitoring of your IBM Spectrum Archive EE setup. SNMP monitoring software usually requires such an MIB file to manage the various SNMP traps sent to it. The IBM Spectrum Archive EE MIB file is in the /opt/ibm/ltfsee/share/IBMSA-MIB.txt directory.
Installing, upgrading, or uninstalling IBM Spectrum Archive EE automatically
This section describes how to install, upgrade, or uninstall binary rpm files for IBM Spectrum Archive EE automatically after extracting them from the installation package. We used this method during our lab setup to write this book and document the examples.
The automated method is based on a utility (a shell script), which is provided by the IBM Spectrum Archive EE installation package. The script is named ltfsee_install and can be found after extracting the binary installation files in the ~/LTFSEE/rpm.[version]_[buildlevel] directory with the IBM Spectrum Archive EE rpm files (such as /root/LTFSEE/rpm.1322_52823/).
ltfsee_install utility
Use the ltfsee_install command-line utility to install rpm packages automatically to the system. You must have root user authority to use this command.
The ltfsee_install <option> command installs the following rpm packages to the system:
•IBM Spectrum Archive LE component
•Integrated customized IBM Spectrum Protect for Space Management with IBM Spectrum Archive EE
•IBM Spectrum Archive Migration Driver
The command includes the following options:
•--install
Install rpm packages. If rpm packages are already installed, the installation is stopped.
•--upgrade
Upgrade installed rpm packages.
•--clean
Uninstall rpm packages.
•--verify
Verify the prerequisite conditions and IBM Spectrum Archive Enterprise Edition package installation only. No installation will be performed.
•--check
Check the prerequisite conditions only. No installation will be performed.
Verify that these conditions are met by logging on to the operating system as a root user and running the following command:
# ./ltfsee_install --check
If the conditions are met, the following message is shown as the last line of output:
The prerequisites checking is completed successfully.
Example 4-4 shows the complete output.
Example 4-4 Output for the ltfsee_install --check command
./ltfsee_install --check
Checking rpm installation and version.
 
The prerequisites checking is completed successfully.
The ltfsee_install file installs or upgrades all required rpm packages on the server node. It can also uninstall those rpm packages from the node if needed.
 
Important: The ltfsee_install command procedures in this topic automatically perform all operations from 4.5, “Quick installation guide for IBM Spectrum Archive EE” on page 88, except for installing optional TIVsm language packages (if they are needed).
Complete the following steps to automatically install, upgrade, or uninstall IBM Spectrum Archive EE by running the ltfsee_install command:
1. Log on to the operating system as a root user.
2. On each node in the cluster, complete the set of tasks for the action you want to take:
a. Installing IBM Spectrum Archive EE on the node:
i. Run the following command:
# ./ltfsee_install --install
Example 4-5 shows you the complete output of the ltfsee_install --install command.
ii. Verify that the command completed successfully. Check for the following success message in the command output:
All rpm packages are installed successfully.
Example 4-5 Output for the ltfsee_install --install command
[root@ltfsServer rpm.1320_52814]# ./ltfsee_install --install
Checking the software prerequisites on ltfsServer.tuc.stglabs.ibm.com.
No error found during the prerequisite check.
Starting RPM installation.
Installing HSM modules.
Created symlink from /etc/systemd/system/multi-user.target.wants/hsm.service to /usr/lib/systemd/system/hsm.service.
Installing EE modules.
Starting HSM.
Completed RPM installation.
Running the post-installation steps.
All rpm packages are installed successfully.
The installed IBM Spectrum Archive EE version: 1.3.2.0_52814.
Complete the configuration by using the /opt/ibm/ltfsee/bin/ltfsee_config command.
** ATTENTION **
For problem determination, it is strongly recommended that you disable log suppression and set up the abrtd daemon to capture the Spectrum Archive core dumps.
Refer to the Troubleshooting section of the IBM Spectrum Archive Enterprise Edition documentation in the IBM Knowledge Center.
iii. Complete the configuration by running the /opt/ibm/ltfsee/bin/ltfsee_config command, as described in 5.2, “Configuring IBM Spectrum Archive EE” on page 105.
b. Upgrading the rpm files to the latest versions:
 
Note: In a multi-node environment, run the ltfsee_install --upgrade --all command on one node to automatically update all nodes in the cluster. Running the ltfsee_install --upgrade command on each node is not recommended because doing so might can cause unexpected failures during a multi-node system upgrade.
i. Run the eeadm cluster stop command.
ii. Run the pidof mmm command on all active control nodes and wait until there are no processes returned.
iii. Run the pidof ltfs command on every EE node and wait until there are no processes returned.
To perform the upgrade process, run the ltfsee_install --upgrade command or the ltfsee_install --upgrade --all command for multi node environment. An example for a single node upgrade is shown in Example 4-6 on page 81.
Example 4-6 Running ltfsee_install --upgrade command
[root@ltfsServer rpm.1320_52814]# ./ltfsee_install --upgrade
The upgrade installation option is selected.
This option upgrades the IBM Spectrum Archive EE software
From: Version 1.3.1.0-xxxxx
To: Version 1.3.2.0-52814
Do you want to continue? [Y/n]: Y
Preparing for the software upgrade.
Checking the software prerequisites on ltfsServer.tuc.stglabs.ibm.com.
No error found during the prerequisite check.
 
**** Upgrading the software on ltfsServer.tuc.stglabs.ibm.com. ****
Uninstalling RPMs.
Removed symlink /etc/systemd/system/multi-user.target.wants/hsm.service.
Starting RPM installation.
Installing HSM modules.
Created symlink from /etc/systemd/system/multi-user.target.wants/hsm.service to /usr/lib/systemd/system/hsm.service.
Installing EE modules.
Starting HSM.
Completed RPM installation.
Running the post-installation steps.
All rpm packages are upgraded successfully on the local node, ltfsServer.tuc.stglabs.ibm.com.
 
The following files were updated during the installation. (The original files were copied to the /opt/ibm/ltfsee/bin directory)
- /etc/rsyslog.d/ibmsa-rsyslog.conf
- /etc/logrotate.d/ibmsa-logrotate
 
** ATTENTION for upgrade **
If you have installed the IBM Spectrum Archive EE dashboard, restart the logstash on all of the IBM Spectrum Archive EE nodes.
** ATTENTION **
For problem determination, it is strongly recommended that you disable log suppression and set up the abrtd daemon to capture the Spectrum Archive core dumps.
Refer to the Troubleshooting section of the IBM Spectrum Archive Enterprise Edition documentation in the IBM Knowledge Center.
iv. Verify that the command completed. Check for the following success message in the command output:
All rpm packages are installed successfully.
c. Uninstalling IBM Spectrum Archive EE from the node:
i. Run the following command:
# ltfsee_install --clean
ii. Verify that the command completed. Check for the following success message in the command output:
Uninstallation is completed.
3. Verify that the installation or uninstallation completed successfully by running the following command:
# ltfsee_install --verify
If the installation (see Example 4-7) was successful, the following message is shown:
Module installation check is completed.
Example 4-7 Successful ltfsee_install --verify command
[root@ltfsServer rpm.1320_52814]# ./ltfsee_install --verify
Checking the software prerequisites on ltfsServer.ltfsServer.tuc.stglabs.ibm.com.
No error found during the prerequisite check.
An IBM Spectrum Archive EE package ltfs-license is installed.
An IBM Spectrum Archive EE package ltfsle-library is installed.
An IBM Spectrum Archive EE package ltfsle-library-plus is installed.
An IBM Spectrum Archive EE package ltfsle is installed.
An IBM Spectrum Archive EE package ltfs-admin-utils is installed.
An IBM Spectrum Archive EE package gskcrypt64 is installed.
An IBM Spectrum Archive EE package gskssl64 is installed.
An IBM Spectrum Archive EE package TIVsm-API64 is installed.
An IBM Spectrum Archive EE package TIVsm-BA is installed.
An IBM Spectrum Archive EE package TIVsm-HSM is installed.
An IBM Spectrum Archive EE package ltfs-mig is installed.
All IBM Spectrum Archive EE packages are installed.
The module installation check completed.
 
4.4 Installing a RESTful server
This section describes how to install the IBM Spectrum Archive EE REST API after extracting the installation package, as described in 4.3.1, “Extracting binary rpm files from an installation package” on page 76 and installing IBM Spectrum Archive EE as described in 4.3.2, “Installing, upgrading, or uninstalling IBM Spectrum Archive EE” on page 78. This section must be followed after IBM Spectrum Archive EE has been installed.
The rest service can be installed on any node within the cluster that has IBM Spectrum Archive EE installed. To start the installation, some software requirements must be met before the rpm can be installed.
The following software applications are required:
•IBM Spectrum Archive EE v1.2.4 or later
•httpd
•mod_ssl
•mod_wsgi
•Python 2.4 or later, but earlier than 3.0
•Flask
Example 4-8 shows how to perform the installation of the required software to run REST.
Example 4-8 Required software for rest installation
[root@ltfseesrv1 ~]# yum install -y httpd mod_ssl mod_wsgi
Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos, subscription-manager
This system is receiving updates from RHN Classic or Red Hat Satellite.
Resolving Dependencies
--> Running transaction check
---> Package httpd.x86_64 0:2.4.6-45.el7 will be installed
--> Processing Dependency: httpd-tools = 2.4.6-45.el7 for package: httpd-2.4.6-45.el7.x86_64
--> Processing Dependency: /etc/mime.types for package: httpd-2.4.6-45.el7.x86_64
---> Package mod_ssl.x86_64 1:2.4.6-45.el7 will be installed
---> Package mod_wsgi.x86_64 0:3.4-12.el7_0 will be installed
--> Running transaction check
---> Package httpd-tools.x86_64 0:2.4.6-45.el7 will be installed
---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed
--> Finished Dependency Resolution
 
Dependencies Resolved
 
=====================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================
Installing:
httpd x86_64 2.4.6-45.el7 rhel-x86_64-server-7 1.2 M
mod_ssl x86_64 1:2.4.6-45.el7 rhel-x86_64-server-7 105 k
mod_wsgi x86_64 3.4-12.el7_0 rhel-x86_64-server-7 76 k
Installing for dependencies:
httpd-tools x86_64 2.4.6-45.el7 rhel-x86_64-server-7 84 k
mailcap noarch 2.1.41-2.el7 rhel-x86_64-server-7 31 k
 
Transaction Summary
=====================================================================================================================
Install 3 Packages (+2 Dependent packages)
 
Total download size: 1.5 M
Installed size: 4.4 M
Downloading packages:
(1/5): httpd-2.4.6-45.el7.x86_64.rpm | 1.2 MB 00:00:00
(2/5): httpd-tools-2.4.6-45.el7.x86_64.rpm | 84 kB 00:00:00
(3/5): mailcap-2.1.41-2.el7.noarch.rpm | 31 kB 00:00:00
(4/5): mod_ssl-2.4.6-45.el7.x86_64.rpm | 105 kB 00:00:00
(5/5): mod_wsgi-3.4-12.el7_0.x86_64.rpm | 76 kB 00:00:00
---------------------------------------------------------------------------------------------------------------------
Total 467 kB/s | 1.5 MB 00:00:03
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Installing : mailcap-2.1.41-2.el7.noarch 1/5
Installing : httpd-tools-2.4.6-45.el7.x86_64 2/5
Installing : httpd-2.4.6-45.el7.x86_64 3/5
Installing : mod_wsgi-3.4-12.el7_0.x86_64 4/5
Installing : 1:mod_ssl-2.4.6-45.el7.x86_64 5/5
Verifying : httpd-tools-2.4.6-45.el7.x86_64 1/5
Verifying : mod_wsgi-3.4-12.el7_0.x86_64 2/5
Verifying : mailcap-2.1.41-2.el7.noarch 3/5
Verifying : 1:mod_ssl-2.4.6-45.el7.x86_64 4/5
Verifying : httpd-2.4.6-45.el7.x86_64 5/5
 
Installed:
httpd.x86_64 0:2.4.6-45.el7 mod_ssl.x86_64 1:2.4.6-45.el7 mod_wsgi.x86_64 0:3.4-12.el7_0
 
Dependency Installed:
httpd-tools.x86_64 0:2.4.6-45.el7 mailcap.noarch 0:2.1.41-2.el7
 
Complete!
If pip is not installed on the designated node (pip is installed by default if the version of Python is 2.7.9 or greater), it can be installed by running the following commands:
curl “https://bootstrap.pypa.io/get-pip.py” -o “get-pip.py”
python get-pip.py
After pip is installed, run the following command to install flask version 0.12.2:
pip install flask==0.12.2
Example 4-9 shows how to install flask.
Example 4-9 Install flask V0.12
[root@ltfseesrv1 ~]# pip install flask==0.12.2
Collecting flask
Downloading Flask-0.12.2-py2.py3-none-any.whl (83kB)
100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 92kB 513kB/s
Collecting click>=2.0 (from flask)
Downloading click-6.7-py2.py3-none-any.whl (71kB)
100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 71kB 1.4MB/s
Collecting Jinja2>=2.4 (from flask)
Downloading Jinja2-2.9.6-py2.py3-none-any.whl (340kB)
100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 348kB 1.0MB/s
Collecting Werkzeug>=0.7 (from flask)
Downloading Werkzeug-0.12.2-py2.py3-none-any.whl (312kB)
100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 317kB 1.3MB/s
Collecting itsdangerous>=0.21 (from flask)
Downloading itsdangerous-0.24.tar.gz (46kB)
100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 51kB 5.0MB/s
Collecting MarkupSafe>=0.23 (from Jinja2>=2.4->flask)
Downloading MarkupSafe-1.0.tar.gz
Building wheels for collected packages: itsdangerous, MarkupSafe
Running setup.py bdist_wheel for itsdangerous ... done
Stored in directory: /root/.cache/pip/wheels/fc/a8/66/24d655233c757e178d45dea2de22a04c6d92766abfb741129a
Running setup.py bdist_wheel for MarkupSafe ... done
Stored in directory: /root/.cache/pip/wheels/88/a7/30/e39a54a87bcbe25308fa3ca64e8ddc75d9b3e5afa21ee32d57
Successfully built itsdangerous MarkupSafe
Installing collected packages: click, MarkupSafe, Jinja2, Werkzeug, itsdangerous, flask
Found existing installation: MarkupSafe 0.11
Uninstalling MarkupSafe-0.11:
Successfully uninstalled MarkupSafe-0.11
Successfully installed Jinja2-2.9.6 MarkupSafe-1.0 Werkzeug-0.12.2 click-6.7 flask-0.12.2 itsdangerous-0.24
After all the required software has been installed, in the same directory that the IBM Spectrum Archive EE was extracted to, there is an RHEL7 directory that contains a file called.ibmsa-rest-[version]-[buildlevel].x86_64.rpm. To install the restful service, run the yum install command on this file, as shown in Example 4-10.
Example 4-10 Installing IBM Spectrum Archive Rest service
[root@ltfseesrv1 RHEL7]# yum install -y ibmsa-rest-1.2.4.0-12441.x86_64.rpm
Loaded plugins: langpacks, product-id, rhnplugin, subscription-manager
This system is receiving updates from RHN Classic or Red Hat Satellite.
Examining ibmsa-rest-1.2.4.0-12441.x86_64.rpm: ibmsa-rest-1.2.4.0-12441.x86_64
Marking ibmsa-rest-1.2.4.0-12441.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package ibmsa-rest.x86_64 0:1.2.4.0-12441 will be installed
--> Finished Dependency Resolution
 
Dependencies Resolved
 
=====================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================
Installing:
ibmsa-rest x86_64 1.2.4.0-12441 /ibmsa-rest-1.2.4.0-12441.x86_64 51 k
 
Transaction Summary
=====================================================================================================================
Install 1 Package
 
Total size: 51 k
Installed size: 51 k
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : ibmsa-rest-1.2.4.0-12441.x86_64 1/1
##############################################################
# ibmsa-rest have been installed successfully.
# Please restart or reload httpd to enable REST server.
##############################################################
Verifying : ibmsa-rest-1.2.4.0-12441.x86_64 1/1
 
Installed:
ibmsa-rest.x86_64 0:1.2.4.0-12441
 
Complete!
At the bottom of a successful installation, it says the installation was successful and that a restart of the httpd service is required to enable the rest server. To restart the service, run the following command:
systemctl restart httpd
 
Note: If REST is already installed on cluster updating IBM Spectrum Archive EE will automatically update the REST interface, however a manual restart of httpd is required after starting IBM Spectrum Archive EE.
When this is all done, to quickly test that the rest service has been successfully installed, run the following command:
curl -i -X GET ‘http://localhost:7100/ibmsa/v1’
Example 4-11 shows using a test curl command to see whether the installation was successful.
Example 4-11 Test curl command
[root@ltfseesrv1 ~]# curl -i -XGET 'http://localhost:7100/ibmsa/v1'
HTTP/1.1 200 OK
Date: Wed, 12 Jul 2017 22:03:00 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5
Content-Length: 83
Content-Type: application/json
 
{"message":"IBM Spectrum Archive REST API server is working.","status_code":"200"}
The default port is on 7100 and the default protocol to use is http. If SSL is required, uncomment SSLEngine, SSLCertificateFile, SSLCertifcateKeyFile and provide the direct path to both the certificate file and the certificate key file in the following file:
/etc/httpd/conf.d/ibmsa-rest-httpd.conf
For an overview of IBM Spectrum Archive EE Rest API and commands, see 6.26, “IBM Spectrum Archive REST API” on page 219.
4.5 Quick installation guide for IBM Spectrum Archive EE
This section summarizes the overall installation process of IBM Spectrum Archive EE:
1. Ensure that all prerequisite software (Linux packages) and HBA driver are installed.
2. Ensure that the IBM Spectrum Scale file system daemon is started by running the following command:
mmstartup -a
3. Extract the binary rpm files from an IBM Spectrum Archive EE installation package by running the following command:
./ltfsee-1.3.2.2_52823.bin
4. Install IBM Spectrum Archive EE automatically by using the ltfsee_install tool. Use --check for preinstallation check, --install for the installation, and --verify for a postinstallation verification, as shown in the following commands:
 – ~/LTFSEE/rpm.[version]_[buildlevel]/ltfsee_install --check
 – ~/LTFSEE/rpm.[version]_[buildlevel]/ltfsee_install --install
 – ~/LTFSEE/rpm.[version]_[buildlevel]/ltfsee_install --verify
4.6 Library replacement
Library replacement has been introduced to give users the ability to upgrade their older tape library to a newer tape library. There are two library replacement scenarios available for users to perform: a complete library replacement, and a pool relocation. Both are disruptive, but the pool relocation offers less down time and the ability to continue running IBM Spectrum Archive while the pool that is going to be relocated is disabled.
The library replacement procedure requires the user to halt their environment to perform, due to the relocation of all tape cartridges and possibly all tape drives to a newer library.
The pool relocation procedure requires a multi-library configuration so that a pool can be relocated from one library to the other. While the pool is being relocated operations are not allowed on that pool however the other pools are still available for operations.
In addition to these new procedures, IBM Spectrum Archive EE now appends a new state for tape cartridges, appendable. This new state is determined by the pool settings and the state of the tape to determine if the tape is candidate for migration. An appendable tape cartridge within a pool allows data to be written to that tape. Those tapes can either be empty, or partially filled with data.
Non-appendable tape cartridges are tapes that do not allow writes to the tape. Non-appendable tape cartridges result from being completely full, erroneous tapes, or tapes within pools that do not match their media-restriction or format type. With the introduction of this new tape state, users have better control over the flow of their data from disk to tape and from tape to tape. Refer to 6.11.5, “Data Migration” on page 180.
 
Note: The following library replacement procedures are supported with IBM Spectrum Archive EE v1.2.6 and above.
4.6.1 Library replacement procedure
This procedure must be used if you are switching or upgrading your current tape library to another tape library and want to continue using the tapes and tape drives and cluster configuration within your IBM Spectrum Archive EE environment. For example, you might be replacing your TS3500 tape library with a new TS4500 tape library.
To do so, complete the following steps:
1. Identify the library name and serial number that you intend to replace, for use in the subsequent steps. Example 4-12 shows how to get a list of libraries and serial numbers by running the ltfsee_config -m LIST_LIBRARIES command.
Example 4-12 ltfsee_config -m LIST_LIBRARIES
[root@server1 ~]# ltfsee_config -m LIST_LIBRARIES
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m LIST_LIBRARIES
LIST_LIBRARIES mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
 
Library Name Serial Number Control Node
lib1 0000013FA0520401 9.11.244.22
lib2 0000013FA052041F 9.11.244.23
2. If the tape drives from the old library will not be used in the new library, remove the tape drives by using the eeadm drive unassign command. Refer to “IBM Spectrum Scale commands” on page 323 for more information about the command.
3. Stop IBM Spectrum Archive EE by executing the eeadm cluster stop command.
4. Replace the physical old tape library with the new tape library.
5. Physically move all of the tape cartridges to the new library.
6. If you are moving the tape drives from the old tape library to the new library, physically remove the tape drives from the old tape library and install them in the new library. The drives need to be attached to the same node that they were attached to before.
7. The REPLACE_LIBRARY command associates the new library’s serial number with the old library’s ID. Example 4-13 shows the output from running the ltfsee_config -m REPLACE_LIBRARY command to associate the new library with the old library serial number.
Example 4-13 ltfsee_config -m REPLACE_LIBRARY
[root@server1 ~]# ltfsee_config -m REPLACE_LIBRARY
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m REPLACE_LIBRARY
REPLACE_LIBRARY mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
** Configuration change for library: lib1
 
The number of logical libraries with the assigned control node: 2
The number of logical libraries available from this node: 1
The number of logical libraries available from this node and with assigned control node: 0
 
** Select the tape library from the following list
and input the corresponding number. Then press Enter.
 
Model Serial Number
1. 03584L32 0000013FA052041B
q. Exit from this Menu
 
Input Number > 1
is going to be set to library lib1.
Do you want to continue (y/n)?
Input > y
 
Restarting HSM daemon on server1
 
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m RESTART_HSM
RESTART_HSM mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
Deactivating failover operations on the node.
Restarting Space Management service...
Stopping the HSM service.
Terminating dsmwatchd.............
Starting the HSM service.
Starting dsmmigfs..................................
Activating failover operations on the node.
 
Restarting HSM daemon on server2
 
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m RESTART_HSM
RESTART_HSM mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
Deactivating failover operations on the node.
Restarting Space Management service...
Stopping the HSM service.
Terminating dsmwatchd.............
Starting the HSM service.
Starting dsmmigfs..................................
Activating failover operations on the node.
 
REPLACE_LIBRARY mode completed .
 
Note: In releases before IBM Spectrum Archive EE version 1.2.6, the serial number of a library was used as the library ID. Beginning with version 1.2.6, the library ID can have a unique value other than the serial number. A UUID is assigned as the library ID in libraries that are configured with version 1.2.6 and subsequent releases.
With the separation of the library ID from the library serial number, IBM Spectrum Archive EE can replace a library by changing the library serial number that is associated with the library ID. The configuration of the cartridges, and pools, and drives in the old library is transferred to the new library.
8. Verify library serial change by running the ltfsee_config -m LIST_LIBRARIES.
9. Start IBM Spectrum Archive EE by using the eeadm cluster start command.
10. If you are using new drives in the new library, configure the drives with the eeadm drive assign command. See “The eeadm <resource type> --help command” on page 316 for more information about the command.
4.6.2 Pool relocation procedure
Use this procedure to logically and physically move a tape pool from one library (the source) to another library (the destination), within an IBM Spectrum Archive EE cluster. During the procedure, the tape pool that is being moved is disabled. However, during most of the procedure, the IBM Spectrum Archive EE system remains online, and other tape pools remain available for operations.
 
Note: Pool relocation will fail if any files are migrated to pools from IBM Spectrum Archive EE v1.1. To determine if any pools have files from v1.1, run the following command:
ltfsee_count_v11_files -p <pool_name> -l <library_name>
 
Pool relocation only works in a multi-library IBM Spectrum Archive EE cluster. Therefore, if you have a single-library environment and want to move a pool, you first need to have a second IBM Spectrum Archive EE node added to the cluster and an identical media type secondary tape library attached.
For the pool replacement procedure the following assumptions are made:
•IBM Spectrum Archive EE is configured as multi-library configuration.
•A pool is selected to move from one library (called the source library) to another library (called the destination library).
•All physical tape cartridges in the selected pool are moved to the destination library manually.
1. Get the pool information that is being relocated by running the eeadm pool list command.
2. Stop IBM Spectrum Archive EE.
3. Prepare the selected pool for relocation with the ltfsee_config -m PREPARE_MOVE_POOL command. Example 4-14 shows the output from running the command on pool1 from library lib1 to library lib2.
Example 4-14 ltfsee_config -m PREPARE_MOVE_POOL
[root@server1 ~]# ltfsee_config -m PREPARE_MOVE_POOL -p pool1 -s lib1 -d lib2
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m PREPARE_MOVE_POOL -p pool1 -s lib1 -d lib2
PREPARE_MOVE_POOL mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
 
Start the mmapplypolicy GPFS command to get a list of migrated files that are in IBM Spectrum Archive V1.1 format.
 
 
Starting IBM Spectrum Archive EE to refresh the index cache of the libraries.
 
Library name: lib2, library serial: 0000013FA052041F, control node (ltfsee_md) IP address: 9.11.244.23.
Running start command - sending request : lib2.
Library name: lib1, library serial: 0000013FA052041B, control node (ltfsee_md) IP address: 9.11.244.22.
Running start command - sending request : lib1.
Running start command - waiting for completion : lib2.
................
Started the IBM Spectrum Archive EE services for library lib2 with good status.
Running start command - waiting for completion : lib1.
 
Started the IBM Spectrum Archive EE services for library lib1 with good status.
 
Stopping IBM Spectrum Archive EE.
 
Library name: lib2, library serial: 0000013FA052041F, control node (ltfsee_md) IP address: 9.11.244.23.
Running stop command - sending request and waiting for the completion.
Library name: lib1, library serial: 0000013FA052041B, control node (ltfsee_md) IP address: 9.11.244.22.
Running stop command - sending request and waiting for the completion...
Stopped the IBM Spectrum Archive EE services for library lib2.
Stopped the IBM Spectrum Archive EE services for library lib1.
 
Checking tapes with a duplicated VOLSER in library lib1 and lib2.
 
 
Copying pool definitions from library lib1 to lib2.
 
 
Saving index cache of the tapes in pool pool1.
 
 
PREPARE_MOVE_POOL mode completed.
 
Note: Pools with the same name appear in the source and destination libraries after this command. (The pool name specified for relocation must not exist in the destination library before this command). The mode attribute of the source pool is set to relocation_source, and the mode attribute of the destination pool is set to relocation_destination.
4. List pools that have been or are in process of being moved, as shown in Example 4-15.
Example 4-15 List relocated pools
[root@server1 ~]# ltfsee_config -m LIST_MOVE_POOLS
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m LIST_MOVE_POOLS
LIST_MOVE_POOLS mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
 
Source pool Destination pool Activated
pool1@lib1 pool1@lib2 no
5. Start IBM Spectrum Archive EE by using the eeadm cluster start command.
 
Note: Jobs related to the tapes in the pool with “source” or “destination” in the Mode attribute will be rejected.
6. Make a list of tapes which belong to the pool for relocation with the eeadm tape list command.
7. Move tapes within the selected pool to the IE slot to remove from the previous library using the eeadm tape move <tape1[tape2 tape3 ...] -L ieslot -p <pool> -l <library> command.
8. Stop IBM Spectrum Archive.
9. Activate the pool for relocation by running the ltfsee_config -m ACTIVATE_MOVE_POOL command. Example 4-16 illustrates activating the relocated pool after all tapes have been physically moved to the new tape library.
Example 4-16 The ltfsee_config -m ACTIVATE_MOVE_POOL command
[root@server1 ~]# ltfsee_config -m ACTIVATE_MOVE_POOL -p pool1 -s lib1 -d lib2
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m ACTIVATE_MOVE_POOL -p pool1 -s lib1 -d lib2
ACTIVATE_MOVE_POOL mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
 
Starting IBM Spectrum Archive EE to refresh the index cache of the libraries.
 
Library name: lib2, library serial: 0000013FA052041F, control node (ltfsee_md) IP address: 9.11.244.23.
Running start command - sending request : lib2.
Library name: lib1, library serial: 0000013FA052041B, control node (ltfsee_md) IP address: 9.11.244.22.
Running start command - sending request : lib1.
Running start command - waiting for completion : lib2.
.................
Started the IBM Spectrum Archive EE services for library lib2 with good status.
Running start command - waiting for completion : lib1.
.......
Started the IBM Spectrum Archive EE services for library lib1 with good status.
 
Stopping IBM Spectrum Archive EE.
 
Library name: lib2, library serial: 0000013FA052041F, control node (ltfsee_md) IP address: 9.11.244.23.
Running stop command - sending request and waiting for the completion.
Library name: lib1, library serial: 0000013FA052041B, control node (ltfsee_md) IP address: 9.11.244.22.
Running stop command - sending request and waiting for the completion.
Stopped the IBM Spectrum Archive EE services for library lib2.
.
Stopped the IBM Spectrum Archive EE services for library lib1.
 
Checking whether all the tapes in pool pool1 are properly moved from library lib1 to lib2.
 
 
Updating the index cache of library lib2.
 
 
ACTIVATE_MOVE_POOL mode completed .
10. Verify that the pool has been activated, as shown in Example 4-17.
Example 4-17 List relocated pools
[root@server1 ~]# ltfsee_config -m LIST_MOVE_POOLS
The EE configuration script is starting: /opt/ibm/ltfsee/bin/ltfsee_config -m LIST_MOVE_POOLS
LIST_MOVE_POOLS mode starts .
 
## 1. Check to see if the cluster is already created ##
The cluster is already created and the configuration file ltfsee_config.filesystem exists.
 
Source pool Destination pool Activated
pool1@lib1 pool1@lib2 yes
11. Start IBM Spectrum Archive EE by using the eeadm cluster start command.
12. Verify that the pool and tapes are valid, as shown in Example 4-18.
Example 4-18 Verify pool and tapes in new tape library
[root@server1 ~]# eeadm pool list
 
Pool Name Usable(TiB) Used(TiB) Available(TiB) Reclaimable% Tapes Type Library Node Group
pool1 2.6 1.3 1.2 1% 4 LTO lib2     G0
pool2 1.3 0.9 0.4 0% 4 LTO lib2     G0
 
[root@server1 ~]# eeadm tape list
 
Tape ID Status State Usable(GiB) Used(GiB) Available(GiB) Reclaimable% Pool Library Location Task ID
D00369L5 ok appendable 1327 835 491 1% pool1 lib2     homeslot -
2MA133L5 ok      appendable             1327       763           564          2% pool1 lib2     homeslot -
2FC181L5 ok appendable 1327 543 783 0% pool1 lib2     homeslot -
2MA139L5 ok      appendable             1327       655           672          
0% pool2 lib2     homeslot -
2MA144L5 ok      appendable             1327       655           672          
0% pool1 lib2     homeslot -
1IA134L5 ok      appendable             1327       655           672          
0% pool2 lib2     homeslot -
1SA180L5 ok      appendable             1327         0          1327          
0% pool2 lib2     homeslot -
1FB922L5 ok      appendable             1327       885           441          
0% pool2 lib2     homeslot -
4.7 Tips when upgrading host operating system
IBM Spectrum Archive EE cluster down time can be decreased on a multi-node environment by actively removing and adding nodes to the cluster.
If upgrading a single node cluster or if the environment does not follow the Validity Checklist, see Upgrading Operating System from RH7.x to RH8.x.
Similar node refresh techniques are described in 3.8, “High-level component upgrade steps” on page 70. This information provides more references when planning or performing host operating system upgrades.
Planning the upgrade
The upgrade must be planned with care because the total performance of IBM Spectrum Archive EE decreases along with the nodes that are removed during this procedure.
Requests to IBM Spectrum Archive EE must not exceed the total computing capabilities of the current state of the cluster. Be sure to consider the expected workload that IBM Spectrum Archive EE needs during the time when the nodes are removed for the operating system upgrade. If available, adding a temporary node to the cluster can help to maintain needed computing capabilities.
Validity checklist
Use this check list to confirm whether the upgrade procedure is fully planned. All requirements must met to perform the upgrade:
o The cluster consists of more than one node per library.
o All nodes in the cluster are upgraded to 1.3.1.2 or later, and have matching release versions.
o The cluster can handle requests as the nodes are removed.
o Each node that is left in the cluster can reach at least one Control Path Drive on a library.
Performing the upgrade
 
Caution: Ensure that IBM Spectrum Scale and IBM Spectrum Protect are upgraded to ensure interoperability.
Complete the following steps to upgrade the host operating system:
1. Ensure that the “Validity checklist” is fully met.
2. Stop the cluster to temporarily remove the nodes that is planned for the operating system upgrade.
3. Remove the nodes from the cluster by using ltfsee_config REMOVE_NODE command (see 5.2.1, “The ltfsee_config utility” on page 105). At least one control node must left in the cluster. After the planned nodes are removed, restart the cluster.
4. Perform the operating system upgrades to the nodes that were rolled out.
5. After the operating system upgrade is finished, stop the cluster temporarily to add the upgraded nodes.
6. Configure the upgraded node back into the cluster by using the ltfsee_config ADD_NODE or ltfsee_config ADD_CTRL_NODE command.
7. Repeat the process with other nodes until all nodes are upgraded
 
Note: These operating system upgrade steps refer only to the upgrade steps of IBM Spectrum Archive EE. The operating system upgrade must be carefully planned to meet all hardware and other software compatibility requirements. For operating system update assistance, contact IBM.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.116.37.62