6-68044-01 Rev. K StorNext 5 and StorNext FX 5 Upgrade Guide

6-68044-01 Rev. K StorNext 5 and StorNext FX 5 Upgrade Guide
Upgrade Guide
StorNext 5 and StorNext FX 5
6-68044-01 Rev K
*6-68044-01*
StorNext 5 and StorNext FX 5 Upgrade Guide, 6-68044-01 Rev K, October 2016, Product of USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including
but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation
may revise this publication from time to time without notice.
COPYRIGHT STATEMENT
© 2016 Quantum Corporation. All rights reserved.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written
authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law.
TRADEMARK STATEMENT
Artico, Be Certain (and the Q brackets design), DLT, DXi, DXi Accent, DXi V1000, DXi V2000, DXi V4000, GoVault,
Lattus, NDX, the Q logo, the Q Quantum logo, Q-Cloud, Quantum (and the Q brackets design), the Quantum logo,
Quantum Be Certain (and the Q brackets design), Quantum Vision, Scalar, StorageCare, StorNext,
SuperLoader, Symform, the Symform logo (and design), vmPRO, and Xcellis are either registered trademarks or
trademarks of Quantum Corporation and its affiliates in the United States and/or other countries. All other trademarks
are the property of their respective owners.
Products mentioned herein are for identification purposes only and may be registered trademarks or trademarks of their
respective companies. All other brand names or trademarks are the property of their respective owners.
Quantum specifications are subject to change.
StorNext 5 and StorNext FX 5 Upgrade Guide
ii
Contents
Preface
vi
Chapter 1: Introduction
1
System Requirements
1
StorNext FX Upgrades
2
DVD Directories
2
Chapter 2: Getting Ready to Upgrade
4
Upgrade Considerations
5
Upgrade Guidelines
5
StorNext Licensing
8
Upgrade Implications
8
Freeing Media Capacity
8
Upgrading from snsm_was License to object_storage License
9
Upgrade Summary Steps For Non-HA Systems
9
Upgrading the Client Software
10
StorNext Media on DVD
10
Post-Upgrade Browser Refresh
10
StorNext 5 and StorNext FX 5 Upgrade Guide
iii
Contents
Considerations for Downloading the Installation Files from the Web
Chapter 3: Running the Pre-Installation Script
11
13
Before You Begin
14
Running snPreInstall
15
Interpreting snPreInstall Output
16
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
Upgrading non-HA Linux MDCs to StorNext 5
18
18
The License Check Option
21
SSL Certificate Exception
22
Chapter 5: Upgrading a Windows Client or Non-HA Server to
StorNext 5
Upgrading a Windows Client or Non-HA Server to StorNext 5
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
23
23
26
26
HA Upgrade Options
26
Upgrading a StorNext 4.3.2 or later HA System to StorNext 5 HA System on the Linux OS
27
Upgrading a Windows 4.3.x or later HA System to 5 HA
30
Chapter 7: Upgrading HA Systems To StorNext 5 with .RPM Files
Upgrading HA Systems To StorNext 5 with .RPM Files
Upgrading a 4.1 or later HA System to 5 using RPM files
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
32
32
32
35
35
StorNext Software Requirements
35
StorNext FX Upgrades
36
Upgrading Linux and Unix Clients
36
StorNext 5 and StorNext FX 5 Upgrade Guide
iv
Contents
Upgrade Debian Linux
44
Upgrading Sun Solaris Clients
46
Upgrading AIX Clients
47
Upgrading HP-UX Clients
48
Chapter 9: Upgrading of SNSM Object Storage Configuration to
StorNext 5 release 5.1 (or later)
Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Converting an AXR Namespace to an S3 Bucket
Chapter 10: Upgrading Firmware
Upgrading Firmware
Chapter 11: Compression and Encryption Usage Report
Compression and Encryption Usage Report
StorNext 5 and StorNext FX 5 Upgrade Guide
50
50
53
54
54
55
55
v
Preface
This manual contains the following chapters:
l
Chapter 1: Introduction
l
Chapter 2: Getting Ready to Upgrade
l
Chapter 3: Running the Pre-Installation Script
l
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
l
Chapter 5: Upgrading a Windows Client or Non-HA Server to StorNext 5
l
Chapter 6: Upgrading HA Systems To StorNext 5
l
Chapter 7: Upgrading HA Systems To StorNext 5 with .RPM Files
l
Chapter 8: Upgrading Clients To StorNext 5
l
Chapter 9: Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
l
Chapter 10: Upgrading Firmware
l
Chapter 11: Compression and Encryption Usage Report
Audience
This manual is written for StorNext 5 and StorNext FX 5 (FX stands for File System for Xsan) operators,
system administrators, and field service engineers.
StorNext 5 and StorNext FX 5 Upgrade Guide
vi
Preface
Notational Conventions
This manual uses the following conventions:
Convention Example
User input is shown in bold monospace font.
./DARTinstall
Computer output and command line examples are shown in
monospace font.
./DARTinstall
User input variables are enclosed in angle brackets.
http://<ip_address>/cgi-bin/stats
For UNIX and Linux commands, the command prompt is implied.
./DARTinstall
is the same as
# ./DARTinstall
File and directory names, menu commands, button names, and
window names are shown in bold font.
/data/upload
Menu names separated by arrows indicate a sequence of menus to
be navigated.
Utilities > Firmware
The following formats indicate important information:
Note: Note emphasizes important information related to the main topic.
Caution: Caution indicates potential hazards to equipment or data.
WARNING: Warning indicates potential hazards to personal safety.
l
Right side of the system - Refers to the right side as you face the component being described.
l
Left side of the system - Refers to the left side as you face the component being described.
l
Data sizes are reported in base 1000 rather than base 1024. For example:
o
1 MB = 1,000,000 bytes
o
1 GB = 1,000,000,000 bytes
o
1 TB = 1,000,000,000,000 bytes
Product Safety Statements
Quantum will not be held liable for damage arising from unauthorized use of the product. The user assumes
all risk in this aspect.
StorNext 5 and StorNext FX 5 Upgrade Guide
vii
Preface
This unit is engineered and manufactured to meet all safety and regulatory requirements. Be aware that
improper use may result in bodily injury, damage to the equipment, or interference with other equipment.
For the most up to date information on StorNext 5 and StorNext FX 5, see:
http://www.quantum.com/serviceandsupport/index.aspx
StorNext 5 and StorNext FX 5 Upgrade Guide
viii
Preface
Contacts
For information about contacting Quantum, including Quantum office locations, go to:
http://www.quantum.com/aboutus/contactus/index.aspx
Comments
To provide comments or feedback about this document, or about other Quantum technical publications,
send e-mail to:
doc-comments@quantum.com
Getting More Information or Help
StorageCare™, Quantum’s comprehensive service approach, leverages advanced data access and
diagnostics technologies with cross-environment, multi-vendor expertise to resolve backup issues faster
and at lower cost.
Accelerate service issue resolution with these exclusive Quantum StorageCare services:
l
Service and Support Website - Register products, license software, browse Quantum Learning
courses, check backup software and operating system support, and locate manuals, FAQs, firmware
downloads, product updates and more in one convenient location. Get started at:
http://www.quantum.com/serviceandsupport/index.aspx
l
eSupport - Submit online service requests, update contact information, add attachments, and receive
status updates via email. Online Service accounts are free from Quantum. That account can also be used
to access Quantum’s Knowledge Base, a comprehensive repository of product support information. Get
started at:
https://onlineservice.quantum.com
For further assistance, or if training is desired, contact the Quantum Customer Support Center:
Region
Support Contact
North America
1-800-284-5101 (toll free)
+1-720-249-5700
EMEA
+800-7826-8888 (toll free)
+49 6131 324 185
StorNext 5 and StorNext FX 5 Upgrade Guide
ix
Preface
Region
Support Contact
Asia Pacific
+800-7826-8887 (toll free)
+603-7953-3010
For worldwide support:
http://www.quantum.com/serviceandsupport/index.aspx
Worldwide End-User Product Warranty
For more information on the Quantum Worldwide End-User Standard Limited Product Warranty:
http://www.quantum.com/serviceandsupport/warrantyinformation/index.aspx
StorNext 5 and StorNext FX 5 Upgrade Guide
x
Chapter 1: Introduction
This chapter contains the following topics:
System Requirements
1
StorNext FX Upgrades
2
DVD Directories
2
This document provides instructions for upgrading metadata controllers (MDCs) running StorNext File
System (SNFS) and StorNext Storage Manager (SNSM) to StorNext 5 from supported StorNext releases.
Instructions are provided for upgrading and staging StorNext client upgrades.
System Requirements
The operating systems, kernel versions, hardware platforms, hardware, and network requirements, for both
StorNext MDCs and StorNext and StorNext FX clients are listed in the StorNext 5 Compatibility Guide
available online at: http://www.quantum.com/sn5docs.
Make sure the system meets all the requirements outlined in the guide, and, if necessary, update your
system before upgrading StorNext.
StorNext 5 and StorNext FX 5 Upgrade Guide
1
Chapter 1: Introduction
StorNext FX Upgrades
StorNext FX Upgrades
If you need to upgrade StorNext FX software, follow the installation instructions for your particular platform
as described in the current version of the StorNext 5 Installation Guide available online at
http://www.quantum.com/sn5docs.
DVD Directories
Files on the StorNext installation DVD are located in the following locations, depending on whether a media
kit DVD or a user-created DVD from an .iso image for a web-release download is used:
Directory Location
Directory
Contents
Media Kit DVD
/fs_only
This contains the installation binaries for supported
platforms for StorNext Filesystem-only and Filesystemonly clients and clients plus Distributed Data Mover
(DDM), which are located in the _plus_mover directory.
This also contains the StorNext and StorNext FX client
installation binaries for supported platforms.
/stornext_full
This contains the installation binaries for supported
platforms for full installation of StorNext, including both
the File System and Storage Manager.
/stornext_full/clients
This contains the StorNext and StorNext FX client
installation binaries for supported platforms.
/documentation
This contains the current set of StorNext documentation
and the documentation front end, which provides a way to
navigate to the documents.
/offlinenotification
This contains the installation binaries for supported
platforms for StorNext offline notification installations.
StorNext 5 and StorNext FX 5 Upgrade Guide
2
Chapter 1: Introduction
DVD Directories
Directory Location
Directory
Contents
Web Release DVD
/fs_only
This contains the installation binaries for supported
platforms for StorNext Filesystem-only and Filesystemonly clients and clients plus Distributed Data Mover
(DDM), which are located in the _plus_mover directory.
This also contains the StorNext and StorNext FX client
installation binaries for supported platforms.
/stornext_full
This contains the installation binaries for supported
platforms for full installation of StorNext, including both
the File System and Storage Manager.
/stornext_full/clients
This contains the StorNext and StorNext FX client
installation binaries for supported platforms.
/offlinenotification
This contains the installation binaries for supported
platforms for StorNext offline notification installations.
StorNext 5 and StorNext FX 5 Upgrade Guide
3
Chapter 2: Getting Ready to
Upgrade
This chapter contains the following topics:
Upgrade Considerations
5
Upgrade Guidelines
5
StorNext Licensing
8
Upgrading the Client Software
10
StorNext Media on DVD
10
Post-Upgrade Browser Refresh
10
Considerations for Downloading the Installation Files from the Web
11
This section includes important information about upgrading to StorNext 5. Review the following sections
before upgrading:
l
Upgrade Considerations on the next page
l
Upgrade Guidelines on the next page
l
StorNext Licensing on page 8
l
Upgrading the Client Software on page 10
l
StorNext Media on DVD on page 10
l
Post-Upgrade Browser Refresh
l
Considerations for Downloading the Installation Files from the Web on page 11
StorNext 5 and StorNext FX 5 Upgrade Guide
4
Chapter 2: Getting Ready to Upgrade
Upgrade Considerations
Upgrade Considerations
Before you begin the upgrade you should note the following considerations so you can plan accordingly.
Consider the following prior to upgrading:
l
Not all StorNext releases may be upgraded to a given StorNext 5 release. As a result, an upgrade to the
current version of StorNext may require multiple, incremental upgrades, depending on the version of
StorNext currently installed.
For information about supported upgrade paths for StorNext 5, consult the StorNext 5 Compatibility
Guide. If your system is running a StorNext release prior to the supported upgrade releases for a given
StorNext 5 release, consult an earlier version of the StorNext 5 Compatibility Guide that applies to your
specific upgrade, and the dependencies for StorNext Clients in the environment.
l
Firmware upgrade installation files must first be acquired from Quantum.
Note: You can upgrade directly to StorNext 5 only from StorNext 4.3.2 and later releases; except
StorNext 4.6.x, which requires you upgrade to StorNext 4.7.0.1 before upgrading to StorNext 5.
If your MDC is using a StorNext release earlier than 4.3.2, you must first upgrade the MDC to at least
StorNext 4.3.2 and then to StorNext 5.
See the StorNext 5 Compatibility Guide for supported upgrade versions for a given StorNext release.
Upgrade Guidelines
Before upgrading StorNext review the following upgrade guidelines:
Note: This upgrade guide documents supported upgrades to StorNext 5 only. For customers with
older versions of StorNext, consult the StorNext Upgrade Guide that corresponds to the version of
StorNext you are upgrading to.
Note: StorNext 5 requires a minimum journal size of 4MB and a recommended size of 64MB. If you
have file systems with journal sizes less than the 4MB minimum, you must resize their journals before
upgrading to StorNext 5. Use the cvupdatefs utility or the GUI to resize the journal. When the journal
is resized, the new size must be 16MB or greater. File systems with journals between 4MB and 16MB
will run with StorNext 5, but it is recommended that these file systems have their journal resized to the
recommended 64MB.
Note: For non-Windows upgrades, the snPreInstall script must be run prior to install.stornext.
l
l
Beginning with 4.3.0, StorNext uses a MySQL database for information needed internally by Storage
Manager.
The MySQL database requires a minimum of 8 GB of RAM.
StorNext 5 and StorNext FX 5 Upgrade Guide
5
Chapter 2: Getting Ready to Upgrade
Upgrade Guidelines
Before attempting to upgrade from a previous StorNext release, make sure you have free space on the
file system. If the file system is nearly full when you begin the upgrade, serious errors may occur or the
upgrade could fail. Best practice is to maintain an area on the file system which is not used for data or
system files, but is reserved as an empty buffer to ensure that upgrades and other operations complete
successfully.
l
StorNext 5 and later has the following additional disk space requirements:
l
Table 1: Space requirements from snPreInstall
Component
Directory Space Required
Database
231 MB
Journal
11 MB
Mapping
157 MB
Metadata
333 MB
MySQL_tmp
120 MB
Total
852 MB
* Space requirements based on the following:
l
250, 000 files
l
10, 000 directories
l
1 copy per file
l
1 version per file
Additional space will be required as Storage Manager manages more files, directories, copies and versions.
l
l
If you are planning on upgrading your RHEL5 to RHEL6, refer to Replacing an MDC in a non-HA
environment (non-backup/restore method)” in the “Replacing an MDC” topic of the StorNext User’s
Guide.
Make sure the MDC uses a supported operating system and platform, and if necessary update to a
supported release or kernel version before installing StorNext.
Note: There is a potential problem with the system clock on Nehalem Intel processors that can cause
the clock to jump and temporarily freeze the system. The problem affects RedHat Linux releases 6.0,
6.1, 6.2 and their CentOS counterparts on systems with Intel processor versions identified by the
internal codename Nehalem. The fix involves changing the kernel parameters in the grub.conf file.
Follow the steps below to modify the grub.conf file so that the Intel sleep state is disabled. Making this
change could result in increased power consumption, but it helps prevent problems which result in
system hangs due to processor power transition.
1. For the above systems, prior to installation:
Add the following text to the "kernel" line in /boot/grub/grub.conf:
StorNext 5 and StorNext FX 5 Upgrade Guide
6
Chapter 2: Getting Ready to Upgrade
Upgrade Guidelines
grub.conf:idle=poll intel_idle.max_cstate=0 processor.max_cstate=1
In some cases, performance can also be improved by adjusting the idle kernel parameter. However,
care should be taken when using certain values. For example, idle=poll maximizes performance
but is incompatible with hyperthreading (HT) and will lead to very high power consumption. For
additional information, refer to the documentation for your version of Linux.
2. Reboot the system for the change to take effect.
l
l
l
l
Before upgrading, make sure there is no I/O activity. On the StorNext home page, the number of store
candidates should be zero. For tape drives, make sure no media is mounted and no read/write
operations are being performed. If there is I/O activity, wait for the I/O activity to complete before
upgrading. If you attempt to perform an upgrade during a period of high activity, the upgrade may fail.
Before upgrading, Quantum recommends reviewing system configuration settings and performing a
backup procedure to back up StorNext configuration files.
Before upgrading, Quantum recommends storing all files. (If you do not store files prior to upgrading,
Quantum recommends running a rebuild policy after the upgrade.)
Before upgrading, Quantum recommends making sure all tape drives are at approved firmware levels.
After upgrading, you may not be able to use drives that are not running an approved firmware version.
Caution: As the File System Manager (FSM) supports over 1000 clients (with more than 1000 file
requests per client), the resource limits of your MDC may be exhausted with additional load from other
processes. Exceeding the file descriptor limit will cause errors to your system. Quantum recommends
you not run additional applications on the MDC.
Note: The performance of the storage holding the Storage Manager database and metadumps has an
impact on overall StorNext file system performance. Quantum recommends that the Storage Manager
database and metadata dumps are stored on high performance storage devices, such as a RAID array.
Storing the Storage Manager database on slower storage devices, including local disks, can result in
poor performance or time-outs.
Note: The install.stornext script will scan the rpms that are to be installed to ensure that all
dependencies will be successfully resolved. Unresolved dependencies will result in a warning from the
install.stornext script, and prompt the user to either quit or continue. Continuing without resolving the
dependencies may result in system instability or StorNext not being able to operate. It is strongly
recommended that the missing dependencies are resolved prior to installing StorNext.
Consult your operating system's package repository for the missing dependencies. Required
dependencies include gcc, make, and kernel-headers on Redhat or kernel-source on SuSE.
Note: The UIDs for the quantumdb and tdlm users and the adic group must be identical on both
nodes of an HA pair. If the UIDs are not identical, the MySQL database will not start (due to file
permission errors), which in turn prevents storage manager from fully starting up. Quantum
recommends creating the UIDs for the quantumdb and tdlm users along with the adic group on both
nodes prior to running install.stornext.
StorNext 5 and StorNext FX 5 Upgrade Guide
7
Chapter 2: Getting Ready to Upgrade
StorNext Licensing
StorNext Licensing
Separate licenses are required for different StorNext components (such as File System and Storage
Manager) and features (such as Replication, HA and Distributed Data Mover.)
For a list of all the StorNext licenses, refer to the current StorNext5 Licensing Guide available online at:
http://www.quantum.com/sn5docs.
New in StorNext 5 release 5.2. Disk licensing has been added to StorNext in order to help quantify
customers’ configurations. Disk licenses are required on all StorNext Metadata Controllers (MDCs) but may
be updated after upgrade. For additional information on disk licensing, see the StorNext 5 and StorNext FX
5 Licensing Guide.
Upgrade Implications
Be aware of the following upgrade-related implications and plan accordingly:
l
l
l
l
l
A non-expired Maintenance license is required to perform a StorNext upgrade. This means you must
contact Quantum Technical Support for a Maintenance license before you can upgrade StorNext.
The Maintenance license provided by Quantum Technical Support must be put into place prior to the
upgrade, or you will not be allowed to proceed with the upgrade. You can either enter licenses through
the StorNext GUI or manually edit the license.dat file.
You will still be allowed to run StorNext if the Maintenance license expires. However, no future upgrades
will be allowed.
The Maintenance license must remain in place even after expiration to allow the StorNext software to
run, because it indicates which version of the software was purchased.
When you extract client/server .bin files, you must read and accept the StorNext End User License
Agreement (EULA).
Freeing Media Capacity
If you are ready to upgrade and then notice that the Storage Manager capacity has been exceeded, you can
follow the procedure below to free up capacity to bring it under the licensed value. These steps will clean up
“dead space” on tape media, and do not apply to storage disks.
1. Run the fsmedcopy command with no arguments. Running command generates a report of media
and wasted space. The report looks similar to this:
% fsmedcopy
-----------------------------------------------------------Media Fragmentation Report Thu Feb 4 15:18:14 2010
Media ID Fill Level Wasted Space
StorNext 5 and StorNext FX 5 Upgrade Guide
8
Chapter 2: Getting Ready to Upgrade
StorNext Licensing
-----------------------------------------------------------000099 10.00 0.00
000098 30.00 5.00
000096 70.99 44.98
000095 0.12 99.65
The “Fill Level” column displays how full the media is. The “Wasted Space” column indicates how much
of the used space is wasted, NOT the percentage of the entire tape.
Media with high percentages for both values (such as media 000096 in the example) are good
candidates for eliminating dead space.
2. For each media you identify as having significant dead space, run this command:
% fsmedcopy -r <mediaid>
Note: On a large system, the fsmedcopy report can take a long time to complete. If your site is
dynamic (that is, it has a lot of file removes and updates,) you can skip step 1 and just pick media
you know are full, and then run the command fsmedcopy -r against those media.
Upgrading from snsm_was License to object_storage
License
If you are upgrading to StorNext 5 release 5.1 (or later), and you have an existing snsm_was license:
1. Obtain a new license file for your system that includes the new object_storage license.
2. Manually create a staging area for the license update at /usr/cvfs/update/config. Do this on both
the primary and secondary nodes in an HA environment.
3. Manually copy in the new license.dat file to /usr/cvfs/update/config. Do this on both the
primary and secondary nodes in an HA environment.
4. Upgrade to StorNext 5 release 5.1 (or later) per the applicable procedure in this document.
Upon a successful upgrade, use the StorNext GUI to verify the license object_storage is installed.
Upgrade Summary Steps For Non-HA Systems
Taking into consideration the new licensing procedures, here is a summary of the steps necessary to
upgrade to 5:
1. Obtain the necessary licenses from Quantum Technical Support.
2. Update the license.dat file with a current Maintenance license and any other StorNext
component/feature licenses you have purchased.
StorNext 5 and StorNext FX 5 Upgrade Guide
9
Chapter 2: Getting Ready to Upgrade
Upgrading the Client Software
3. Run the upgrade program as explained in Upgrading non-HA Linux MDCs to StorNext 5 on page 18.
4. Log in to the StorNext GUI.
5. Use the StorNext Configuration Wizard to finish configuring your system.
Upgrading the Client Software
To upgrade to the StorNext 5 client software on Linux and Unix systems, install the new client software
package. There is no need to uninstall previous versions of the client software. (On Solaris systems, you will
need to uninstall previous versions before upgrading.) For more information about installing the client
software on Linux and Unix, see the current StorNext Installation Guide.
The steps required to upgrade clients to StorNext 5 includes the following:
1. Unmount all StorNext file systems.
2. Stopping the cvfs services by running /etc/init.d/cvfs fullstop,
/sbin/init.d/cvfs fullstop, or some other method.
3. Unpack the new build.
4. Unload and load or upgrade rpm/package/builds.
5. Restart services.
6. Check cvadmin/cvlabel.
7. Mount the StorNext file systems.
StorNext Media on DVD
Installation and upgrade media is shipped on DVDs. If you plan to install from media, you must have a DVD
ROM drive to perform the installation or upgrade. See DVD Directories on page 2 for information on the
directories used on the DVD.
Post-Upgrade Browser Refresh
Quantum recommends to clear the browser and cookie cache after upgrading to a StorNext release before
logging into the GUI on the upgraded system.
The steps used to clear the cache depend on the browser:
StorNext 5 and StorNext FX 5 Upgrade Guide
10
Chapter 2: Getting Ready to Upgrade
Considerations for Downloading the Installation Files from the Web
For Google Chrome
1. Click the configuration icon and the Settings option.
2. Click the Show advanced settings option.
3. In the Privacy section, click Clear browsing data.
4. Select the beginning of time option in the Obliterate the following items from menu.
5. Select the Clear browsing history, Empty the cache, and Delete cookies and other... options.
6. Click Clear browsing data.
7. Close the Settings tab.
For Internet Explorer
1. Go to Tools > Internet Options.
2. On the General tab, look in the Browsing History section and click Delete.
3. Select the Temporary Internet Files and Cookies options.
4. Click Delete.
5. Click OK to close the Internet Options dialog.
For Mozilla Firefox
1. Click Tools > Clear Recent History. (If this option is not visible, right-click the top of the browser
window and select the Menu Bar option).
2. In the Time Range to Clear menu, select Everything.
3. Click Details, and select the Browsing & Download History, Cookies, and Cache options.
4. Click Clear Now.
Considerations for Downloading the Installation
Files from the Web
The upgrade instructions in the following sections are for DVD upgrades. If you download your StorNext
installation software from the Web, your steps will be slightly different. You will download an executable
program that will require you to accept the StorNext end user license agreement and will then extract the
StorNext installer.
Note: If you are performing an upgrade on a single MDC node system using RPM files, see Installing
StorNext File System-Only from RPMs section in the current StorNext 5 Installation Guide.
As part of the installation from a Web download, the software files are extracted into the /tmp/stornext
directory by default. The software, when extracted, requires approximately 800 MB of space. Make sure
there is enough free space in the default directory to extract the files. If there is not sufficient space, you may
need to specify an alternative directory with the -d option.
StorNext 5 and StorNext FX 5 Upgrade Guide
11
Chapter 2: Getting Ready to Upgrade
Considerations for Downloading the Installation Files from the Web
Note: When selecting install packages to download from the web, observe that the stornext_full
directory includes the Storage Manager install packages and the fs_only directory installs the StorNext
File System only.
To specify an alternate location before beginning the installation, enter the following command:
# ./<installation file> -d <dir>
where <installation file> is the name of the installation file, and <dir> is the directory into which you
want to extract the installation files.
StorNext 5 and StorNext FX 5 Upgrade Guide
12
Chapter 3: Running the PreInstallation Script
This chapter contains the following topics:
Before You Begin
14
Running snPreInstall
15
Interpreting snPreInstall Output
16
StorNext 5 has several dependency checks to make sure required RPM packages are installed. The
dependency checks include environmental requirements, such as:
l
Disk space
l
LTFS appliance
The StorNext pre-installation script (snPreInstall) is included on the StorNext installation DVD (for nonWindows installations only). When you run snPreInstall, you are prompted for information about your
system. The pre-installation script uses this information to estimate the amount of local disk space required
for SNFS and SNSM support directories. In addition, the script recommends the optimal locations for
support directories.
StorNext uses four directories to store application support information. These directories are stored locally
on the server.
The StorNext support directories are described in Table 1 on the next page.
StorNext 5 and StorNext FX 5 Upgrade Guide
13
Chapter 3: Running the Pre-Installation Script
Before You Begin
Table 1: StorNext Support Directories
Support Directory*
Description
Database
/usr/adic/database
Records information about where and how data files are
stored.
Journal
Records changes made to the database.
/usr/adic/database/journal
Mapping
/usr/adic/TSM/internal/mapping_dir
Contains index information that enables quick searches
on the file system.
Metadata
Stores metadata dumps (backups of file metadata).
/usr/adic/database/metadumps
* Depending on file system configuration, the support directory locations may be different. However, symbolic links in
/usr/adic/ will always point to the support directories.
Note: For optimal performance in non-HA configurations, the Metadata directory should not be
located on the same file system as (in order of priority) the Journal, Database, or Mapping directory.
Before You Begin
Before running the pre-installation script, be prepared to answer the following questions:
l
Is this an upgrade installation?
l
What local file systems can be used to store support information?
l
What version of StorNext will be installed?
l
What is the maximum number of directories expected (in millions)?
l
What is the maximum number of files expected (in millions)?
l
How many copies will be stored for each file?
l
How many versions will be retained for each file?
Note: Keep in mind that storage needs typically grow rapidly. Consider increasing the maximum
number of expected directories and files by a factor of 2.5x to ensure room for future growth.
Note: The pre-installation script ignores unmounted file systems. Before running snPreInstall, be sure
to mount all local file systems that will hold StorNext support information.
StorNext 5 and StorNext FX 5 Upgrade Guide
14
Chapter 3: Running the Pre-Installation Script
Running snPreInstall
Running snPreInstall
To run the pre-installation script, use the StorNext installation DVD.
1. Log on to the MDC as root.
2. Mount the StorNext installation DVD and change to the DVD root directory.
Note: When you mount a DVD in a Red Hat 5 system, DVDs are mounted by default with a noexec
(non-executable) option which prevents you from proceeding with the installation.
For Red Hat users only, before proceeding you must remount the DVD by typing mount -o remount, exec ...
3. List the installation directories on the DVD. At the command prompt, type:
ls -l
4. Change to the stornext_full directory.
Note: Make sure you are in the stornext_full directory and not the fs_only directory. The fs_only directory installs the StorNext File System only.
5. List the directories in the stornext_full directory. At the command prompt, type:
ls -l
6. Identify the correct installation directory for your operating system and hardware platform, and then
change to that directory.
For example, for Red Hat Linux 5 running on an x86 64-bit platform, change to the RedHat50AS_
26x86_64 directory.
7. Run the script. At the command prompt, type:
./snPreInstall
The pre-installation script runs (Figure 1 on the next page).
StorNext 5 and StorNext FX 5 Upgrade Guide
15
Chapter 3: Running the Pre-Installation Script
Interpreting snPreInstall Output
Figure 1: Pre-Installation Script
8. Follow the onscreen instructions, and answer each question when prompted.
The script outputs results based on the information you entered.
Interpreting snPreInstall Output
After you enter all requested information, the pre-installation script outputs the following results:
l
Estimated disk space required for each support directory.
l
Recommended file system location for each support directory.
Note: For optimal performance, each support directory should be located on its own local file system,
and each local file system should reside on a separate physical hard disk on the server computer.
There are three types of directory recommendations, as indicated by the text preceding the
recommendation. The three types of recommendations are described in Table 2 below.
Table 2: Pre-Installation Script Recommendation Types
Type
Description
RECOMMEND
The suggested directory locations will result in optimal system performance.
NOTE
The suggested directory locations are valid but system performance will not be
optimal.
SPACE
Additional hard disk space is required to store the required support directories.
StorNext 5 and StorNext FX 5 Upgrade Guide
16
Chapter 3: Running the Pre-Installation Script
Interpreting snPreInstall Output
The pre-installation script bases directory location recommendations on the following criteria:
l
l
To aid disaster recovery, the Database and Journal directories should be located on different file
systems.
For optimal performance, each support directory should be located on its own local file system, and each
local file system should reside on a separate physical hard disk in the MDC.
Note: These recommendations apply to non-HA systems only.
StorNext 5 and StorNext FX 5 Upgrade Guide
17
Chapter 4: Upgrading non-HA
Linux MDCs to StorNext 5
This chapter contains the following topics:
Upgrading non-HA Linux MDCs to StorNext 5
18
Upgrading non-HA Linux MDCs to StorNext 5
Use the StorNext installation script to upgrade to StorNext 5 on a metadata controller running StorNext
Storage Manager and StorNext File System. The installation script will upgrade full StorNext installations.
To launch the script, use the StorNext installation DVD.
Note: If you are performing an upgrade on a single MDC node system using RPM files, see Installing
StorNext File System-Only from RPMs in the current StorNext Installation Guide.
The following instructions apply to non-HA server upgrades. However, they may also be used to upgrade
RPM-only configurations to a full StorNext configuration. For instruction on upgrading HA servers only, see
Upgrading HA Systems To StorNext 5 on page 26.
Pre-Upgrade Steps
1. It is recommended that you run and complete a StorNext backup prior to starting the upgrade. If you
have not completed a backup, you can initiate one from the StorNext GUI.
2. Make sure all store and retrieve requests have finished.
3. If you are using DDM, disable it on all the hosts by using the StorNext GUI or the fsddmconfig
command. Storage Manager requires that the MDC and DDM clients are running the same version of
StorNext 5 and StorNext FX 5 Upgrade Guide
18
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
Upgrading non-HA Linux MDCs to StorNext 5
the software. Refer to the section on Distributed Data Mover in the StorNext 5 User’s Guide for
information on DDM.
Upgrade the MDC
1. Mount the StorNext installation DVD and change to the DVD root directory.
Note: When you mount a DVD in a Red Hat 5 or 6 system, DVDs are mounted by default with a
noexec (non-executable) option which prevents you from proceeding with the installation.
For Red Hat users only, before proceeding you must remount the DVD by typing mount -o remount, exec ...
2. List the installation directories on the DVD. At the command prompt, type:
ls -l
3. Change to the stornext_full directory.
Note: Make sure you are in the stornext_full directory and not the fs_only directory. The fs_only directory installs the StorNext File System only.
4. List the directories in the stornext_full directory. At the command prompt, type:
ls -l
5. Identify the correct installation directory for your operating system and hardware platform, and then
change to that directory.
For example, for Red Hat Linux 5 running on an x86 64-bit platform, change to the RedHat50AS_
26x86_64 directory.
6. As described in StorNext Licensing on page 8, license checks are made as part of the upgrade. Some of
these checks require the software to be running, so start it now. At the command prompt, type:
service cvfs start
7. Run the script with the -liccheck option. At the command prompt, type:
./install.stornext -liccheck
The install script runs and checks for valid licenses. If the license check fails, then contact Quantum
before continuing with the upgrade. For sample output, see The License Check Option on page 21.
8. Run the install script. At the command prompt, type:
StorNext 5 and StorNext FX 5 Upgrade Guide
19
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
Upgrading non-HA Linux MDCs to StorNext 5
./install.stornext
The installation script runs (Figure 2 below).
Figure 2: StorNext Installation Script
9. On the Upgrade Menu, type 2 and press <Enter>.
The StorNext installation script runs and displays the current progress of the upgrade.
10. When the upgrade is complete, press <Enter> to return to the Main Menu.
Note: A database schema update is applied to Storage Manager when upgrading from StorNext
4.3.x to StorNext 5. This update takes approximately one hour for every hundred million entries in
the filecomp tables.
In a non-HA environment, database schema updates will be applied during the first start of
StorNext from install.stornext following the upgrade to the new version of the StorNext
software StorNext file systems are accessible while the database schema is being updated, but
Storage Manager functionality (including stores and retrieves) will be offline.
Do NOT interrupt StorNext services while the database is being updated. Interrupting the database
schema update could result in an inconsistent database, and may require assistance from Quantum
Support to repair or restore the database.
11. To exit the installation script, type 4 and press <Enter>.
12. After running the installer, source the profile on the MDC by running this command:
. /usr/adic/.profile
Post-Upgrade Steps
If you are using the DDM feature, follow these steps:
1. Upgrade the DDM hosts to same version of StorNext as the MDC.
2. Enable the DDM host by executing the fsddmconfig command or the StorNext GUI.
StorNext 5 and StorNext FX 5 Upgrade Guide
20
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
Upgrading non-HA Linux MDCs to StorNext 5
The License Check Option
When you run the installation script with the -liccheck option, the script checks for valid licenses. Proceed
with the upgrade only if the license check is successful.
Note: Even if the license check is successful, messages about unlicensed features may display.
However, if these features are not in use, you may proceed with the upgrade.
The license check can fail for the following reasons:
l
StorNext or StorNext components are not running, which keeps the licensing status from being
determined for a feature. Therefore it is treated as non-licensed even if the license is present.
l
The capacity has been reached for a licensed feature so it is treated as non-licensed.
l
A feature is found to be in use but not licensed.
l
The maintenance license expired prior to the build date of the upgrade release.
See the sections below for sample output for a successful and a failed license check.
Successful License Check Sample Output
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
- The server license status is: Good
- The proxy license status is: Good
- The dedup license status is: Unused
- The replication license status is: Unused
- The failover license status is: Unused
- The manager license status is: Unused
- The checksum license status is: Unused
- The vaulting license status is: Unused
- The sdisk license status is: Good
- The ddm license status is: Good
- The maintenance license status is: Good
License check done.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
Failed License Check Sample Output
StorNext 5 and StorNext FX 5 Upgrade Guide
21
Chapter 4: Upgrading non-HA Linux MDCs to StorNext 5
Upgrading non-HA Linux MDCs to StorNext 5
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
- The server license status is: Good
- The proxy license status is: Good
- The dedup license status is: Good
- The replication license status is: License Missing
- The failover license status is: Unused
- The manager license status is: Over Capacity
- The checksum license status is: Unused
- The vaulting license status is: Unused
- The sdisk license status is: Good
- The ddm license status is: UNKNOWN
- The maintenance license status is: Good
--------------------------------------------------------Improperly licensed features have been detected on the
system. Please
contact Support to get licenses for the features
indicated above that are not properly licensed and are in
use.
------------------------------------------------------------- Number of improperly licensed StorNext features: 3
--- Verify the following two items before contacting
Support. If these things were not done, correct and try
again.
-> The license file is installed and up to date.
-> The software is up and running as this is needed
for some license checks.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
SSL Certificate Exception
When you log into StorNext for the first time, you might see a message warning you about a security
certificate. Refer to the Quantum Knowledge Base and search for “SSL” for a permanent workaround to this
issue.
For a temporary solution, create a certificate exception that will allow you to log into the StorNext GUI
without seeing the warning message during subsequent logins.
StorNext 5 and StorNext FX 5 Upgrade Guide
22
Chapter 5: Upgrading a Windows
Client or Non-HA Server to
StorNext 5
This chapter contains the following topics:
Upgrading a Windows Client or Non-HA Server to StorNext 5
23
Upgrading a Windows Client or Non-HA Server
to StorNext 5
This section describes how to install StorNext on Windows clients or non-HA servers. During an upgrade,
the old software is removed and the new software is installed. Your previous configuration settings remain
intact.
Note: Depending on your security settings, you must be Administrator or have Administrator
privileges/rights to install StorNext software.
For StorNext clients you do not require licenses. For StorNext MDCs you will need Maintenance, Server
and (optionally) Distributed LAN client licenses.
StorNext 5 and StorNext FX 5 Upgrade Guide
23
Chapter 5: Upgrading a Windows Client or Non-HA Server to StorNext 5
Upgrading a Windows Client or Non-HA Server to StorNext 5
Note: You can upgrade directly to StorNext 5 only from StorNext 4.3.2 and later releases; except
StorNext 4.6.x, which requires you upgrade to StorNext 4.7.0.1 before upgrading to StorNext 5.
If your MDC is using a StorNext release earlier than 4.3.2, you must first upgrade the MDC to at least
StorNext 4.3.2 and then to StorNext 5.
See the StorNext Compatibility Guide for supported upgrade versions for a given StorNext release.
1. If any StorNext file systems are currently shared, temporarily disable sharing.
2. Copy the snfs_client_Windows_x86_64.zip file (for 64-bit systems only) from the StorNext installation
DVD and place it on the system onto which you want to install it. Be sure to select the file from the fs_
only directory and not the stornext_full directory.
Note: The StorNext 32-bit Windows Client is no longer supported as a StorNext client in StorNext
5. StorNext 32-bit clients are supported with StorNext 3.2.x or later. StorNext clients at StorNext
3.1.x or earlier will not connect to the FSM and a reject message will appear in the StorNext log.
3. Unzip the file.
4. Open the unzipped folder and double-click the client software installer file. This file is named
SnfsSetup.exe.
Note: If you are not logged in with Administrator privileges, right-click the file and choose “Run as
Administrator”.
The StorNext Installation screen appears (Figure 3 below).
Figure 3: StorNext Installation Window: Upgrade/Reinstall StorNext
5. Click Upgrade/Reinstall StorNext.
The StorNext Component Selection window appears (Figure 4 on the next page).
Note: If you are upgrading the client, you will not have the Server or Install Licenses options.
StorNext 5 and StorNext FX 5 Upgrade Guide
24
Chapter 5: Upgrading a Windows Client or Non-HA Server to StorNext 5
Upgrading a Windows Client or Non-HA Server to StorNext 5
Figure 4: Component Selection
6. Select the check boxes of the components you want to include in the upgrade. Clear the check boxes of
the components you want to exclude. Click Next to proceed.
The StorNext End User License Agreement (EULA) appears.
7. Read the EULA. If you accept, select “I accept the terms in the License Agreement” and then click Next
to continue the install.
It make take several minutes for the selected components to finish being added or removed.
8. When a message informs you that the installation is finished, click OK.
9. In some cases you may be required to reboot your system. In these situations StorNext attempts to
complete the installation automatically when the system starts back up. However, some platforms, virus
checkers, etc. prohibit the automatic restart feature. If the installation is not automatically completed (i.e.,
there is no Start->All Programs->StorNext menu), restart the SnfsSetup.exe program manually and
follow the on-screen directions.
10. After the upgrade is complete, re-enable sharing on your StorNext file systems.
StorNext 5 and StorNext FX 5 Upgrade Guide
25
Chapter 6: Upgrading HA
Systems To StorNext 5
This chapter contains the following topics:
Upgrading HA Systems To StorNext 5
26
Upgrading HA Systems To StorNext 5
This section describes how to upgrade a High Availability (HA) system using primary and secondary MDC
nodes to StorNext 5.
Note: This section is not intended for single-node MDCs. If you are performing an upgrade on a single
MDC node system using RPM files, see Installing StorNext File System-Only from RPMs section in the
current StorNext Installation Guide.
Before you begin this or any other upgrade procedure, verify that you have the necessary licenses required to upgrade. If you do not have the required licenses, the upgrade may fail and you will be unable
to continue.
HA Upgrade Options
The upgrade procedure requires running commands from the command line. You should also have a solid
understanding of the HA feature in StorNext 5 and a general familiarity with the StorNext GUI.
StorNext 5 and StorNext FX 5 Upgrade Guide
26
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
Note: You should not attempt to perform this procedure unless you have carefully read the upgrade
steps and are confident you can complete the steps successfully.
Note: If you use scripts in your environment to upgrade - removing StorNext from the secondary node
first, then upgrading the primary node, they can still be used to perform the HA upgrade.
Note: If you are uncertain about your ability to perform the upgrade unassisted, please contact
Quantum Professional Services for assistance in upgrading either remotely or on site.
Note: IMPORTANT: If you decide to perform the upgrade yourself and you encounter an error during
the upgrade which is not caused by a bug in the upgrade installer, Quantum’s Profession Services
group must be consulted to come to your location to correct the issue, and you will be billed for their
services. Note that Professional Services representatives cannot travel without a purchase order, and
normal scheduling applies. Please consider this before you decide to perform an HA upgrade on your
own.
Upgrading a StorNext 4.3.2 or later HA System to
StorNext 5 HA System on the Linux OS
This procedure describes how to upgrade from a StorNext 4.3.2 or later HA system to a StorNext 5 HA
system on the Linux operating system.
As always, before you begin the upgrade make sure you have obtained the proper licenses for both nodes
for the targeted build. Refer to The License Check Option on page 21 if you are not sure you have the
necessary licenses for StorNext 5.
Pre-Upgrade Steps
1. It is recommended that you run and complete a StorNext backup prior to starting the upgrade. If you
have not completed a backup, you can initiate one from the StorNext GUI.
2. Make sure all store and retrieve requests have finished.
3. If you are using DDM, disable it on all the hosts by using the StorNext GUI or the fsddmconfig
command. Storage Manager requires that the MDC and DDM clients are running the same version of
the software. Refer to the section on Distributed Data Mover in the StorNext 5 User’s Guide for
information on DDM.
Upgrade the Secondary MDC Node
1. Login to command line of the secondary MDC node.
2. Identify the correct installation directory for your operating system and hardware platform, and then
change to that directory.
For example, for Red Hat Linux 5 running on an x86 64-bit platform, change to the RedHat50AS_
26x86_64 directory.
StorNext 5 and StorNext FX 5 Upgrade Guide
27
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
3. Upgrade StorNext on the secondary MDC node by running the following command:
install.stornext
Upgrade the Primary MDC Node
1. After the upgrade on the secondary node completes, log in to command line of the primary MDC node.
2. Upgrade StorNext on the primary MDC node by running the following command:
install.stornext
Note: Upgrading the primary MDC node triggers a failover of control to the secondary MDC node. At
this point, the secondary node becomes the new primary node. Client connectivity can be checked to
ensure that the new primary node is functioning properly.
Note: The new primary MDC node converts the old StorNext file system to the new StorNext 5 file
system in the background. During this process, it is possible the old primary MDC running the older
version of StorNext will still try to access the new StorNext 5 file system. Because the file system is
converting, the old primary StorNext log may show ICB error messages in the log.
Note: Also, while the file system is being converted, stores and retrieves will not be available until the
conversion is completed. It is possible that this process could take hours.
Note: A database schema update is applied to Storage Manager when upgrading from StorNext 4.3.x
to StorNext 5. This update takes approximately one hour for every hundred million entries in the
filecomp tables.
In a HA environment, database schema updates will be applied during the first activation of the
HaShared file system following an upgrade to the new version of the StorNext software.
StorNext file systems are accessible while the database schema is being updated, but Storage
Manager functionality (including stores and retrieves) will be offline.
Do NOT interrupt StorNext services while the database is being updated. Interrupting the database
schema update could result in an inconsistent database, and may require assistance from Quantum
Support to repair or restore the database.
Initiate a Graceful System Failover and Verification
During the upgrade of the node originally operating as the primary, the node originally operating as the
secondary node becomes the primary. After the database updates are complete and the upgrade of the
original primary completes, a failover of the node currently operating as the primary should be triggered so it
once again is operating as the secondary, and to reinstate the original primary node to operate as primary
again.During StorNext 5 or later upgrades, the Metadata ApplianceArtico Server fails over once. Because
of this single failover, the MDCArtico Server node originally operating as primary is set as the secondary
StorNext 5 and StorNext FX 5 Upgrade Guide
28
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
after the upgrade. This procedure provides the steps necessary to set the MDCArtico Server nodes back to
the system state prior to the upgrade for this scenario.
To initiate the graceful failover of an HA pair:
1. Open an SSH connection to the MDCArtico Server node operating as the primary.
2. Login to the command line of the primary MDCArtico Server node as root.
l
User: stornext
l
Password: (use the password for the stornext user account)
3. Type sudo rootsh to gain root user access.
4. Enter the password a second time.
5. Confirm that the MDCArtico Server node is operating as the primary by entering the following at the
command line:
snhamgr -m status
6. Verify the output is (bold used for clarification):
:default:primary:default:running:
7. On the MDCArtico Server node operating as the primary, initiate an HA failover to the MDCArtico
Server node operating as the secondary.
service cvfs stop
8. Wait until the secondary MDCArtico Server node becomes the primary, and leave your SSH
connection to this node open. (Time may vary.)
9. Open an SSH connection to the MDCArtico Server node now operating as the primary.
10. Login to the command line of the primary MDCArtico Server node as root and enter the following:
l
User: stornext
l
Password: (use the password assigned to the stornext user account)
11. Type sudo rootsh to gain root user access.
12. Enter the password a second time.
13. Confirm that the MDCArtico Server node is operating as the primary by entering the following at the
command line:
snhamgr -m status
StorNext 5 and StorNext FX 5 Upgrade Guide
29
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
14. Verify the output is:
:default:primary:default:stopped:
15. From the SSH connection to the MDCArtico Server node now operating as the secondary, enter the
following:
service cvfs start
16. Confirm that the MDCArtico Server node is operating as the secondary by entering the following at the
command line:
snhamgr -m status
17. Verify the output is:
:default:running:default:primary:
18. Repeat if desired to fail over to the original system operating as the primary.
19. Verify that all clients have full access.
20. Test access to all file systems.
Post-Upgrade Steps
If you are using the DDM feature, follow these steps:
1. Upgrade the DDM hosts to same version of StorNext as the MDC.
2. Enble the DDM host using the fsddmconfig command or the StorNext GUI.
Upgrading a Windows 4.3.x or later HA System to 5 HA
To upgrade a Windows HA server to the latest version of StorNext:
1. On the secondary MDC, navigate to Start Menu -> All Programs -> StorNext File System and click
"Services Stop and Remove".
StorNext 5 and StorNext FX 5 Upgrade Guide
30
Chapter 6: Upgrading HA Systems To StorNext 5
Upgrading HA Systems To StorNext 5
On the secondary MDC, navigate to Start Menu > Programs > StorNext File System > Stop and Remove to stop the File System Managers (FSMs).
2. Upgrade the secondary MDC to the new version of StorNext.
3. Click Services > Start to start the FSMs.
4. From the command line, type the following for all the file systems to fail over the FSMs.
cvadmin fail <fs_name>
5. Now the upgraded MDC should now be the primary MDC.
6. Repeat above steps 1-3 on the other (now secondary) MDC.
7. You can initiate a failover of the MDCs to verify HA is correctly failing over if desired.
StorNext 5 and StorNext FX 5 Upgrade Guide
31
Chapter 7: Upgrading HA
Systems To StorNext 5 with .RPM
Files
This chapter contains the following topics:
Upgrading HA Systems To StorNext 5 with .RPM Files
32
Upgrading HA Systems To StorNext 5 with
.RPM Files
This section describes how to upgrade to a StorNext 5 High Availability (HA) system with primary and
secondary MDC nodes using RPM files.
Note: This section is not intended for single-node MDCs. If you are performing an upgrade on a single
MDC node system using RPM files, see Installing StorNext File System-Only from RPMs in the current
StorNext Installation Guide.
Steps are run on both the primary and secondary nodes, and indicated accordingly.
Upgrading a 4.1 or later HA System to 5 using RPM files
You can upgrade directly from StorNext 4.1 if you are using RPM files to upgrade the MDC.Acquire the
StorNext client, server and core 5 RPMs for your server OS architecture from the installation DVD, or by
downloading the tarball from the Quantum web site. For example:
StorNext 5 and StorNext FX 5 Upgrade Guide
32
Chapter 7: Upgrading HA Systems To StorNext 5 with .RPM Files
Upgrading HA Systems To StorNext 5 with .RPM Files
a. quantum_jansson-<version>.rpm
b. quantum_protobuf-<version>.rpm
c. quantum_zeromq-<version>.rpm
d. snfs-common-<version>.rpm
e. snfs-extapi-<version>.rpm
f. snfs-client-<version>.rpm
g. snupdate-<version>.rpm
Make sure you have obtained and installed the proper licenses for both nodes for the targeted build (such as
5). Refer to StorNext Licensing on page 8 for more information about license requirements.
Stop the StorNext File System processes on each client machine by running /etc/init.d/cvfs
fullstop.
On the Secondary MDC
1. Stop the StorNext services by running this command:
service cvfs fullstop
2. Upgrade the required .rpm files in the following order. Use the command rpm -Uvh before each
package. For example, rpm -Uvh quantum_jansson-<version>.rpm. The files are installed in the
directory: /usr/cvfs.
a. quantum_jansson-<version>.rpm
b. quantum_protobuf-<version>.rpm
c. quantum_zeromq-<version>.rpm
d. snfs-common-<version>.rpm
e. snfs-extapi-<version>.rpm
f. snfs-client-<version>.rpm
g. snupdate-<version>.rpm
3. Start cvfs by running this command:
service cvfs start
4. Verify that all SNFS mounts completed successfully.
On the Primary MDC
1. Stop StorNext services by running this command:
StorNext 5 and StorNext FX 5 Upgrade Guide
33
Chapter 7: Upgrading HA Systems To StorNext 5 with .RPM Files
Upgrading HA Systems To StorNext 5 with .RPM Files
service cvfs fullstop
2. Verify that the Secondary MDC is now serving the configured file systems by running this command:
cvadmin -e select
3. Upgrade the required .rpm files in the following order. Use the command rpm -Uvh before each
package. For example, rpm -Uvh quantum_jansson-<version>.rpm. The files are installed in the
directory: /usr/cvfs.
a. quantum_jansson-<version>.rpm
b. quantum_protobuf-<version>.rpm
c. quantum_zeromq-<version>.rpm
d. snfs-common-<version>.rpm
e. snfs-extapi-<version>.rpm
f. snfs-client-<version>.rpm
g. snupdate-<version>.rpm
4. Start cvfs by running this command:
service cvfs start
5. Verify that all SNFS mounts completed successfully
Back on the Secondary MDC
Test failover of the HA system by running the following command:
/usr/cvfs/bin/cvadmin -e "hamon smith"
If the previous command does not verify the SMITH failover, use the following command to verify that FSM
processes failover to the primary MDC.
/usr/cvfs/bin/cvadmin -e "fail <file system name>"
StorNext 5 and StorNext FX 5 Upgrade Guide
34
Chapter 8: Upgrading Clients To
StorNext 5
This chapter contains the following topics:
Upgrading Clients To StorNext 5
35
Upgrading Clients To StorNext 5
This section describes how to upgrade clients to StorNext 5. Refer to the instructions pertaining to your
particular operating system.
Procedures for upgrading Windows clients and servers for non-HA systems are described in Upgrading a
Windows Client or Non-HA Server to StorNext 5 on page 23.
StorNext Software Requirements
Upgrading Debian Linux, Solaris, AIX and HP-UX UNIX StorNext clients to StorNext 5 requires installing
these quantum-supplied packages:
l
zeromq
l
protobuf
These packages are used by StorNext and are bundled with the StorNext .bin file.
Note: When upgrading RedHat and SUSE Linux clients, the snupdate service installs these packages.
StorNext 5 and StorNext FX 5 Upgrade Guide
35
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
UpgradingInstalling Redhat and SUSE mover clients requires installing these additional quantum-supplied
DDM packages:
l
quantum_curl
l
quantum_openssl
l
snfs-mover
l
quantum_unixODBC
l
snltfs
Note: UpgradingInstalling these packages might require using the --force option.
StorNext FX Upgrades
If you need to upgrade StorNext FX software, follow the installation instructions for your particular platform
as described in the current version of the StorNext Installation Guide posted here (click the “Select a
StorNext Version” menu to view documents for a given StorNext release):
http://www.quantum.com/sn5docs
Upgrading Linux and Unix Clients
The snupdate service allows you to manage StorNext software packages by providing the ability to install,
upgrade, remove, and rollback StorNext software packages. The snupdate service works with RHEL
versions 5 and 6 and SUSE versions 11, AIX, Debian, HPUX and Solaris.
Packages can be applied immediately or they can be staged and updated at a later time. The snupdate
service is a boot time script that starts before cvfs. It checks to see if there are staged updates available. If an
update has been staged, the snupdate service will apply that update.
The snupdate service, located in the /etc/init.d/ directory, calls the snupdate utility
(/opt/quantum/snupdate/bin/snupdate) which performs the actions and manages the snupdate
repository (/opt/quantum/snupdate/var).
The snupdate repository consists of a set of packages. These packages are the contents of the extracted
StorNext .bin archives. The snupdate has the ability to install, update, and remove a package that is copied
into the repository. It also has the ability to rollback a package to a previous version, provided that the
package supports the ability to downgrade its version.
The snupdate utilty can stage an install, upgrade, or rollback (if the package supports rollback) by marking in
the repository the next version that the package should be updated to. The staged action is applied at a later
time by the snupdate apply command.
Multiple versions of a package can be copied into the snupdate repository. The snupdate utility will
determine which version of a package is currently installed and keep track of the previously installed version
for the purpose of rollback. It can also detect if there is a newer version in the repository for upgrades.
StorNext 5 and StorNext FX 5 Upgrade Guide
36
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
Get Help
The snupdate utiltiy supports an interactive help system. Running
/opt/quantum/snupdate/bin/snupdate help will provide a list of available snupdate commands. Table
1 below lists the available commands.
The help system syntax is:
/opt/quantum/snupdate/bin/snupdate help [COMMAND]
To get additional information on a command, type:
/opt/quantum/snupdate/bin/snupdate help import
Table 1: Snupdate Commands
Command
Description
apply
Apply a staged action.
cancel
Cancel a staged action.
clean
Delete a package from the repository.
help
Print extended help on a command.
import
Import packages into the repository.
install
Install package on the system.
remove
Remove package from the system.
rollback
Rollback package.
show
Display package and version information.
stage
Stage an upgrade.
status
Status for staged actions.
upgrade
Upgrade package on the system.
Install the snupdate Service
To install the snupdate service, complete the following:
1. Run the StorNext .bin command to extract a StorNext package. The snupdate package is bundled with
the StorNext 5 .bin file.
Note: The StorNext package will extract into /tmp/stornext directory by default. If this directory
exists, the installation will fail and you will receive an error message. You will need to identify an
alternate location into which to extract the files by entering the following command, for example:
StorNext 5 and StorNext FX 5 Upgrade Guide
37
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
# ./<archive name> -d <dir>
Note: where <archive name> is the name of the client software archive file you downloaded, and
<dir> is the directory into which you want to extract the installation files.
2. Change to the directory where you extracted the contents of the .bin file.
3. Install the snupdate service by running this command:
l
On RedHat or SuSE Linux excute:
# rpm -ivh snupdate-<version>.rpm
l
On Debian Linux execute:
# dpkg --install snupdate-<version>.deb
l
On AIX execute:
# installp -ac -d . -f snupdate-<version>.bff
l
On HPUX execute:
# swinstall -x mount_all_filesystems=false \
-s snupdate-<version>.depot \*
l
On Solaris execute:
# pkadd -d . QUANTUMsnupdate
Import a StorNext Package Into the Repository
To import a StorNext package into the snupdate repository, complete the following:
1. Import the /tmp/stornext package into the snupdate repository. Snupdate will determine the package
name and version of the package and copy the package into
/opt/quantum/snupdate/var/PACKAGE/VERSION, for example:
# /opt/quantum/snupdate/bin/snupdate import \
/tmp/stornext/
Checking for new packages in /tmp/stornext
Copying 4.3.3-32779/ to /opt/quantum/snupdate/var/snfs_client/4.3.3-32779
If you extracted the .bin file into another directory, such as /tmp/stornext5/, then import the contents of
the directory to the snupdate repository.
StorNext 5 and StorNext FX 5 Upgrade Guide
38
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
# /opt/quantum/snupdate/bin/snupdate import \
/tmp/stornext5/
Checking for new packages in /tmp/stornext5
Copying 5.0.0-38570/ to /opt/quantum/snupdate/var/snfs_client/5.0.0-38570
2. Run the show versions command to ensure the package was imported:
# /opt/quantum/snupdate/bin/snupdate show versions
package: snfs_client
version: 4.3.3-32779 (Current)
version: 5.0.0-38570
package: snfs_full
version: (none)
package: stornext_full
version: (none)
Upgrade a Package in the Repository
To immediately upgrade a package, complete the following:
1. Upgrade to the latest version of the snfs_client that is available in the
/opt/quantum/snupdate/var repository:
# /opt/quantum/snupdate/bin/snupdate upgrade snfs_client
Upgrading snfs_client package /opt/quantum/snupdate/var/snfs_client/5.0.038570...
Preparing... ######################################## snfs-common
######################################## snfs-client
########################################
CC [M] /usr/cvfs/install/linuxif_fs.o
CC [M] /usr/cvfs/install/linuxif_fs_common.o
CC [M] /usr/cvfs/install/linuxif_fsctl.o
LD [M] /usr/cvfs/install/cvfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/cvfs/install/cvfs.mod.o
LD [M] /usr/cvfs/install/cvfs.ko.unsigned
NO SIGN [M] /usr/cvfs/install/cvfs.ko
INSTALL /usr/cvfs/install/cvfs.ko
DEPMOD 2.6.32-279.el6.x86_64
2. Run the show versions command to verify the installed version. The output will show a status of
Current, as shown:
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous)
version: 5.0.0-38570 (Current)
StorNext 5 and StorNext FX 5 Upgrade Guide
39
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
Stage an Upgrade
To stage an upgrade of the package to another version, complete the following:
1. Assuming the packages have been imported as shown in the previous procedure, list the available
versions.
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Current)
version: 5.0.0-38570
2. Verify that the package update is available:
# /opt/quantum/snupdate/bin/snupdate status
Upgrade available for package: snfs_client (5.0.0-38570)
3. Stage the upgrade using the snupdate stage command
# /opt/quantum/snupdate/bin/snupdate stage upgrade snfs_client
Staging upgrade of snfs_client to version 5.0.0-38570
4. Check on the status of snfs_client package to see that it has been marked to be updated.
# /opt/quantum/snupdate/bin/snupdate status
Staged upgrade scheduled for package: snfs_client (5.0.0-38570)
You could also verify the updates by running the snupdate service command:
# service snupdate status
Staged upgrade scheduled for package: snfs_client (5.0.0-38570)
5. Verify the new update has been staged by running the show versions command:
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client package: snfs_
client
version: 4.3.3-32779 (Current)
version: 5.0.0-38570 (StagedUpgrade)
Apply a Staged Upgrade
1. Verify that a staged update is available.
# /etc/init.d/snupdate status
Staged upgrade scheduled for package: snfs_client (5.0.0-38570)
2. The cvfs service wil need to be stopped and unloaded prior to starting the snupdate service.
l
On Linux execute:
StorNext 5 and StorNext FX 5 Upgrade Guide
40
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
/usr/cvfs/bin/DSM_control fullstop
l
On Solaris execute:
/usr/cvfs/bin/cvfs fullstop
l
On AIX execute:
/etc/rc.cvfs fullstop
l
On HPUX execute:
/sbin/init.d/cvfs fullstop
3. Starting the snupdate service will cause any staged updates to be applied. The snupdate service script
checks for staged updates and applies any that are available and then exits. It runs in the foreground.
# /etc/init.d/snupdate start
Checking for new packages in /tmp/stornext
package /opt/quantum/snupdate/var/snfs_client/5.0.0-38570 is already up to date
Staged upgrade scheduled for package: snfs_client (5.0.0-38570)
Upgrading snfs_client package /opt/quantum/snupdate/var/snfs_client/5.0.038570...
Preparing... ######################################## quantum_zeromq
##################################### quantum_protobuf
#####################################
snfs-common ######################################## snfs-client
########################################
CLEAN /usr/cvfs/install/.tmp_versions
CLEAN /usr/cvfs/install/Module.symvers /usr/cvfs/install/modules.order
CC [M] /usr/cvfs/install/linuxif_fs.o
CC [M] /usr/cvfs/install/linuxif_fs_common.o
CC [M] /usr/cvfs/install/linuxif_fsctl.o
LD [M] /usr/cvfs/install/cvfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/cvfs/install/cvfs.mod.o
LD [M] /usr/cvfs/install/cvfs.ko.unsigned
NO SIGN [M] /usr/cvfs/install/cvfs.ko
INSTALL /usr/cvfs/install/cvfs.ko
DEPMOD 2.6.32-131.0.15.el6.x86_64
No staged action defined for snfs_full
No staged action defined for stornext_full
4. After running snupdate to upgrade, rollback, or apply a staged operation, the cvfs service will need to be
restarted:
l
On Linux execute:
/usr/cvfs/bin/DSM_control start
StorNext 5 and StorNext FX 5 Upgrade Guide
41
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
l
On Solaris execute:
/usr/cvfs/bin/cvfs start
l
On AIX execute:
/etc/rc.cvfs start
l
On HPUX execute:
/sbin/init.d/cvfs start
Rollback to a Previous Version
To rollback to the previously installed version, complete the following:
1. Identify the versions currently in the repository using the show versions option, for example:.
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous)
version: 5.0.0-38570 (Current)
2. Stage a rollback to a previously installed version by using the stage rollback option. You can also use
a specific version to rollback to a different version instead of the last installed version:
# /opt/quantum/snupdate/bin/snupdate stage rollback \ snfs_client 4.3.3-32779
Staging rollback of snfs_client to version 4.3.3-32779
3. Use the show versions to list the current versions of a package and the intended states.
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous,StagedRollback)
version: 5.0.0-38570 (Current)
4. Use the snupdate apply command or the service snupdate start command to make the
StorNext software update take effect.
StorNext 5 and StorNext FX 5 Upgrade Guide
42
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
# /opt/quantum/snupdate/bin/snupdate apply snfs_client
Rolling back snfs_client to /opt/quantum/snupdate/var/snfs_client/4.3.3-32779...
CLEAN /usr/cvfs/install/.tmp_versions
CLEAN /usr/cvfs/install/Module.symvers /usr/cvfs/install/modules.order
Preparing... ########################################
snfs-common ######################################## snfs-client
########################################
CC [M] /usr/cvfs/install/linuxif_fs.o
CC [M] /usr/cvfs/install/linuxif_fs_common.o
CC [M] /usr/cvfs/install/linuxif_fsctl.o
LD [M] /usr/cvfs/install/cvfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/cvfs/install/cvfs.mod.o
LD [M] /usr/cvfs/install/cvfs.ko.unsigned
NO SIGN [M] /usr/cvfs/install/cvfs.ko
INSTALL /usr/cvfs/install/cvfs.ko
DEPMOD 2.6.32-279.el6.x86_64
5. Use the show versions to show that rollback succeeded.
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Current)
version: 5.0.0-38570 (Previous)
Cancel a Staged Update
A staged update operation may be canceled using the snupdate cancel command. To cancel a staged
update, complete the following:
1. Use the snupdate show versions command to list the available versions:
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous,StagedRollback)
version: 5.0.0-38570 (Current)
2. Use the snupdate cancel command to cancel the pending staged update for a package:
# /opt/quantum/snupdate/bin/snupdate cancel snfs_client
package: snfs_client
Canceling staged rollback for package snfs_client
3. Verify that the staged update has been canceled using the show versions command:
StorNext 5 and StorNext FX 5 Upgrade Guide
43
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous)
version: 5.0.0-38570 (Current)
Cleaning Up the snupdate Repository
Use the snupdate clean command to clear up stale versions from the snupdate repository.
Complete the following:
1. List the current packages using the show versions command.
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 4.3.3-32779 (Previous)
version: 5.0.0-38570 (Current)
2. Delete the stale StorNext packages from the repository in the
/opt/quantum/snupdate/var directory using the clean command. The clean command requires
both a package name and a version:
# /opt/quantum/snupdate/bin/snupdate clean snfs_client 4.3.3-32779
Removing /opt/quantum/snupdate/var/snfs_client/4.3.3-32779 from repository
3. Verify the package has been removed from the repository using the show versions command:
# /opt/quantum/snupdate/bin/snupdate show versions snfs_client
package: snfs_client
version: 5.0.0-38570 (Current)
Upgrade Debian Linux
Follow these steps to upgrade a Debian Linux Client
1. Log on to the StorNext or StorNext FX client system as root.
2. Change to the directory where the client software archive file you downloaded is located.
3. Unbundle the snfs_client_Debian60_26x86_64.bin package.
When you are presented with the StorNext End User License Agreement (EULA), press <ENTER> to read
the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline.
After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if
you specified an alternate location).
StorNext 5 and StorNext FX 5 Upgrade Guide
44
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
Note: If the directory into which the files are being extracted does not have enough space, the
installation will fail and you will receive an error message. You will need to identify an alternate
location into which to extract the files by entering the following command:
# ./<archive name> -d <dir>
Note: where <archive name> is the name of the client software archive file you downloaded, and <dir> is
the directory into which you want to extract the installation files.
Caution: If the directory into which the files are being extracted already exists, you will receive a
warning message. If this occurs, either remove the directory and try the installation again, or change the
installation directory by entering the following command:
# ./<archive name> -d <dir>
Caution: where <archive name> is the name of the client software archive file you downloaded, and <dir>
is the directory into which you want to extract the installation files.
It is NOT recommended that you force using an existing directory (by using the -f command) because
this could lead to additional problems installing the .rpm files.
4. From the /tmp/stornext directory, install the required SNFS packages first, and then install the client
and common software pacakges:
Example:
dpkg
dpkg
dpkg
dpkg
-i
-i
-i
-i
quantum-protobuf_<version>.deb
quantum-zeromq_<version>.deb
snfs-common-<version>.deb
snfs-client-<version>.deb
5. Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC to which the StorNext
or StorNext FX client will connect.
The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file
does not exist, use a text editor to create it.
Note: The fsnameservers file needs to contain only the IP address of the MDC.
6. For StorNext FX clients ONLY, copy the .auth_secret file from the Xsan MDC to
/usr/cvfs/config/.auth_secret on the client system.
7. If this is a SAN client, check to make sure LUNs are visible. At the command prompt, type:
/usr/cvfs/bin/cvlabel -l
StorNext 5 and StorNext FX 5 Upgrade Guide
45
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
Create a mount point.
Example:
/stornext/<snfs1>
Where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system.
8. Edit the /etc/fstab to add the client mount options.
Example:
<snfs1> /stornext/snfs1 cvfs rw 0 0
Where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system.
9. Start the file system service. At the command prompt, type:
service cvfs start
Verify file systems are mounted.
Upgrading Sun Solaris Clients
To upgrade Solaris clients, you will have to remove the old zeromq and protobuf packages using the pkgrm
command. These packages are “generic quantum packages” and can be installed or upgraded by other
Quantum products.
Caution: If you have other Quantum products that share the zeromg and protobuf packages, it is
recommend you use the newer versions. Consult the other product’s documentation on how to remove
the older versions.
Follow these steps to upgrade a Solaris client:
1. Un-mount the StorNext file system(s) and remove the driver by using this command:
/usr/cvfs/bin/cvfs fullstop
2. List installed StorNext package with this command:
pkginfo | egrep -e "ADIC|QUANTUM"
3. Remove the installed StorNext client package by using this command:
pkgrm ADICsnfs
pkgrm QUANTUMprotobuf
pkgrm snupdate
pkgrm QUANTUMzeromq
StorNext 5 and StorNext FX 5 Upgrade Guide
46
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
4. Verify StorNext client package has been removed by using this command:
pkginfo | egrep -e "ADIC|QUANTUM"
No results should be returned.
5. Extract the .bin client package, for example:
./snfs_client_SunOS5100i386_64.bin
and then accept the StorNext End User License Agreement (EULA).
6. Change to the directory where the new StorNext client package is located. The default location is:
/tmp/stornext/
7. Install the required SNFS packages first, and then install the client software package. At the command
prompt, type:
pkgadd
pkgadd
pkgadd
pkgadd
-d
-d
-d
-d
.
.
.
.
snupdate
QUANTUMprotobuf
QUANTUMzeromq
ADICsnfs
8. Reboot the system.
9. Verify the StorNext file system is mounted by running the mount command.
Upgrading AIX Clients
Follow these steps to upgrade an AIX client:
1. Un-mount the StorNext file system(s) and unload the driver by using this command:
/etc/rc.cvfs fullstop
2. Make a copy of the /etc/filesystems file to preserve StorNext mount configuration information. For
example:
cp /etc/filesystems /etc/filesystems.bak
3. List installed StorNext client package by using this command:
lslpp –L | grep snfs
Only one client package should be listed.
4. Remove StorNext client package by using this command:
installp –u –g <file name listed in previous step>
StorNext 5 and StorNext FX 5 Upgrade Guide
47
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
For example:
installp –ug snfs_5.0b21125.rte
Note: As part of this step, mount configuration information for StorNext file systems is removed
from /etc/filesystems.
5. Verify under the Summary section of the removal that the event header displays “de-installed” and the
results header displays “success.”
6. Use the following command to list installed StorNext client package again to verify all packages has
been removed:
lslpp –L | grep snfs
No client package should be listed.
7. Extract the .bin client package i.e. (./snfs_client_AIX61_powerpc_64.bin) and agree to the StorNext
End User License Agreement (EULA).
8. Change to the directory where the new StorNext client package is located.
9. Install the new StorNext client package as described in the StorNext installation Guide by using this
command:
installp –ac –d . all
10. Edit /etc/filesystems and re-add mount configuration information for StorNext file systems. Consult
the previously saved file /etc/filesystems.bak.
11. Start the new StorNext client software by using this command:
/etc/rc.cvfs start
Alternatively, you can reboot the system.
12. Verify the StorNext file system is mounted by using the mount command.
Upgrading HP-UX Clients
Follow these steps to upgrade an HP-UX client:
1. Unmount StorNext file systems by using this command:
umount /stornext/snfs1
2. Stop all StorNext services by using this command:
/sbin/init.d/cvfs fullstop
3. Verify all services are stopped.
StorNext 5 and StorNext FX 5 Upgrade Guide
48
Chapter 8: Upgrading Clients To StorNext 5
Upgrading Clients To StorNext 5
4. Uninstall the existing StorNext installed build by using this command:
swremove -x mount_all_filesystems=false snfsclient
swremove -x mount_all_filesystems=false quantum_protobuf
swremove -x mount_all_filesystems=false quantum_zeromq
5. Extract the .bin client package, for example:
./snfs_client_HPUX1131_ia64.bin
and then accept the StorNext End User License Agreement (EULA).
6. Change to the directory where the new StorNext client package is located.
7. Install the required RPM packages and the new build by using this command:
swinstall -s /tmp/stornext/quantum_zeromq-<version>.depot \
-x mount_all_filesystems=false \*
swinstall -s /tmp/stornext/quantum_protobuf-<version>.depot \
-x mount_all_filesystems=false \*
swinstall -s /tmp/stornext/snfs-client_hpux_<version>.depot \
-x mount_all_filesystems=false \*
8. Verify that StorNext services are running. If necessary, start services by using this command:
/sbin/init.d/cvfs start
9. If not already mounted, mount the StorNext file systems on the HP-UX client.
StorNext 5 and StorNext FX 5 Upgrade Guide
49
Chapter 9: Upgrading of SNSM
Object Storage Configuration to
StorNext 5 release 5.1 (or later)
This chapter contains the following topics:
Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
50
Upgrading of SNSM Object Storage
Configuration to StorNext 5 release 5.1 (or
later)
If you have existing systems configured with Object Storage, upon upgrading to StorNext 5 release 5.1 (or
later), you will notice the following changes to your configuration:
l Appliance Component
The Provider will be set to LATTUS.
l Controller Component
The HTTP|HTTPS Protocol and ioport are no longer an attribute of the Controller. These attributes
are now owned by the iopath component. During upgrade, these parameters are no longer set for
the Controller Component.
l Iopath Component
StorNext 5 and StorNext FX 5 Upgrade Guide
50
Chapter 9: Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
The HTTP|HTTPS Protocol, AXR|S3 Object Storage Service API, PATH|VHOST are attributes of
the iopath. The hostaddress is now defined as a TCP connection endpoint. This parameter now
includes an IP address (or a DNS name) and a TCP/IP port number (for example,
123.123.123.123:8080). The port number is Optional.
During an upgrade, the following changes are made:
l
An iopath is created for each defined ioport.
l
The alias of the iopath is modified.
l
The Object Storage Service API is set to AXR.
l
The path style is set to PATH.
l Namespace Component
The namespace component now contains AXR or S3. During an upgrade, this parameter is set to
AXR.
l DDM Device Component
The DDM device configuration are also changed to reflect the new iopath configuration.
Figure 5: Example of an Object Storage configuration before a StorNext 5 release 5.1 upgrade
Figure 6: Example of a DDM Object Storage device configuration before a StorNext 5 release 5.1 upgrade
StorNext 5 and StorNext FX 5 Upgrade Guide
51
Chapter 9: Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Figure 7: Example of an Object Storage configuration after a StorNext 5 release 5.1 upgrade
Figure 8: Example of a DDM Object Storage device configuration after a StorNext 5 release 5.1 upgrade
StorNext 5 and StorNext FX 5 Upgrade Guide
52
Chapter 9: Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Upgrading of SNSM Object Storage Configuration to StorNext 5 release 5.1 (or later)
Converting an AXR Namespace to an S3 Bucket
With Lattus 3.5.1, it is possible to convert AXR namespaces to S3 buckets and make them accessible via the
S3 interface.
StorNext 5 release 5.2 provides the capability to convert the media type from AXR to S3.
To convert one or more AXR namespaces to S3 buckets, follow the procedure in the section titled
Converting an AXR Namespace to an S3 Bucket located within the StorNext 5 User’s Guide which is
available on-line at http://www.quantum.com/sn5docs.
StorNext 5 and StorNext FX 5 Upgrade Guide
53
Chapter 10: Upgrading Firmware
This chapter contains the following topics:
Upgrading Firmware
54
Upgrading Firmware
For instructions on upgrading your firmware, refer to the current Release Notes for your particular
appliance:
l
For Xcellis, see http://www.quantum.com/xcelliswfddocs.
l
For Artico, see http://www.quantum.com/articodocs.
l
l
For M660, M440, M330 Metadata Appliance and Pro Foundation, see
http://www.quantum.com/snmdcdocs.
For G300 Gateway Appliance, see http://www.quantum.com/sngatewaydocs.
StorNext 5 and StorNext FX 5 Upgrade Guide
54
Chapter 11: Compression and
Encryption Usage Report
This chapter contains the following topics:
Compression and Encryption Usage Report
55
Compression and Encryption Usage Report
Beginning with StorNext 5 release 5.3, with compression and encryption for Q-Cloud devices, you can
request to view compression and encryption usage information. The compression and encryption usage
information is maintained in two new tables:
l
filecomp_obj
l
classobj_info
The fsobjinfo Command
Execute the command fsobjinfo to generate the compression and encryption usage report. The
command fsobjinfo produces a summary usage report for object store media. Object store usage is
summarized based on object store media ID and policy class ID. Reported usage can be limited to the
optionally specified set of policy class IDs or object store media IDs.
In order to generate accurate reports, existing Q-Cloud Archive usage must be accounted for. The usage
information in the filecomp table must be populated in the filecomp_obj and classobj_info tables. The
command qcloud_migrate.pl provides the capability; execute the command qcloud_migrate.pl after
you upgrade your system to StorNext 5 release 5.3.
The full path of the command is:
/usr/adic/TSM/util/install/qcloud_migrate.pl
StorNext 5 and StorNext FX 5 Upgrade Guide
55
Chapter 11: Compression and Encryption Usage Report
Compression and Encryption Usage Report
Note: Your system will operate normally without execution of the qcloud_migrate.pl command.
Considerations for the qcloud_migrate.pl Command
l
You can execute the command anytime after an upgrade to StorNext 5 release 5.3.
l
Execute the command qcloud_migrate.pl only once.
l
l
The compression and encryption usage report may not be accurate if your system contains existing QCloud Archive devices.
If your system does not contain existing Q-Cloud Archive devices, do not execute the command
qcloud_migrate.pl.
StorNext 5 and StorNext FX 5 Upgrade Guide
56
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising