4 Installing Oracle HSM and QFS Software

Oracle HSM uses the Image Packaging System (IPS) that became standard with Oracle Solaris 11. IPS is a network-centric package management system that streamlines and coordinates installation, upgrade, and removal of software packages. It greatly simplifies patch management and eases deployment into production environments.

Using the Solaris Package Manager graphical desktop application or IPS terminal commands, administrators access an Oracle Solaris software repository and locate, download, and install the required software packages, while IPS automatically handles dependency checking and package validation. IPS makes changes to a snapshot of the system so that new software can be deployed non-disruptively, during a maintenance window. So changes can be rolled back, if necessary. Installations and updates can thus be applied safely to running, production systems.

To install the Oracle HSM software, carry out the following tasks:

Obtaining Software
Installing Solaris Cluster Software (High-Availability Configurations Only)
Upgrading Shared Oracle HSM File Systems (if applicable)
Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts

The chapter concludes with brief notes on Uninstalling Oracle HSM Software.

Obtaining Software

This section outlines the process for obtaining required installation software and software updates. See the following sections:

Check Installation Requirements
Download Software Installation Packages.

Check Installation Requirements

For the latest information on installation requirements, including the supported versions of the Oracle Solaris and Linux operating systems, Oracle Cluster software, and other required or supported software packages, consult the Oracle HSM release notes, Oracle support services at support.oracle.com, and the Oracle HSM wiki pages at wikis.oracle.com/display/hsmqfs/Home.

Download Software Installation Packages

Download the installation packages for Oracle software products from the Oracle Software Delivery Cloud. The basic procedure is similar for all Oracle products.

To download Oracle HSM Release 6.0 packages, proceed as follows:

Open edelivery.oracle.com in a web browser window.
Register, if you have not already used the site.
Sign in using your registration credentials.
Check the checkbox to acknowledge the applicable software license.
Check the checkbox to agree to the export restrictions that apply to the software.
On the Media Pack Search page, select Oracle StorageTek Products from the list in the Select a Product Pack control.
From the Platform list, select Oracle Solaris on the platform architecture that will host the Oracle HSM software.
Press the Go button.
When the results list appears, click the radio button that corresponds to the Oracle Hierarchical Storage Manager media pack and press Continue.
When the Oracle Hierarchical Storage Manager and StorageTek QFS Software Media Pack for Oracle Solaris page appears, press the Readme button and read the download instructions.
While still on the Oracle Hierarchical Storage Manager and StorageTek QFS Software Media Pack for Oracle Solaris page, press the View Digest button and save the digest values.

Digests are checksums created by a cryptographic hash function. By comparing the published digest with the digest locally computed from a downloaded file, you can insure that the downloaded file is complete and intact. For instructions on calculating checksums from a file, see the Solaris dgst and md5 man pages.
While still on the Oracle Hierarchical Storage Manager and StorageTek QFS Software Media Pack for Oracle Solaris page, press the Download button that corresponds to the product that you have licensed.

The list includes separate entries for Oracle Hierarchical Storage Manager and StorageTek QFS Software. The Oracle Hierarchical Storage Manager media pack includes both the archiving and the file-system software. The Oracle StorageTek QFS Software media pack contains only the file-system software.
When prompted, save the ZIP archive to a local directory, as described on the Readme page.

The chosen directory should be accessible from all Oracle HSM hosts via the local network. For the examples in this chapter, we download the file to the /hsmqfs directory on a network file server named sw_install.
If you cannot download the required files after several tries, please contact Software Delivery Customer Service at edelivery_ww@oracle.com for assistance.

Once you have downloaded the ZIP file, unzip it in the local directory.

In the example, we unzip the Oracle Hierarchical Storage Manager and StorageTek QFS Software file Q12345-01.zip in the /hsmqfs subdirectory and then list the contents:

[sw_install]root@solaris:~# cd /hsmqfs
[sw_install]root@solaris:~# unzip Q12345-01.zip
[sw_install]root@solaris:~# ls Q12345-01/
./       COPYRIGHT.txt       linux.iso             README.txt
../      iso.md5             Oracle-HSM_6.0/
[sw_install]root@solaris:~# ls Oracle-HSM_6.0/
total 42
./        COPYRIGHT.txt      linux1/       solaris_sparc/../       README.txt         linux2/       solaris_x64/

If you are preparing a high-availability file-system, got to "Installing Solaris Cluster Software (High-Availability Configurations Only)" below.
If you are upgrading a multi-host, shared file system, go to "Upgrading Shared Oracle HSM File Systems" below.
Otherwise, go directly to "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".

Installing Solaris Cluster Software (High-Availability Configurations Only)

If you are preparing a high-availability Oracle HSM configuration, proceed as follow:

