Get Ready To Upgrade

Before you begin the upgrade, consider the following:

• If you are running StorNext 5.x on your system, then use the CLI command cvlabel to convert VTOC labels to EFI labels prior to upgrading to StorNext 6 (or later). Advances in disk arrays have made the 32-bit Volume Table of Contents (VTOC) disk labels obsolete. Modern disk arrays use Extensible Firmware Interface (EFI) disk labels capable of supporting physical disks that are larger than 2 TB in size. VTOC labels are not supported in StorNext 6 (or later).

• Not all StorNext releases may be upgraded to a given StorNext 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, consult the StorNext Compatibility Guide. If your system is running a StorNext release prior to the supported upgrade releases for a given StorNext 6 (and later) release, consult an earlier version of the StorNext Compatibility Guide that applies to your specific upgrade, and the dependencies for StorNext Clients in the environment.

• Firmware upgrade installation files must first be acquired from Quantum.

• If you attempt to perform a full backup operation (for example, by using the command snbackup) immediately after upgrading, the backup operation will fail.

  Note: The backup operation fails due to the metadata archive build process, and will not succeed until the metadata archive build is complete. The amount of time required for the metadata archive build to complete depends on the size of the file system (for example, the number of files and directories); however, other file system actions are allowed (for example, adding new files, modifying files, and so on).

  Run the following command to check the status of the metadata archive build process:

  /usr/adic/DSM/bin/cvadmin -F <file_system_name> -e "mdarchive status"

  When the status returns current, you can perform a full backup operation.

Before upgrading StorNext review the following upgrade guidelines:

Note: This upgrade guide documents supported upgrades to StorNext 7 (and later) 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 7 requires a minimum journal size of 64 MB. If you have file systems with journal sizes less than the 4MB minimum, you must resize their journals before upgrading to StorNext 7. 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 7, 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.

Beginning with StorNext 7.1.0, new columns were added to the StoreCandidate tables. If there are a large number of store candidates in the tables, the upgrade of TSM might require an extended amount of time. Quantum recommends you run the CLI command showc on your MDC to determine the number of store candidates. If your MDC contains more than 1,000 store candidates, Quantum recommends you store the candidates prior to upgrading StorNext. Otherwise, the upgrade process might require an extended amount of time.

Beginning with StorNext 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.

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.

• After a successful upgrade from StorNext 6, you should move the files under /usr/adic/database/metadumps off of the file system or delete the files, as they are no longer used by StorNext 7 and might consume a significant amount of disk space.

  Note: StorNext 7 uses the directory /usr/adic/database/mdarchives to hold external copies of file system metadata.

• Prior to StorNext 7, keeping an external copy of metadata for unmanaged file systems was rarely done because the use cases were very limited. However, beginning with StorNext 7, there are several features that require or benefit when you enable Metadata Archive. These include, but are not limited to the following features:

  • FlexSync
  • StorNext File System Pooling

  • Stripe group management (sgmanage)

  • Auditing
  • snhistory
  • snrecover

  Note: If you enable Metadata Archive for non-managed file systems, additional space is consumed on the HA shared file system. The amount is approximately one gigabyte per million files.

StorNext 6 (and later) and later has the following additional disk space requirements:

• 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.

  Note: 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 metadata archives has an impact on overall StorNext file system performance. Quantum recommends that the Storage Manager database and metadata archives 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.

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

The sections below provide information about the various licenses supported in StorNext.

Beginning with StorNext 7, your system can accept each of the following license models, but only operates using one license model:

Subscription Licenses

The subscription license model applies to a new system pre-installed with StorNext 7 (or later) software, or if you convert/migrate your system from the perpetual (license.dat) license model to the StorNext 7 subscription (product key) license model. To convert/migrate your system, see Convert from a Perpetual License to a Subscription (Product Key) License.

Note: Subscription licenses are only supported on systems running StorNext 7 (and later); they are not supported on systems running StorNext 6.x (and earlier).

