Upgrading SNFS on Linux and Unix................................................................9
Upgrading SNFS on Windows.........................................................................10
Contacting Quantum17
Document 6-01620-10 Rev A, June 20091
StorNext 3.5.1 Upgrade Guide
Document 6-01620-10 Rev A
June 2009
Made in the 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.
US Patent No: 5,990,810 applies. Other Patents pending in the US and/or other countries.
StorNext is either a trademark or registered trademark of Quantum Corporation in the US and/or other countries.
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
ADIC, Quantum, DLT, DLTtape, the Quantum logo, and the DLTtape logo are all registered trademarks of Quantum Corporation. SDLT and
Super DLTtape are trademarks of Quantum Corporation.
Other trademarks may be mentioned herein which belong to other companies.
2
StorNext 3.5.1 Upgrade Guide
Document 6-01620-10 Rev A
June 2009
Introduction0
This document provides information about upgrading to StorNext 3.5.1 from a
previous version. Instructions are provided for metadata controllers (MDCs)
running both StorNext File System (SNFS) and StorNext Storage Manager
(SNSM), as well as for MDCs running SNFS only.
Note:Quantum supports upgrades only from the previous two
major releases of StorNext. For example, you can upgrade to
StorNext 3.5.1 from version 3.1 or 3.0, but not from version 2.8
or earlier.
For upgrade procedures, or to learn how to contact Quantum for assistance, see
the following sections:
•Getting Ready to Upgrade on page 3
•Running the Pre-Installation Script on page 4
•Upgrading to StorNext 3.5.1 (SNFS and SNSM) on page 7
•Upgrading to StorNext 3.5.1 (SNFS Only) on page 8
•Contacting Quantum on page 17
Getting Ready to Upgrade0
This section includes important information about upgrading to StorNext 3.5.1.
Review the following sections before upgrading:
•Upgrade Guidelines
•Converting a Metadata Controller Running IRIX
•Upgrading HA Systems
•Upgrading the Client Software
Upgrade Guidelines0Before upgrading StorNext, review the following upgrade guidelines:
•Before upgrading, make sure there is no I/O activity. On the StorNext home
page, the number of store candidates should be 0. 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.
Introduction3
StorNext 3.5.1 Upgrade Guide
Document 6-01620-10 Rev A
June 2009
•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.
•Because the metadata dump format changed starting in StorNext 3.0, a
metadata dump is automatically performed during the upgrade process.
Depending on the size of the file system, this can extend the time required to
complete the upgrade.
•After upgrading, your StorNext license remains valid. You do not need to
request a new licence if the system ID does not change.
Converting a Metadata
Controller Running IRIX
Upgrading HA Systems 0Upgrades for MDCs running in a High Availability (HA) Failover environment
Upgrading the Client
Software
Starting with release 3.0.2, StorNext does not support metadata controllers
running the SGI IRIX operating system. To upgrade to StorNext 3.5.1 from a
0
release earlier than 3.0.2, MDCs running IRIX must be converted to a supported
operating system. This conversion must be performed by Quantum Professional
Services. For more information, or to schedule an IRIX conversion, contact the
Quantum Technical Assistance Center (see
must be performed by Quantum Professional Services. If your system is running
with failover enabled, contact the Quantum Technical Assistance Center (see
Contacting Quantum on page 17).
To upgrade to the StorNext 3.5.1 client software on Linux and Unix systems,
install the new client software package. There is no need to uninstall previous
0
versions of the client software. For more information about installing the client
software on Linux and Unix, see the StorNext 3.5.1 Installation Guide.
To upgrade to the StorNext 3.5.1 client software on Windows, follow the
procedure in
Upgrading SNFS on Windows on page 9.
Contacting Quantum on page 17).
Running the Pre-Installation Script0
The StorNext pre-installation script (snPreInstall) is included on the StorNext
installation CD. When you run
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 five directories to store application support information. These
directories are stored locally on the metadata controller, except for the
directory, which is stored on the managed file system.
The StorNext support directories are described in Table 1.
Running the Pre-Installation Script4
snPreInstall, you are prompted for information
Backup
StorNext 3.5.1 Upgrade Guide
Document 6-01620-10 Rev A
June 2009
Table 1 StorNext Support
Directories
Support DirectoryDescription
Database
/adic/database
Journal
/adic/database_jnl
Mapping
/adic/mapping_dir
Metadata
/adic/database_meta
Backup
/backup
Records information about where and how data files
are stored.
Records changes made to the database.
Contains index information that enables quick
searches on the file system.
Stores metadata dumps (backups of file metadata).
Contains configuration files and support data
required for disaster recovery.
Before You Begin0Before running the pre-installation script, be prepared to answer the following
questions:
•Is this an upgrade installation?
•What local file systems can be used to store support information?
•What version of StorNext will be installed?
•What is the maximum number of directories expected (in millions)?
•What is the maximum number of files expected (in millions)?
•How many copies will be stored for each file?
•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.
Running snPreInstall0To run the pre-installation script, use the StorNext installation CD.
1 Log on to the MDC as root.
2 Mount the StorNext installation CD and change to the CD root directory.
3 List the installation directories on the CD. At the command prompt, type:
ls -l
4 Identify the correct installation directory for your operating system and
hardware platform, and then change to that directory.
Running the Pre-Installation Script5
Figure 1 Pre-Installation Script
StorNext 3.5.1 Upgrade Guide
Document 6-01620-10 Rev A
June 2009
For example, for Red Hat Linux 5 running on an x86 64-bit platform, change
to the
6 Follow the onscreen instructions, and answer each question when prompted.
The script outputs results based on the information you entered.
After you enter all requested information, the pre-installation script outputs the
following results:
0
•Estimated disk space required for each support directory.
•Recommended file system location for each support directory.
Tech Tip:For optimal performance, each support directory (other than
the
Backup 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.
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.
TypeDescription
RECOMMENDThe suggested directory locations will result in
optimal system performance.
Running the Pre-Installation Script6
Loading...
+ 11 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.