On each host, install the Oracle Solaris Cluster and SUNW.HAStoragePlus data service software, as described in the installation and data-service administration documents in the online Information Library for the Solaris Cluster software.
Then go to "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".

Upgrading Shared Oracle HSM File Systems

If you are upgrading the software for a shared file-system that needs to remain available during the upgrade process, consider a rolling upgrade. When one or more potential metadata servers are configured, in addition to the active server, you can update an inactive server, activate the updated server, and then configure and re-activate the primary server before upgrading remaining potential metadata servers and clients. This rolling upgrade process keeps an active Oracle HSM metadata server available at all times, so that file-system data remains accessible to clients.

To perform a rolling upgrade, carry out the following tasks:

Upgrade Any Significantly Older Releases of Oracle HSM
Carry Out the Rolling Upgrade

Upgrade Any Significantly Older Releases of Oracle HSM

At any given time, the Oracle HSM software on the metadata server and clients of a shared file system must be, at most, one release apart. If your shared file-system configuration includes hosts that are running Oracle HSM (or SAM-QFS) software that is more than one release behind the targeted upgrade release, you cannot upgrade to the desired release until you carry out corrective action.

Proceed as follows:

If any client hosts are not running the same release of the Oracle HSM (or SAM-QFS) software as the metadata server, upgrade them to the release used on the server before proceeding.
If the Oracle HSM (or SAM-QFS) software on the active metadata server is more than one release behind the targeted upgrade release and if the file system needs to remain mounted during the upgrade, repeatedly Carry Out the Rolling Upgrade, one release level at a time, until all hosts are fully up to date.
If the Oracle HSM (or SAM-QFS) software on the active metadata server is more than one release behind the targeted upgrade release and if the file system does not need to remain mounted during the upgrade, do not attempt a rolling upgrade. Stop the archiving and staging processes, unmount the file system, and upgrade each host individually, as described in "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".

Carry Out the Rolling Upgrade

Make sure that you Upgrade Any Significantly Older Releases of Oracle HSM before continuing!

If any host is more than one release behind the targeted upgrade release when you attempt a rolling upgrade, the upgrade will fail, at best leaving the file systems in an inconsistent state.
Log in to the currently active (first) metadata server as root. Then log in to the currently potential (second) metadata server, also as root.

In the example, we log in to the active metadata server, first-mds. Then, in a second terminal window, we use secure shell (ssh) to log in to the inactive, potential metadata server, second-mds:
```
[first-mds]root@solaris:~# 

[first-mds]root@solaris:~# ssh root@second-mds
Password:
[second-mds]root@solaris:~# 
```
Upgrade the currently inactive, second metadata server. Install the updated Oracle HSM software using the procedures in "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".
Once the upgrade steps are complete, prepare to activate the second server. If the first, active metadata server mounts an Oracle HSM or SAM-QFS archiving file system, stop any new archiving and staging activity, idle media drives, and wait for current jobs to finish. Then stop the library-control daemon.

For full description of how to stop archiving activity, see the Oracle Hierarchical Storage Manager and StorageTek QFS Software Maintenance and Administration Guide.
```
[first-mds]root@solaris:~# samcmd aridle
[first-mds]root@solaris:~# samcmd stidle
[first-mds]root@solaris:~# samcmd 901 idle
...
[first-mds]root@solaris:~# samcmd a
 ...
Waiting for :arrun
[first-mds]root@solaris:~# samcmd r
...
ty   eq status      act  use  state     vsn
li  801  ---------p    0   0%  off
                empty
...
[first-mds]root@solaris:~# samd stop
[first-mds]root@solaris:~# 
```
On the second metadata server, load the Oracle HSM configuration files and start Oracle HSM processes. Use the command samd config.
```
[second-mds]root@solaris:~# samd config
[second-mds]root@solaris:~# 
```

On the second metadata server, mount the Oracle HSM file system.

[second-mds]root@solaris:~# mount sharefs1
[second-mds]root@solaris:~#

Activate the newly updated second metadata server. From the second metadata server, issue the command samsharefs -s server file-system, where server is the hostname of the newly updated metadata server and file-system is the name of the Oracle HSM shared file system.

In the example, the potential metadata server is second-mds and the file system name is sharefs1:
```
[second-mds]root@solaris:~# samsharefs -s second-mds sharefs1
[second-mds]root@solaris:~# 
```
Upgrade the now-inactive first metadata server. Install the updated Oracle HSM software using the procedures in "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".
Once the upgrade steps are complete, prepare to re-activate the first metadata server. If the currently active second metadata server mounts an Oracle HSM archiving file system, stop any new archiving and staging activity, idle media drives, and wait for current jobs to finish. Then stop the library-control daemon.
```
[second-mds]root@solaris:~# samcmd aridle
[second-mds]root@solaris:~# samcmd stidle 
...
[second-mds]root@solaris:~# samd stop
[second-mds]root@solaris:~# 
```
On the first metadata server, load the Oracle HSM configuration files and start Oracle HSM processes. Use the command samd config.
```
[first-mds]root@solaris:~# samd config
[first-mds]root@solaris:~# 
```