Information on Registering an Appliance (MDC and Product Key)

• If you did not purchase a Quantum Appliance, visit myStorNext and register your Appliance using your serial number(s). You must also validate your Product Key using the StorNext GUI (see Service > Product Key on the StorNext 7 Documentation Center).

• If you purchased a Quantum Appliance running StorNext 7, the product key is automatically installed in the factory before shipment and does not need to be installed during setup.

• If you purchased a StorNext 7 (or later) license renewal or upgrade for a previously registered StorNext 7 Appliance, no additional Product Key validation is required.

• Per the EULA, you must register your Appliance on myStorNext (https://mystornext.quantum.com/) for license reporting through myStorNext. See Register and Create an Account.

• During your appliance setup, the appliance setup user interface offers the option to automatically register the appliance with myStorNext; this option requires internet connectivity from the appliance to myStorNext.

• For sites that do not have internet connectivity, or to register the appliance later after the initial setup, visit the myStorNext (https://mystornext.quantum.com/) to create a user account and register one or more appliances.

• Sites without internet connectivity can use the StorNext user interface to export license reports and later upload to myStorNext from a location with internet connectivity.

• When you visit myStorNext, you can view all purchased MDC system serial numbers and their corresponding license usage and compliance. The myStorNext site also provides alerting capability and login notifications. See View a Licensing Report.

Contact your Quantum Sales representative to determine which subscription license type is best suited for your environment.

Note: You will automatically receive an informational alert email if your capacity for any given license has reached a threshold, or is approaching out of compliance with the authorized use. The email notification is triggered if you reach 85% of your capacity.

The table below provides information about the three subscription license types available beginning with StorNext 7.

Subscription License Type	Description
Scale-Out Data Services Node License	A Scale-Out Data Services Node License license is required and you must purchase one Node license per node. Note: A Scale-Out Data Services Node License license contains the product key. If your system is configured as a High Availability (HA) system, then your Scale-Out Data Services Node License license contains one product key per HA pair. Below are some examples of a node: Xcellis Workflow Director (XWD) Xcellis Workflow Extender (XWE) Virtual Data Mover NAS SAN Client Distributed Data Mover (DDM) FlexSync File System Pooling
File System Capacity License or Tape Capacity License(per TiB)	A File System Capacity License or Tape Capacity License license is required and you must purchase one Capacity license per metadata-controller (MDC). A File System Capacity License or Tape Capacity License license reflects a shared amount of storage allocated amongst all configured storage nodes in your environment. Below are some examples of an MDC: Xcellis Workflow Director (XWD) F-Series Fusion Series
Public and Private Cloud Capacity License (per TiB)	A Public and Private Cloud Capacity License license is optional; however, you must purchase a Public and Private Cloud Capacity License license if you plan to transfer data to archive storage (for example, an ActiveScale system or a Scalar system). A Public and Private Cloud Capacity License license reflects a shared amount of archive storage allocated amongst all configured archive storage nodes in your environment. Below are some features that require a Public and Private Cloud Capacity License license: StorNext Storage Manager FlexTier™ Private Cloud FlexTier™ Public Cloud Storage Disk (SDISK)

Perpetual Licenses

The perpetual license is supported in StorNext 7.x (and later), but was the only license model available for StorNext 6.x and earlier systems.

Note: The features below are licensed, and the licenses are enforced. If you do not have the appropriate license, you cannot use a StorNext feature.

This license model also applies if you upgrade your system to StorNext 7 (or later) software. For example, if you upgrade from StorNext 6.4 software to StorNext 7 (or later) software.

License Type	Description
Certified Disk	A Certified Disk license allows a Metadata Controller (MDC) to use a specified amount of Quantum-certified disks. For additional information, see StorNext Disk Licensing and StorNext Disk Certification Catalog (DCC).
FlexTier™ Private Cloud	A FlexTier™ Private Cloud license permits Storage Manager to store data onto a supported private cloud destination, such as Quantum P-100. Both expiring and permanent versions of this license are offered. Note: A minimum requirement of StorNext 6.0.5 (or later) is necessary in order to obtain and install a FlexTier™ Private Cloud expiring license. A minimum requirement of StorNext 6.1.0 (or later) is necessary in order to obtain and install a FlexTier™ Private Cloud permanent license. Note: FlexTier™ expiring licenses are purchased and renewed periodically. If your FlexTier™ license expires prior to being renewed, or if you exceed the amount of licensed capacity, Storage Manager does not store new files to the destination. Watch Video
FlexTier™ Public Cloud	A FlexTier™ Public Cloud license permits Storage Manager to store data onto a supported public cloud destination, such as Amazon S3 or Microsoft Azure. Both expiring and permanent versions of this license are offered. Note: A minimum requirement of StorNext 6.0.5 (or later) is necessary in order to obtain and install a FlexTier™ Public Cloud expiring license. A minimum requirement of StorNext 6.1.0 (or later) is necessary in order to obtain and install a FlexTier™ Public Cloud permanent license. Note: FlexTier™ expiring licenses are purchased and renewed periodically. If your FlexTier™ license expires prior to being renewed, or if you exceed the amount of licensed capacity, Storage Manager does not store new files to the destination. Caution: If you have installed a FlexTier™ Public Cloud expiring license and are running any release prior to StorNext 6.0.5, see Product Bulletin 100. Watch Video
LAN Client	StorNext LAN Clients use IP protocols to read and write data to the StorNext File System through Quantum appliances that can operate as a StorNext LAN Gateway. You must have a LAN Client license for each LAN Client you intend to use with StorNext (in addition to any SAN Client licenses). Note: For Quantum appliances that can operate as a StorNext LAN Gateway, LAN Clients are referred to as Gateway Clients, and are not licensed on a "per-seat" basis. See the Quantum Appliances StorNext Perpetual Licenses.
Maintenance	A Maintenance license is associated with the expiration date of your current service contract. A valid Maintenance License is required to enable StorNext software upgrades. This license is a time-based license key that expires on the same date as the maintenance contract. Each time the maintenance contract is extended, a new maintenance license key is generated. Note: License enforcement is based on the date of the software to which you are upgraded, regardless of the current date. For example, if your maintenance license key is valid between January 16th, 2017 and January 16th, 2018, you could upgrade to a software version that is released prior to the expiration date of the maintenance license (and of the associated underlying service contract) expiration date, but not to a version released after January 16th, 2018. See Quantum Appliances StorNext Perpetual Licenses for information about Maintenance Licenses on StorNext appliances.
Object Storage	The Object Storage license specifies the amount of data that StorNext Storage Manager can place onto a Quantum Lattus object store platform. The Object Storage license must be installed on supported Quantum appliances and MDC with dedicated 10GbE NIC connections in order to configure StorNext to use Object Storage as a storage destination. Prior to StorNext 5 Release 5.1, this license was called SNSM Wide Area Storage, which was first supported in StorNext 4.6. This license name was deprecated in StorNext 5 Release 5.1, and is superseded by the Object Storage license.
SAN Client	A StorNext SAN Client enables a host computer to mount a StorNext file system with direct block-level access to the disk arrays using Fibre Channel or iSCSI connections. The StorNext file system is licensed on a per-client basis. Any machine that directly mounts the file system is considered a client. If you are an Xsan customer, then you can use an unlimited number of Xsan clients when connected to a StorNext MDC.
SNSM Wide Area Storage	The StorNext Storage Manager (SNSM) for Wide Area Storage (WAS) license was used to enable Object Storage access for supported Quantum appliances and WAS-capable MDCs configured for use with Lattus/ActiveScale systems. This license is deprecated in StorNext 5 release 5.1. For systems running StorNext 5 release 5.1 or later, see the Object Storage license. The SNSM Wide Area Storage license is installed but not enabled by default as part of StorNext 4.6.x until StorNext 5 release 5.1, and from StorNext 5 release 5.1 forward the Object Storage license for supported Quantum Appliances and MDCs. A license key must be applied through the StorNext GUI in order to enable the license.
Storage Manager	StorNext Storage Manager is licensed based on the capacity of data stored to secondary tiers of storage (Tape or Storage Disk). For StorNext 5 releases 5.4 and later, a Storage Manager manager license provides full access to the base functionality of StorNext Storage Manager. Support for non-Quantum object storage on public or private clouds are licensed using the annual capacity-based subscription model (see the FlexTier™ subscription licenses). For StorNext 5 releases up to and including 5.3.x, a Storage Manager license provides full access to the data management capabilities of Storage Manager.
StorNext LAN Gateway	A StorNext LAN Gateway license is a StorNext SAN Client that allows LAN-based client connectivity to a StorNext File System.
Uncertified Disk	An Uncertified Disk license allows a Metadata Controller (MDC) to use a specified amount of non-Quantum-certified disks. For additional information, see StorNext Disk Licensing and StorNext Disk Certification Catalog (DCC).

Licenses for Features

Note: The Checksum license key is no longer required to enable Generation and Validation of checksums within a Policy. Existing checksum license keys are ignored, and new licenses do not include checksum licenses keys.

Feature License	Description
Alternate Store Location	An Alternate Store Location license is required for the automated copying of files from a main instance of StorNext to a remote instance of StorNext. For additional information, see the section "Alternate Store Location" in the StorNext User's Guide.
Distributed Data Mover (DDM)	A DDM license is required to retrieve data using additional servers besides the system functioning as a StorNext metadata controller (MDC). This license is available only for Storage Manager environments, and is required for each DDM host. Note: Each DDM host also requires one File System SAN Client license, in addition to the DDM license.
Failover (HA)	A Failover HA (High Availability) license enables automated failover from the primary server node to the secondary server node, in the event of a primary server node failure. This license is available for either File System only or Storage Manager environments. One HA license is required for each server node pair. The HA license is applied to both server nodes. In addition to the client licenses applied to each server node, a third client must be installed in is also required to ensure proper failover functionality. This client can be one that is already accessing a StorNext file system. However, this third client must be purchased separately. See the StorNext File System Client Mount Requirement.
FlexSync™	FlexSync is a licensed feature that uses advanced metadata capabilities to create local or remote replicas of an entire file system, or any portion of a file system. FlexSync solutions are easily configured using a simple, but powerful user interface, deliver sustained scalable performance, and are very resource efficient. Whether protecting files locally or across a network connection, FlexSync creates file replicas in near real time to ensure that file data is protected and easily recoverable. See the FlexSync Licensing Guidelines section available in the FlexSync Documentation Center for additional details. Watch Video
NAS	A NAS license is used to enable Network File Sharing (NFS) and Server Message Block (SMB) sharing of StorNext file systems using Quantum-supplied NFS and SMB software. Additional Resources Learn more about Xcellis Scale-out NAS: www.quantum.com/products/scale-out-storage/nas/index.aspx Watch a video featuring Quantum's Molly Presley discussing the new Xcellis Scale-out NAS appliance: www.quantum.com/nas-video For Appliance Controller configuration, see the Appliance Controller Documentation Center at www.quantum.com/accdocs.
Archive Conversion	An Archive Conversion Utility (ACU) license is required to enable the reading and migrating of a non-StorNext Storage Manager archive into StorNext. An ACU license is only available as part of a Quantum professional services project. Note: Contact your Quantum sales representative for more information about Archive Conversion Utility.
Partial File Retrieval (PFR)	A StorNext Partial File Retrieval (PFR) license enables you to quickly retrieve and use segments of large media files, rather than the entire file, based on timecode parameters. PFR licenses are not included in the license.dat file. PFR uses a different licensing and installation process, as described in the StorNext PFR 1.2 Users Guide.
Storage Disk	You must have a Storage Disk (SDISK) license to configure and use StorNext storage disks. This license enables the SDISK feature, but data written still counts toward the per TB capacity of the Storage Manager.
Vaulting	A Vault Option license allows you to move seldom-used media from a Quantum or supported third-party library to a manual archive vault, freeing room for media in the managed archives. This license is available only for Storage Manager environments. If a vault option license is purchased, any data that is stored in a vault does not apply to the Storage Manager capacity license.

Information Contained within a License File

Table 1 illustrates the type of information contained within a license file.

Table 1: Parameters and Values Found Within a License File

License Parameter	License Value
Product	server
System	Your System Name
Company	Your Company Name
Serial Number	Your Serial Number
Identifier	C201F8620
Number of Clients	1
Expiration	mm-dd-yyyy
License	AAAAA/DAAAE/AJCLJ/9S2WA/M7RA9/9NH4W/XTL7T/5ARNQ/TYYRJ/4J222/RS
Authorization String	server 1 C201F8620 1 AAAAADAAAEAJCLJ9S2WAM7RA99NH4WXTL7T5ARNQTYYRJ4J222RS <Your System Name> <Your Company Name> <Your Serial Number>

Note: The Authorization String license value includes a prefix applicable to the type of license. In the example below, it is server.

Authorization String: server 1 C201F8620 1 AAAAADAAAEAJCLJ9S2WAM7RA99NH4WXTL7T5ARNQTYYRJ4J222RS <Your System Name> <Your Company Name> <Your Serial Number>

Table 2 provides a conversion table illustrating the type of license and its equivalent prefix as shown in the Authorization String license value.

Table 2: Authorization String License Value Conversion

License Type	License Name in Authorization String
Certified Disk	disk_certified
Checksum	checksum
Distributed Data Mover (DDM)	ddm
Failover (HA)	failover
FlexSync	flexsync
FlexTier Private Cloud	flex_private_cloud
FlexTier Public Cloud	flex_public_cloud
Gateway Licensed MDC	gateway
LAN Client	proxy
Maintenance	maintenance
NAS	nas
Object Storage	object_storage
SAN Client	server
SNFS Wide Area Storage	snfs_was
SNSM Wide Area Storage	snsm_was Note: The SNSM Wide Area Storage license was deprecated in StorNext 5 release 5.1, and renamed to the Object Storage license.
Storage Disk	sdisk
Storage Manager	manager
Uncertified Disk	disk_uncertified
Vaulting	vaulting

Be aware of the following upgrade-related implications and plan accordingly:

• 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).

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
   ------------------------------------------------------------
   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.

If you are upgrading to StorNext 6 (and 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 or product key file to /usr/cvfs/update/config. Do this on both the primary and secondary nodes in an HA environment.
4. Upgrade to StorNext 6 (and later) per the applicable procedure.

Upon a successful upgrade, use the StorNext GUI to verify the license object_storage is installed.

Taking into consideration the new licensing procedures, here is a summary of the steps necessary to upgrade to 6 (and later):

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. If you purchased a Quantum Appliance running StorNext 7.x, the product key is automatically installed in the factory before shipment and does not need to be installed during setup.
3. Run the upgrade program as explained in Upgrade non-HA Linux MDCs.
4. Log in to the StorNext GUI.
5. Use the StorNext Configuration Wizard to finish configuring your system.

To upgrade to the StorNext 6 (and later) client software on Linux systems, install the new client software package. There is no need to uninstall previous versions of the client software. For more information about installing the client software on Linux, see the current StorNext Installation Guide.

The steps required to upgrade clients to StorNext 6 (and later) 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, systemctl stop cvfs, 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.

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:

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.

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 Install a StorNext File System Only Using an RPM.

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.

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:

where <installation file> is the name of the installation file, and <dir> is the directory into which you want to extract the installation files.