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.
Install Solaris Cluster Software (High-Availability Configurations Only)
Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host
Install or Update Oracle HSM Client Software on a Linux Host
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 the installation package for your level of HSM. The download method depends on the version.
For versions 6.1.3 and below, use the Oracle Software Delivery Cloud.
Go to: edelivery.oracle.com
Sign in, or register.
Search for "HSM". Locate the correct version and click Add to Cart.
Click Check Out in the upper right.
Select a language/platform. Click Continue.
Read and accept the terms. Click Continue.
Select the package and then click Download. Save to a directory accessible from all Oracle HSM hosts. For the examples in this chapter, we download the file to the /hsmqfs directory on a network file server named sw_install
While still on the download page, click View Digest. Save these values for comparison to the download. For instructions on calculating checksums from a file, see the Solaris dgst and md5 man pages.
For versions 6.1.4 and above, use My Oracle Support.
Go to: support.oracle.com
Sign in, or register.
Click the Patches & Updates tab.
Within the Patch Search panel, click the Search tab.
Click Product or Family (Advanced).
In the Product field, enter HSM. Select Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software from the product list.
Select the Include all products in family checkbox.
In the Release field, select either:
Oracle Hierarchical Storage Manager (HSM) 6.1.4.0.0
StorageTek QFS Software 6.1
Click Search.
Within the Patch Advanced Search Results panel, click the link in the Patch Name column (this will likely be a number, such as 87654321).
Click Download.
Within the File Download pop-up, click the link for the .zip file. Save it to a directory accessible from all Oracle HSM hosts.
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 zip file in the /hsmqfs subdirectory and then list the contents:
root@sw_install:~# cd /hsmqfs root@sw_install:~# unzip Q12345-02.zip root@sw_install:~# ls Q12345-02/ ./ COPYRIGHT.txt linux.iso README.txt ../ iso.md5 Oracle-HSM_6.1-04/ root@sw_install:~# ls Oracle-HSM_6.1-04/ total 42 ./ COPYRIGHT.txt linux1/ solaris_sparc/ ../ README.txt linux2/ solaris_x64/
Oracle HSM 6.1.4 requires Solaris 11. If running Solaris 11.4, it must be SRU 9 or later. Solaris 10 and earlier releases are no longer supported. Make sure that all Solaris hosts have been upgraded before proceeding:
Log into the host as root.
root@hsmhost:~#
Display the Solaris version number. Use the command uname -v.
In the example, the host is running Solaris 11.4:
root@hsmhost:~# uname -v 11.4.6.4.0 root@hsmhost:~#
If the uname -v command does not return 11.x, upgrade the host operating system using the procedures documented in the Oracle Solaris 11 Information Library, which is available from the Oracle Help Center at: https://docs.oracle.com/en/operating-systems/solaris.html.
Repeat the three preceding steps until all host have been checked and, if necessary, upgraded.
If you are preparing a high-availability file-system, go to "Install Solaris Cluster Software (High-Availability Configurations Only)".
If you are upgrading a multi-host, shared file system, go to "Upgrade Shared Oracle HSM File Systems".
Otherwise, go directly to "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host".
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 "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host".
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:
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.
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 upgrades, 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 "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host" or "Install or Update Oracle HSM Client Software on a Linux Host".
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, mds1. Then, in a second terminal window, we use secure shell (ssh) to log in to the inactive, potential metadata server, mds2:
root@mds1:~#
root@mds1:~# ssh root@mds2
Password:
root@mds2:~#
Upgrade the currently inactive, second metadata server. Install the updated Oracle HSM software using the procedures in "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host" or "Install or Update Oracle HSM Client Software on a Linux Host".
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.
root@mds1:~# samcmd aridle root@mds1:~# samcmd stidle root@mds1:~# samcmd 901 idle ... root@mds1:~# samcmd a ... Waiting for :arrun root@mds1:~# samcmd r ... ty eq status act use state vsn li 801 ---------p 0 0% off empty ... root@mds1:~# samd stop root@mds1:~#
On the second metadata server, load the Oracle HSM configuration files and start Oracle HSM processes. Use the command samd config.
root@mds2:~# samd config root@mds2:~#
On the second metadata server, mount the Oracle HSM file system.
root@mds2:~# mount sharefs1 root@mds2:~#
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 mds2 and the file system name is sharefs1:
root@mds2:~# samsharefs -s mds2 sharefs1 root@mds2:~#
Upgrade the now-inactive first metadata server. Install the updated Oracle HSM software using the procedures in "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host" or "Install or Update Oracle HSM Client Software on a Linux Host".
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.
root@mds2:~# samcmd aridle root@mds2:~# samcmd stidle ... root@mds2:~# samd stop root@mds2:~#
On the first metadata server, load the Oracle HSM configuration files and start Oracle HSM processes. Use the command samd config.
root@mds1:~# samd config root@mds1:~#
On the first metadata server, mount the Oracle HSM file system.
root@mds1:~# mount sharefs1 root@mds1:~#
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 mds1 and the file system name is sharefs1:
root@mds1:~# samsharefs -s mds1 sharefs1 root@mds1:~#
Update the remaining clients. Install the updated Oracle HSM software using the procedures in "Install, Upgrade, or Downgrade Oracle HSM on an Oracle Solaris Host" or "Install or Update Oracle HSM Client Software on a Linux Host"..
Stop here. The upgrade is complete.
To install, upgrade, or downgrade Oracle HSM packages on a Solaris host, start by carrying out the following tasks:
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, use the Solaris Image Packaging System (IPS) command pkg install.
If you are upgrading or downgrading software that was installed using the IPS command pkg install, use the Image Packaging System (IPS) command pkg update.
If you are installing new software on a Solaris 10 host, use the SVR4 pkgrm and pkgadd commands.
If you are upgrading software that was installed using the SVR4 command pkgadd, use the SVR4 pkgrm and pkgadd commands.
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 host as root.
root@solarishosthost:~#
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:
root@solarishosthost:~# samcmd aridle
root@solarishosthost:~#
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:
root@solarishosthost:~# samcmd stidle
root@solarishosthost:~#
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:
root@solarishosthost:~# samcmd a
Archiver status samcmd 6.1.4 10:20:34 Feb 20 2015
samcmd on host
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:
root@solarishosthost:~# samcmd u Staging queue samcmd 6.1.4 10:20:34 Feb 20 2015 samcmd on solaris.demo.lan Staging queue by media type: all sam-stagerd: Waiting for :strun root@solarishosthost:~#
Idle all removable media drives before proceeding further. For each drive, use the command samcmd idle equipment-number, 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:
root@solarishosthost:~# samcmd idle 801 root@solarishosthost:~# samcmd idle 802 root@solarishosthost:~# samcmd idle 803 root@solarishosthost:~# samcmd idle 804 root@solarishosthost:~#
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.
root@solarishosthost:~# samcmd r Removable media samcmd 6.1.4 10:37:09 Feb 20 2014 samcmd on host 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 root@solarishosthost:~#
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.
root@solarishosthost:~# samd stop root@solarishosthost:~#
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 hsmqfs1.
root@solarishosthost:~# unshare /hsmqfs1
root@solarishosthost:~#
In the second example, we stop NFS sharing of the Oracle HSM shared file system samqfs2:
root@solarishostserver:~# unshare /hsmqfs2
root@solarishostserver:~#
Unmount all Oracle HSM file systems.
In the first example, we unmount the unshared, standalone file system hsmqfs1:
root@solarishosthost:~# umount hsmqfs1
In the second example, we unmount the shared file system hsmqfs1, first from the clients and then from the server, allowing 60 seconds for clients to unmount.
root@solarishostserver:~# ssh root@samqfs2client1 Password: [root@solarishostclient1:~# umount /hsmqfs2 [root@solarishostclient1:~# exit root@solarishostserver:~# root@solarishostserver:~# ssh root@samqfs2client1 Password: root@solarishostclient2:~# umount /hsmqfs2 root@solarishostclient2:~# exit root@solarishostserver:~# 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:
root@solarishosthost:~# yes | pkgrm SUNWsamfsu SUNWsamfsr
Next, locate the Oracle HSM packages for your host architecture.
Log in to the Oracle HSM host as root.
root@solarishost:~#
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.1.4+/. 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.1.4-01/.
In the example we change to the download directory for the initial release of the software, Oracle_HSM_6.1.4/ and list the contents:
root@solarishost:~# cd /net/sw_install/hsmqfs/Oracle_HSM_6.1.4/ root@solarishost:~# 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@solarishost:~# cd solaris_sparc/ root@solarishost:~# ls -1 ./ ../ S11.0/ S11.4/ S11.0_ips/ S11.4_ips/
IMPORTANT:
Choose the correct directory:S11.0 for Solaris 11.0 - 11.3
S11.4 for Solaris 11.4
S11.4 for SVr4 packages
S11.4_ips for IPS packages
When Solaris 11 or later is installed on the host, you can install, upgrade, or downgrade the software using the Image Packaging System. Go to one of the following:
When Solaris 11 or later is installed on the host, you can also choose to install, upgrade, or downgrade the software using the pkgadd method. See "Upgrade or Downgrade the Software Using SVR4 pkgrm and pkgadd Commands".
When Solaris 10 is installed on the host, you can install, upgrade, or downgrade the software using the pkgadd method. Go to "Upgrade or Downgrade the Software Using SVR4 pkgrm and pkgadd Commands".
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 Oracle HSM 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.1.4, Oracle_HSM_6.1.4/solaris_sparc/S11_ips/repo.samqfs:
root@solarishost:~# cd repo.samqfs/ root@solarishost:~#
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@solarishost:~# 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@solarishost:~# 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@solarishost:~# /opt/SUNWsamfs/util/sam-qfs-post-install
SUNWsamfs IPS package installed.
inquiry.conf may have been updated for this release.
...
root@solarishost:~#
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 they are 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 a Linux Host".
Otherwise, go to "Using the samsetup Configuration Wizard" or "Configuring the Basic File System".
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 Oracle HSM 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@solarishost:~# pkg update -g . --accept SUNWsamfs SUNWsamqassy ... root@solarishost:~#
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@solarishost:~# pkg update -g . --accept SUNWqfs SUNWsamqassy ... root@solarishost:~#
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.1.4.0 is installed on the host:
root@solarishost:~# samcmd l
Usage information samcmd 6.1.4.0 14:06:20 Feb 20 2015 ...
root@solarishost:~#
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.1.4/solaris_sparc/S11_ips/repo.samqfs:
root@solarishost:~# pwd /net/Oracle_HSM_6.1.4/solaris_sparc/S11_ips/repo.samqfs root@solarishost:~# 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@solarishost:~# 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@solarishost:~#
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@solarishost:~# 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@solarishost:~# pkg update -g . SUNWsamqassy@5.4,5.11:20140926T172135Z ... root@solarishost:~#
Once the pkg update command has finished, restart the system. Use the Solaris reboot command.
root@solarishost:~# reboot
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 a Linux Host".
pkgrm and pkgadd CommandsUse 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 Oracle HSM 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.1.4/solaris_sparc/S10. Then we pipe the reply yes into the command so that all questions are automatically answered:
root@solarishost:~# pwd /net/Oracle_HSM_6.1.4/solaris_sparc/s10 root@solarishost:~# 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@solarishost:~# 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 a Linux Host".
Otherwise, go to Chapter 5, "Using the samsetup Configuration Wizard" or Chapter 6, "Configuring the Basic File System".
pkgrm and pkgadd CommandsUse 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.1.4 configuration files for use with Oracle SAM 5.3:
root@solarishost:~# /opt/SUNWsamfs/sbin/backto 5.3 ...
root@solarishost:~#
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@solarishost:~# yes | pkgrm SUNWsamfsu SUNWsamfsr
If you have not already done so, locate the Oracle HSM 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.1.4/solaris_sparc/S10. Then we pipe the reply yes into the command so that all questions are automatically answered:
root@solarishost:~# pwd /net/Oracle_HSM_6.1.4/solaris_sparc/s10 root@solarishost:~# 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@solarishost:~# pwd /net/Oracle_HSM_6.1.4/solaris_sparc/s10 root@solarishost:~# 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 a Linux Host".
Otherwise, go to Chapter 5, "Using the samsetup Configuration Wizard" or Chapter 6, "Configuring the Basic File System".
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 "Download the HSM Installation Package").
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: root@sw_install:~# 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".
This section outlines following procedures:
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 on an Oracle Solaris Host".To completely uninstall software and remove the configuration files, proceed as follows.
Log in to the host as root.
root@solarishost:~#
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@solarishost:~# 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@solarishost:~# 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@solarishost:~# rm -R /var/opt/SUNWsamfs/ root@solarishost:~# rm -R /etc/opt/SUNWsamfs/ root@solarishost:~# rm -R /var/adm/sam-log/ root@solarishost:~#
Reboot the host.
root@solarishost:~# reboot
Stop here.
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