On the first metadata server, mount the Oracle HSM file system.

[first-mds]root@solaris:~# mount sharefs1
[first-mds]root@solaris:~#

Re-activate the first metadata server. From the first metadata server, issue the command samsharefs -s server file-system, where server is the hostname of the potential metadata server and file-system is the name of the Oracle HSM shared file system.

In the example, the potential metadata server is first-mds and the file system name is sharefs1:
```
[first-mds]root@solaris:~# samsharefs -s first-mds sharefs1
[first-mds]root@solaris:~# 
```
Update the remaining clients. Install the updated Oracle HSM software using the procedures in "Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts".
Stop here. The upgrade is complete.

Installing, Upgrading, or Downgrading Oracle HSM Software on Hosts

To install, upgrade, or downgrade Oracle HSM software on an individual host, carry out the following tasks:

Install, Upgrade, or Downgrade Oracle HSM Software on Oracle Solaris Hosts.
Install or Update Oracle HSM Client Software on Linux Hosts (if any).

Install, Upgrade, or Downgrade Oracle HSM Software on Oracle Solaris Hosts

To install, upgrade, or downgrade Oracle HSM packages on a Solaris host, start by carrying out the following tasks:

Prepare the Host for Software Changes.
Locate the Packages for Your Host Architecture.

Then carry out the installation task that best fits your situation:

If you are installing new software and the host operating system is Solaris 11 or later, Install the Software Using the Image Packaging System (IPS) command pkg install.
If you are upgrading or downgrading software that was installed using the IPS command pkg install, Upgrade or Downgrade the Software Using the Image Packaging System (IPS) command pkg update.
If you are installing new software on a Solaris 10 host, Install the Software Using SVR4 pkgrm and pkgadd Commands.
If you are upgrading software that was installed using the SVR4 command pkgadd, Upgrade or Downgrade the Software Using SVR4 pkgrm and pkgadd Commands.

Prepare the Host for Software Changes

If Oracle HSM software is not currently installed on the host system, go to "Locate the Packages for Your Host Architecture".
Otherwise, log in to the Oracle HSM server as root.
```
[samqfs1host]root@solaris:~# 
```
If Oracle HSM software is currently installed on the host system, idle all archiving processes. Use the command samcmd aridle.

This command will allow current archiving and staging to complete, but will not start any new jobs:
```
[samqfs1host]root@solaris:~# samcmd aridle
[samqfs1host]root@solaris:~# 
```
Idle all staging processes. Use the command samcmd stidle.

This command will allow current archiving and staging to complete, but will not start any new jobs:
```
[samqfs1host]root@solaris:~# samcmd stidle
[samqfs1host]root@solaris:~# 
```
Wait for active archiving jobs to complete. Check on the status of the archiving processes using the command samcmd a.

When archiving processes are Waiting for :arrun, the archiving process is idle:
```
[samqfs1host]root@solaris:~# samcmd a
Archiver status samcmd     6.0 10:20:34 Feb 20 2015
samcmd on samqfs1host
sam-archiverd:  Waiting for :arrun
sam-arfind: ...
Waiting for :arrun
```

Wait for active staging jobs to complete. Check on the status of the staging processes using the command samcmd u.

When staging processes are Waiting for :strun, the staging process is idle:

[samqfs1host]root@solaris:~# samcmd u
Staging queue samcmd      6.0  10:20:34 Feb 20 2015
samcmd on solaris.demo.lan
Staging queue by media type: all
sam-stagerd:  Waiting for :strun
[samqfs1host]root@solaris:~#

Idle all removable media drives before proceeding further. For each drive, use the command samcmd equipment-number idle, where equipment-number is the equipment ordinal number assigned to the drive in the /etc/opt/SUNWsamfs/mcf file.

This command will allow current archiving and staging jobs to complete before turning drives off, but will not start any new work. In the example, we idle four drives, with ordinal numbers 801, 802, 803, and 804:
```
[samqfs1host]root@solaris:~# samcmd 801 idle
[samqfs1host]root@solaris:~# samcmd 802 idle
[samqfs1host]root@solaris:~# samcmd 803 idle
[samqfs1host]root@solaris:~# samcmd 804 idle
[samqfs1host]root@solaris:~# 
```

Wait for running jobs to complete.

We can check on the status of the drives using the command samcmd r. When all drives are notrdy and empty, we are ready to proceed.

[samqfs1host]root@solaris:~# samcmd r
Removable media samcmd     6.0 10:37:09 Feb 20 2014
samcmd on samqfs1host
ty   eq   status      act  use  state  vsn
li  801   ---------p    0   0%  notrdy
          empty
li  802    ---------p    0   0%  notrdy
          empty
li  803   ---------p    0   0%  notrdy
          empty
li  804   ---------p    0   0%  notrdy
          empty
[samqfs1host]root@solaris:~#

When the archiver and stager processes are idle and the tape drives are all notrdy, stop the library-control daemon. Use the command samd stop.
```
[samqfs1host]root@solaris:~# samd stop
[samqfs1host]root@solaris:~# 
```
If file systems are shared through NFS or SMB/CIFS, unshare the file systems. On the metadata server, use the command unshare mount-point, where mount-point is the mount point directory of the Oracle HSM file system.

In the first example, we stop NFS sharing of the Oracle HSM standalone file system samqfs1.
```
[samqfs1host]root@solaris:~# unshare /hsmqfs1
[samqfs1host]root@solaris:~# 
```
In the second example, we stop NFS sharing of the Oracle HSM shared file system samqfs2:
```
[samqfs2server]root@solaris:~# unshare /hsmqfs2
[samqfs2server]root@solaris:~# 
```

Unmount all Oracle HSM file systems.

In the first example, we unmount the unshared, standalone file system samqfs1:

[samqfs1host]root@solaris:~# umount samqfs1

In the second example, we unmount the shared file system samqfs1, first from the clients and then from the server, allowing 60 seconds for clients to unmount.

[samqfs2server]root@solaris:~# ssh root@samqfs2client1
Password: 
[samqfs2client1]root@solaris:~# umount /hsmqfs2
[samqfs2client1]root@solaris:~# exit
[samqfs2server]root@solaris:~# 

[samqfs2server]root@solaris:~# ssh root@samqfs2client1
Password: 
[samqfs2client2]root@solaris:~# umount /hsmqfs2
[samqfs2client2]root@solaris:~# exit
[samqfs2server]root@solaris:~# umount -o await_clients=60 /sharefs2

If you currently have SAM-QFS 5.3 or earlier installed, uninstall all packages. Use the command pkgrm SUNWsamfsu SUNWsamfsr (pkgrm SUNWqfsu SUNWqfsr if only QFS is installed).

Remove the packages in the order specified, starting with SUNWsamfsu and ending with SUNWsamfsr. In the example, we pipe the reply yes into the command so that all questions are automatically answered:
```
[host1]root@solaris:~# yes | pkgrm SUNWsamfsu SUNWsamfsr
```
Next, Locate the Packages for Your Host Architecture.

Locate the Packages for Your Host Architecture

Log in to the Oracle HSM host as root.
```
root@solaris:~# 
```
Change to the directory where the Oracle HSM download file was unpacked, and locate the subdirectory where packages for the desired version are stored.

The initially released packages are stored in the Oracle_HSM_release-number (or STK_QFS_release-number) subdirectory, where release-number is a major and a minor release number, joined by a dot: Oracle_HSM_6.0+/. Patch releases (if any) are located in a similar subdirectory with an additional -patch-number suffix, where patch-number is a two-digit patch sequence number: Oracle_HSM_6.0-01/.

In the example we change to the download directory for the initial release of the software, Oracle_HSM_6.0/ and list the contents:
```
root@solaris:~# cd /net/sw-install/hsmqfs/Oracle_HSM_6.0/
root@solaris:~# ls -1
./
../
linux1/
linux2/
Notices/
README.txt
solaris_sparc/
solaris_x64/
```
Change to the subdirectory that corresponds to your host architecture, either solaris_sparc/ or solaris_x64/, and list the contents.

In the example, we change to the solaris_sparc/ subdirectory:
```
root@solaris:~# cd solaris_sparc/
root@solaris:~# ls -1
./
../
S10/
S11/
S11_ips/
fsmgr_5.4.zip
fsmgr_setup*
```
When Solaris 11 or later is installed on the host, you can install the software using the Image Packaging System. To use IPS, change to the subdirectory S11_ips/ and Install the Software Using the Image Packaging System (IPS) or Upgrade or Downgrade the Software Using the Image Packaging System (IPS).
```
root@solaris:~# cd S11_ips/
```
Alternatively, when Solaris 11 or later is installed on the host, you can also install the software using the pkgadd method. In this case, change to the subdirectory S11/ and either Upgrade or Downgrade the Software Using SVR4 pkgrm and pkgadd Commands.
```
root@solaris:~# cd S11_ips/
```
When Solaris 10 is installed on the host, change to the subdirectory S10/ and Upgrade or Downgrade the Software Using SVR4 pkgrm and pkgadd Commands.
```
root@solaris:~# cd S10/
```

Install the Software Using the Image Packaging System (IPS)

In general, you should use Image Packaging System (IPS) commands to install, upgrade, or downgrade Oracle HSM software on hosts running Solaris 11 or later. For each host, including metadata servers and shared file-system clients (if any), proceed as follows:

If you have not already done so, Locate the Packages for Your Host Architecture.
Change to the repository directory for the Solaris 11 IPS packages, repo.samqfs/.

In the example, we change to repository directory for Oracle HSM 6.0, Oracle_HSM_6.0/solaris_sparc/S11_ips/repo.samqfs:
```
root@solaris:~# cd repo.samqfs/
root@solaris:~# 
```

To install both the Oracle Hierarchical Storage Manager and StorageTek QFS Software packages, use the command pkg install -g . --accept SUNWsamfs SUNWsamqassy, where . is the current directory (the repository) and SUNWsamfs and SUNWsamqassy are the Oracle HSM Image Packaging System package names.

root@solaris:~# pkg install -g . --accept SUNWsamfs SUNWsamqassy
Creating plan
...
* The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */
           Packages to install:   2
       Create boot environment:  No
Create backup boot environment: Yes
DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                2/2       520/520    21.4/21.4    0B/s
PHASE                                          ITEMS
Installing new actions                       693/693
Updating package state database                 Done 
Updating image state                            Done 
Creating fast lookup database                   Done

To install only the QFS Software packages, use the command pkg install -g . --accept SUNWqfs SUNWsamqassy, where . is the current directory (the repository) and SUNWqfs and SUNWsamqassy are the Oracle HSM Image Packaging System package names.

root@solaris:~# pkg install -g . --accept SUNWqfs SUNWsamqassy
Creating plan
...
* The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */
           Packages to install:   2
       Create boot environment:  No
Create backup boot environment: Yes
DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                2/2       520/520    21.4/21.4    0B/s
PHASE                                          ITEMS
Installing new actions                       693/693
Updating package state database                 Done 
Updating image state                            Done 
Creating fast lookup database                   Done

When the packages finish installing, run the post-installation script, SAM-QFS-post-install. It is located in the util/ subdirectory of the Oracle HSM installation directory (either /opt/SUNWsamfs/ or /opt/SUNWqfs/).

In the example, we run /opt/SUNWsamfs/util/SAM-QFS-post-install:
```
root@solaris:~# /opt/SUNWsamfs/util/SAM-QFS-post-install
- The administrator commands will be executable by root only (group bin).
If this is the desired value, enter "y".  If you want to change
the specified value enter "c".
...
root@solaris:~# 
```
Add the Oracle HSM directories /opt/SUNWsamfs/bin and /opt/SUNWsamfs/sbin (or /opt/SUNWqfs/bin and /opt/SUNWqfs/sbin) to the system PATH variable, if it is not already in path.
Add the Oracle HSM directory /opt/SUNWsamfs/man (or /opt/SUNWqfs/man) to the system MANPATH variable, if it is not already in the man path.
If the planned Oracle HSM configuration includes additional Solaris hosts, repeat this procedure from the beginning until the software is installed on all hosts.
If the planned Oracle HSM configuration includes Linux hosts as shared file-system clients, go to Install or Update Oracle HSM Client Software on Linux Hosts.
Otherwise, go to "Using the samsetup Configuration Wizard" or "Configuring the Basic File System".

Upgrade or Downgrade the Software Using the Image Packaging System (IPS)

Use Image Packaging System (IPS) commands to upgrade or downgrade Oracle HSM software that was originally installed using IPS.

For each host, including metadata servers and shared file-system clients (if any), proceed as follows:

If you have not yet done so, Locate the Packages for Your Host Architecture.
To upgrade the Oracle Hierarchical Storage Manager and StorageTek QFS Software packages to the latest versions in the repository, use the command pkg update -g . --accept SUNWsamfs SUNWsamqassy, where . is the current directory (the repository) and SUNWsamfs and SUNWsamqassy are the Oracle HSM Image Packaging System package names.
```
root@solaris:~# pkg update -g . --accept SUNWsamfs SUNWsamqassy
...
root@solaris:~# 
```
To upgrade only the QFS Software packages to the latest versions in the repository, use the command pkg update -g . --accept SUNWqfs SUNWsamqassy, where . is the current directory (the repository) and SUNWqfs and SUNWsamqassy are the Oracle HSM Image Packaging System package names.
```
[host1]root@solaris:~# pkg update -g . --accept SUNWqfs SUNWsamqassy
...
root@solaris:~# 
```

To downgrade the Oracle HSM packages or to upgrade them to a specified version, first obtain the fault managed resource identifier (FMRI) for the desired packages. Use the command pkg info -r -g . package-name, where . specifies the current directory and package-name is the name of the Oracle HSM package.

In the example, Oracle HSM version 6.0.0 is installed on the host:

root@solaris:~# samcmd l  
Usage information samcmd      6.0.0 14:06:20 Feb  20 2015 ...
root@solaris:~#

We need to downgrade to SAM-QFS 5.4.6. So we run the pkg info commands for SUNWsamfs and SUNWsamqassy in the IPS repository for version 5.4.6, Oracle_HSM_6.0/solaris_sparc/S11_ips/repo.samqfs:

root@solaris:~# pwd
/net/Oracle_HSM_6.0/solaris_sparc/S11_ips/repo.samqfs
root@solaris:~# pkg info -r -g . SUNWsamfs
          Name: SUNWsamfs
       Summary: StorageTek SAM and StorageTek SAM-QFS software
   Description: StorageTek Storage and Archive Manager File System
      Category: System/File System
         State: Not installed
     Publisher: samqfs
       Version: 5.4
 Build Release: 5.11
        Branch: None
Packaging Date: Tue Jul 08 22:56:56 2014
          Size: 88.64 MB
          FMRI: pkg://hsmqfs/SUNWsamfs@5.4,5.11:20140708T225656Z

root@solaris:~# pkg info -r -g . SUNWsamqassy
          Name: SUNWsamqassy
       Summary: StorageTek QFS and Storage Archive Manager SAM-QFS IPS assembly services
   Description: SAM-QFS IPS Assembly Services
      Category: System/File System
         State: Installed
     Publisher: samqfs
       Version: 5.4
 Build Release: 5.11
        Branch: None
Packaging Date: Fri Sep 26 17:21:35 2014
          Size: 15.15 kB
          FMRI: pkg://hsmqfs/SUNWsamqassy@5.4,5.11:20140926T172135Z
root@solaris:~#

Then, to downgrade the Oracle HSM packages or to upgrade them to a specified version, run the command pkg update -g . fmri, where . specifies the current directory and fmri specifies the fault managed resource identifier of the desired software version.

In the example, we specify the FMRIs of the 5.4.6 versions of the SUNWsamfs and SUNWsamqassy packages:

root@solaris:~# pkg update -g . SUNWsamfs@5.4,5.11:20140708T225656Z 
           Packages to update:   1
       Create boot environment:  No
Create backup boot environment: Yes
DOWNLOAD                                PKGS         FILES    XFER (MB)  
 SPEEDCompleted                               1/1        160/160    19.2/19.2  3.4M/s
PHASE                                          ITEMS
Updating modified actions                    172/172
Updating package state database                 Done
Updating package cache                           1/1
Updating image state                            Done
Creating fast lookup database                   Done
Updating package cache                           3/3
root@solaris:~# pkg update -g . SUNWsamqassy@5.4,5.11:20140926T172135Z 
...
root@solaris:~#

If the planned Oracle HSM configuration includes additional Solaris hosts, repeat this procedure from the beginning until the software has been updated or downgraded on all hosts.
If the planned Oracle HSM configuration includes Linux hosts as shared file-system clients, go to Install or Update Oracle HSM Client Software on Linux Hosts.

Install the Software Using SVR4 `pkgrm` and `pkgadd` Commands

Use SVR4 package commands when you are installing Oracle HSM software on hosts that run Solaris 10 and when you are upgrading software that was originally installed using SVR4 commands.

For each Oracle HSM Solaris host, including metadata servers and shared file-system clients (if any), proceed as follows:

If you have not already done so, Locate the Packages for Your Host Architecture.
To install both the Oracle Hierarchical Storage Manager and StorageTek QFS Software packages, use the command pkgadd -d . SUNWsamfsr SUNWsamfsu and accept all defaults.

Note that you must install the SUNWsamfsr package before installing the SUNWsamfsu package. In the example, we make sure that we are in the directory for our operating system, Oracle_HSM_6.0/solaris_sparc/S10. Then we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# pwd 
/net/Oracle_HSM_6.0/solaris_sparc/s10
root@solaris:~# yes | pkgadd -d . SUNWsamfsr SUNWsamfsu
```
To install only the QFS Software packages, use the command pkgadd -d . SUNWqfsr SUNWqfsu and accept all defaults.

Note that you must install the SUNWqfsr package before installing the SUNWqfsu package. In the example, we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# yes | pkgadd -d . SUNWqfsr SUNWqfsu
```
If the planned Oracle HSM configuration includes Linux hosts as shared file-system clients, go to Install or Update Oracle HSM Client Software on Linux Hosts.
Otherwise, go to Chapter 5, "Using the samsetup Configuration Wizard" or Chapter 6, "Configuring the Basic File System".

Upgrade or Downgrade the Software Using SVR4 `pkgrm` and `pkgadd` Commands

Use SVR4 package commands when you are upgrading or downgrading Oracle HSM software on hosts that run Solaris 10 and when you are upgrading or downgrading software that was originally installed using SVR4 commands.

For each Oracle HSM Solaris host, including metadata servers and shared file-system clients (if any), proceed as follows:

If you are downgrading the Oracle HSM software to SAM-QFS 5.3, start by restoring configuration files to the locations specified by the older software. Use the command /opt/SUNWsamfs/sbin/backto 5.3.

The backto command restores files to their previous locations and formats. See the backto man page for more information.

In the example, we convert Oracle HSM 6.0 configuration files for use with Oracle HSM 5.3:
```
root@solaris:~# /opt/SUNWsamfs/sbin/backto 5.3 ...
root@solaris:~# 
```
Uninstall all Oracle HSM packages that are currently installed. Use the command pkgrm SUNWsamfsu SUNWsamfsr (pkgrm SUNWqfsu SUNWqfsr if only QFS is installed).

Remove the packages in the order specified, starting with SUNWsamfsu and ending with SUNWsamfsr. In the example, we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# yes | pkgrm SUNWsamfsu SUNWsamfsr
```
If you have not already done so, Locate the Packages for Your Host Architecture.
To install both the Oracle Hierarchical Storage Manager and StorageTek QFS Software packages, use the command pkgadd -d . SUNWsamfsr SUNWsamfsu and accept all defaults.

Note that you must install the SUNWsamfsr package before installing the SUNWsamfsu package. In the example, we make sure that we are in the correct directory for our operating system, Oracle_HSM_6.0/solaris_sparc/S10. Then we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# pwd 
/net/Oracle_HSM_6.0/solaris_sparc/s10
root@solaris:~# yes | pkgadd -d . SUNWsamfsr SUNWsamfsu
```
To install only the QFS Software packages, use the command pkgadd -d . SUNWqfsr SUNWqfsu and accept all defaults.

Note that you must install the SUNWqfsr package before installing the SUNWqfsu package. In the example, we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# pwd 
/net/Oracle_HSM_6.0/solaris_sparc/s10
root@solaris:~# yes | pkgadd -d . SUNWqfsr SUNWqfsu
```
If the planned Oracle HSM configuration includes Linux hosts as shared file-system clients, go to Install or Update Oracle HSM Client Software on Linux Hosts.
Otherwise, go to Chapter 5, "Using the samsetup Configuration Wizard" or Chapter 6, "Configuring the Basic File System".

Install or Update Oracle HSM Client Software on Linux Hosts

For each Linux client of a Oracle HSM shared file system, proceed as follows:

Log in to the Linux client as root.
```
[root@linux ~]# 
```
Unmount all mounted Oracle HSM file systems.
Uninstall old Oracle HSM packages. Run the script /var/opt/SUNWsamfs/Uninstall:
```
[root@linux ~]# /var/opt/SUNWsamfs/Uninstall
```
Locate the Linux client ISO image. The ISO image is in the directory where you downloaded the Oracle HSM installation software (see "Obtaining Software").

In the example, we use ssh to login to the repository host sw-install (IP address 192.168.0.2). We locate the software in the directory /hsmqfs:
```
[root@linux ~]# ssh root@sw-install
Password:
[sw_install]root@solaris:~# ls -1 /hsmqfs
./       COPYRIGHT.txt       linux.iso             README.txt
../      iso.md5             Oracle-HSM_6.0/
```
On the Linux host, create a temporary directory.

In the example, we create the directory /hsmtemp:
```
[root@linux ~]# mkdir /hsmtemp
[root@linux ~]# 
```
Make the linux.iso image available to the Linux host. NFS mount the remote directory that holds the image on the temporary directory that you just created. Use the command mount -t nfs repository-host-IP:hsm-repository-dir temp-dir, where:
- -t nfs identifies the type of file system being mounted.
- repository-host-IP is the IP address of the server that hosts your installation software.
- hsm-repository-dir is the directory that holds the Oracle HSM installation software.
- temp-dir is the temporary directory that you created on the Linux host.
In the example, we NFS mount directory /hsmqfs of host sw-install (192.168.0.2) on mount-point directory /hsmtemp:
```
[root@linux ~]# mount -t nfs 192.168.0.2:/hsmqfs /hsmtemp
[root@linux ~]# 
```
Mount the linux.iso image on the Linux host. Use the command mount -o ro,loop -t iso9660 temp-dir/linux.iso /mnt, where:
- -o specifies a list of mount options.
- ro mounts the image read-only.
- loop mounts the image as a loop device.
- -t iso9660 identifies the type of file system being mounted.
- temp-dir is the temporary directory where the remote image repository directory is mounted.
- /mnt is the standard, temporary mount point directory on Linux systems.
In the example, the ISO image is in /hsmtemp:
```
[root@linux ~]# mount -o ro,loop -t iso9660 /hsmtemp/linux.iso /mnt
[root@linux ~]# 
```
Run the installer. Use the command /mnt/linux1/Install.
```
[root@linux ~]# /mnt/linux1/Install
```
If the installation program does not recognize the installed version of the Linux kernel, it will prompt you to create a custom kernel. Enter yes.
```
[root@linux ~]# ./Install
...
A direct match for your kernel wasn't found. Attempt creating a custom rpm for your kernel (yes/no)? yes
```
Many variations of the Linux kernel exist. The Oracle HSM installation program compiles custom kernel modules so that it can support the largest possible number of variations.
Follow the on-screen instructions.

If you are installing a SuSE Linux client, configure the system to recognize the man pages. Open the /etc/manpath.config file in a text editor, and add 1m to the value of the SECTION parameter.

In the example, we use the vi editor:

[root@linux ~]# vi /etc/manpath.config
...
#---------------------------------------------------------
# Section names. Manual sections will be searched in the order listed here;
# the default is 1, n, l, 8, 3, 2, 5, 4, 9, 6, 7. Multiple SECTION
# directives may be given for clarity, and will be concatenated together in
# the expected way.
# If a particular extension is not in this list (say, 1mh), it will be
# displayed with the rest of the section it belongs to. The effect of this
# is that you only need to explicitly list extensions if you want to force a
# particular order. Sections with extensions should usually be adjacent to
# their main section (e.g. "1 1mh 8 ...").
SECTION 1 1m n l 8 3 2 3posix 3pm 3perl 5 4 9 6 7

If the planned Oracle HSM configuration includes additional Linux client hosts, repeat this procedure from the beginning until the client software is installed on all hosts.
Otherwise, go to "Using the samsetup Configuration Wizard" or "Configuring the Basic File System".

Uninstalling Oracle HSM Software

This section outlines following procedures:

Uninstall Oracle HSM on a Solaris Host

Uninstall the Oracle HSM Client on a Linux Host.

Caution:

Do not uninstall software if you intend to upgrade or reinstall Oracle HSM using an existing configuration! Uninstalling removes all configuration files. Instead, use one of the upgrade methods outlined in "Install, Upgrade, or Downgrade Oracle HSM Software on Oracle Solaris Hosts".

Uninstall Oracle HSM on a Solaris Host

To completely uninstall software and remove the configuration files, proceed as follows.

Log in to the host as root.
```
root@solaris:~# 
```
If the software was installed on Solaris 11 or later using the Solaris Image Packaging System, uninstall the software using the command pkg uninstall SUNWsamfs SUNWsamqassy (or pkg uninstall SUNWqfs SUNWsamqassy if only the QFS software is installed).
```
root@solaris:~#  pkg uninstall SUNWsamfs SUNWsamqassy 
```
If the software was installed on Solaris 10 or on Solaris 11 using the SVR4 pkginstall method, uninstall the software using the command pkgrm SUNWsamfsu SUNWsamfsr (pkgrm SUNWqfsu SUNWqfsr if only the QFS software is installed).

Remove the packages in the order specified, starting with SUNWsamfsu and ending with SUNWsamfsr. In the example, we pipe the reply yes into the command so that all questions are automatically answered:
```
root@solaris:~# yes | pkgrm SUNWsamfsu SUNWsamfsr
```
If the software was installed on Solaris 10 or on Solaris 11 using the SVR4 pkginstall method, delete configuration and log files that are no longer required.
```
root@solaris:~# rm -R /var/opt/SUNWsamfs/
root@solaris:~# rm -R /etc/opt/SUNWsamfs/
root@solaris:~# rm -R /var/adm/sam-log/
root@solaris:~# 
```
Reboot the host.
```
root@solaris:~#  reboot 
```
Stop here.

Uninstall the Oracle HSM Client on a Linux Host

To uninstall and completely remove the Linux client software, proceed as follows.

Log in to the Linux client host as root.
```
[root@linux ~]# 
```
Run the Oracle HSM script /var/opt/SUNWsamfs/Uninstall (/var/opt/SUNWqfs/Uninstall if only QFS is installed).

Do not use any other method! Other methods, such as rpm -e, can cause unexpected results and problems with uninstalling or reinstalling the software. So always use the script:
```
[root@linux ~]#  /var/opt/SUNWsamfs/Uninstall
```