Quantum STORNEXT 3.1.4.1 User Manual

StorNext 3.1.4.1 Release Notes

Product StorNext® 3.1.4.1

Date June 2010

Purpose of This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Other Changes in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

StorNext End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

StorNext Upgrade Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supported Libraries and Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Minimum Firmware Levels for StorNext Drives . . . . . . . . . . . . . . . . . . . . . . . . 19

Supported System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Resolved Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

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.

StorNext utilizes the following components which are copyrighted by their respective entities:

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Operating Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contacting Quantum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 Contents

Purpose of This Release

StorNext 3.1.4.1 is an interim release which addresses previously identified issues and also resolves some critical issues such as the following:

• CR 31271 (SR 1119366): Resolved an issue that could cause data corruption with large mixed data/metadata stripe groups. For more information, refer to StorNext Product Alert 35.

• CR 31272 (SR 1119366): Corrected a condition which resulted in an endless loop when cvfsck reached the point where it writes out the bit map.

• CR 31268 (SR 1113942): Resolved a condition in which using large values for POL_STORE_RESP_ABORT_TIME caused integer overflow. For more information, refer to StorNext Product Alert 34.

• CR 31269 (SR 1113942): File retrieval on SDISK has been enhanced to eliminate errors which prevented retrieving from either copy. For more information, refer to StorNext Product Alert 34.

• CR 31270 (SR 1119366): Corrected an issue in which "fsrmcopy -c ..." failed if the SDISK file was missing.

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

This document also describes supported platforms and system components, as well as currently known issues, issues that were resolved for this release, and known limitations.

Visit www.quantum.com/ServiceandSupport updates for StorNext.

Other Changes in This Release

The delivery mechanism for client software has changed for release 3.1.4.1. Client software for all operating systems is now contained on one disk labeled “Client Software and Product Documentation.” (Formerly, client software was distributed on the software disks for all operating systems.)

As a result of this change, you must now insert the client software disk, copy the client software from the disk, and then install or upgrade the client packages as described in the

In addition, client software is no longer distributed in compressed format (such as tar.gz files). Instead, the client software disk contains executable files which, when launched, extract the client software for the selected platform to the location /tmp/stornext where you can install the package. Windows client packages have not changed, and are still in .zip format.

StorNext 3.1.4.1 Installation Guide

for additional information and

For more information and specific installation instructions, see the

3.1.4.1 Installation Guide

Purpose of This Release 3

StorNext

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

StorNext End User License Agreement

Please read the following StorNext End User License Agreement (EULA). You must read and accept the EULA before you install StorNext.

Quantum Corporation

StorNext End User License Agreement

This License defines the terms and conditions of the license between Quantum Corporation (QUANTUM) and Licensee for use of QUANTUM's Software and Documentation. Any Software or Documentation provided to Licensee by QUANTUM will be subject to the terms and conditions of this License and by downloading, installing or using the Software, Licensee signifies its agreement with this license. If Licensee does not agree to all of the terms of this License, then Licensee must not download, install, or use the Software or Documentation.

1. Definitions:

a “Documentation” means the published documentation accompanying the

Products or available online at QUANTUM’s website, (as applicable) and any Updates thereto, in any form or media provided.

b “Hardware” means the equipment on to which the Software and Open Source

Software is pre-installed or on which it may be installed by Licensee.

c “Open Source Software” means those third party software componen ts identifi ed

as such in the Documentation or in the “About”, “Readme” or similar files in the software, which are required to be licensed under separate terms and conditions by the supplier of such Open Source Software (“ which are delivered as part of the Products and any updates thereto. To obtain a copy of the source code for the Open Source Software, please contact QUANTUM. A copy of the applicable Open Source License is provided with the Open Source Software, in the Documentation, or via the following link on the QUANTUM website:

d “Products” means the Software, Hardware, Open Source Software,

Documentation and maintenance licensed or purchased by Licensee/end-user.

e “Software” means the current version of QUANTUM proprietary software

program(s) accompanying this license, in object code form only, and any updates thereto. Software does not include Open Source Software.

2. Software License.

a License. In consideration of Licensee's payment of the License fees and subject

to the terms of this License, QUANTUM grants to Licensee a personal, nonexclusive, non-transferable license to use the Software and Documentation. A separate license is required for use of each Software program on each of Licensee's computers. The Software will be installed initially on Licensee's Designated Computer. Licensee may thereafter transfer the Software to another one of its computers of the same machine architecture, provided that the Software is installed on one (1) Designated Computer at a time. Licensee acknowledges that Open Source Software is licensed separately pursuant to the applicable Open Source License. Licensee’s use of any Open Source Software shall be subject to and Licensee agrees to comply with the applicable restrictions and other terms and conditions of the applicable Open Source License.

www.quantum.com/OpenSource.

Open Source License”) and

4 StorNext End User License Agreement

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

b Use. Licensee is authorized hereby to use the Software on one computer only

(Designated Computer), or on backup equipment if the Designated Computer is inoperative until such time as the Designated Computer is restored to operation. This grant is specifically limited to use by the Licensee for normal, customary internal data processing, and specifically excludes Licensee's time-sharing or the rental of the Software or use of the Software in the development or marketing of a competitive or compatible product. No right to use, print, copy or display the Software or Documentation, in whole or in part, is granted hereby except as expressly provided in this License.

c Copying. Licensee may make one (1) copy of the Software in a non-printed,

machine-readable form for archival and backup purposes only, and copy the Documentation as needed for internal use only of licensed Software. In order to protect QUANTUM's trade secret and copyrights in the Software and Documentation, Licensee agrees to reproduce and incorporate QUANTUM's trade secret or copyright notice in any copy or partial copy, and will maintain appropriate records of the location of such copy.

d US Government Rights. If the Licensee is the United States government,

Licensee understands and agrees that the Software and Documentation are provided as "Commercial Items" as defined at 48 CFR 2.101 and are being licensed to U.S. Government end users consistent with 48 CFR 12.212 and DFAR Section 227.7202, as applicable.

3. Software Ownership and Protection

a Title to Software. The Software, Documentation, and all copies thereof are

proprietary to QUANTUM and title thereto remains in QUANTUM. All applicable rights to patents, copyrights, trademarks, trade secrets or other proprietary rights in the Software and Documentation and any modifications made at Licensee's request are and will remain in QUANTUM.

b Restrictions. Licensee will not itself or permit others to:

i. sell, sublicense, transfer, publish, disclose, display, provide access via a

network or otherwise make available the Software or Documentation or any copy thereof to others;

ii. remove, obscure, or alter any copyright, trade secret, trademark, patent or

other proprietary rights notice affixed to or displayed on the Software or Documentation;

iii. modify, merge with other programs or translate any portion of the Software

or Documentation into any other assembly or language; and

iv. reverse-assemble, reverse-compile or attempt to derive a source code

equivalent of the Software provided that if you need information in order to assist in debugging a modified Open Source Software library, contact Quantum for assistance.

c Protections. Licensee agrees to secure and protect the Software, the

Documentation, and copies thereof in a manner consistent with QUANTUM's rights therein and to take appropriate action to satisfy its obligations in this Agreement by instruction or agreement with its employees, agents, subcontractors or others who are permitted access to the Software and Documentation. All programs or copies developed by or for Licensee in violation of this License, including translations, compilations, partial copies and updates, are owned by QUANTUM.

StorNext End User License Agreement 5

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

d Responsibility. Licensee has sole responsibility for use of the Products and any

information entered, used, or stored thereon, including responsibility for protection of data from modification, destruction, or disclosure, and for the accuracy and integrity of the data. QUANTUM assumes no responsibility for Licensee's negligence or failure to protect its data.

4. Warranty and Warranty Servicing.

a Warranty. QUANTUM warrants that for a period of 90 days from installation the

Software will conform to all substantial operational features in QUANTUM's current published specifications and will be free of material defects which substantially affect performance of the Software. QUANTUM does not warrant that the Software will meet the Licensee’s requirements or that the operation of the Software will be uninterrupted or error free. The Licensee must notify QUANTUM in writing, within 90 days after installation of the Software of Licensee’s claim of any defect. If QUANTUM determines that the Software is defective, QUANTUM’s sole obligation is for QUANTUM, at its option, to correct, any defect in the Software or to accept the return of the Software. Where Software is returned for claims made during the warranty period, Licensee will receive a refund for the Software. This warranty is made void if the Licensee or any third party makes any modifications to the Software. QUANTUM is not responsible for corrections necessitated by difficulties or defects traceable to Licensee's errors or system changes QUANTUM will have no obligation for the correction of errors that are due to a breach by Licensee of the terms of the Agreement, or that cannot be remedied due to the way Hardware on which the Software or Open Source Software is operated if such Hardware does not meet the minimum systems requirements specified in the Documentation, or as a result of any modifications to the Software or Open Source Software made by Licensee.

b Compatibility. QUANTUM does not warrant that the Software is compatible

with the current releases of all operating systems, nor that the Software will be made compatible with new releases of operating systems within a specified amount of time, or at all. At Licensee's request, QUANTUM will notify Licensee of the version level of the operating system with which the Software is intended to be compatible.

c Warranty Disclaimer. EXCEPT FOR THE EXPRESS LIMITED WARRANTY

STATED ABOVE, THE SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS” AND QUANTUM MAKES NO WARRANTIES, EXPRESS OR IMPLIED, FOR THE SOFTWARE OR DOCUMENTATION, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

5.Term and Termination. This License commences on the Effective Date and will

continue uninterrupted unless Licensee fails to comply with any conditions of this License. If Licensee breaches, QUANTUM may, after allowing Licensee a reasonable time to cure its default, terminate this License upon written notice to the Licensee. Within 30 days after termination of this License, Licensee will certify, in writing, to QUANTUM, that Licensee has discontinued the use of all Software and returned to QUANTUM the original and all copies of the Software and Documentation in any form maintained by Licensee.

6 StorNext End User License Agreement

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

6.DISCLAIMER AND LIMITATION OF LIABILITY. THE LICENSEE HAS THE

SOLE RESPONSIBILITY FOR THE ADEQUATE PROTECTION AND BACK-UP OF ITS DATA USED IN CONNECTION WITH THE PRODUCTS. IN NO EVENT WILL QUANTUM BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, RERU N TI ME, INACCURA TE INPUT OR WORK DELAYS, OR ANY PERSONAL OR PROPERTY DAMAGE ARISING OUT OF OR IN CONNECTION WITH THIS LICENSE OR THE USE, PERFORMANCE OR NON-PERFORMANCE OF THE PRODUCTS, WHETHER IN ACTION, IN CONTRACT, OR TORT INCLUDING NEGLIGENCE, EVEN IF QUANTUM KNEW , SHOULD HAVE KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. QUANTUM's LIABILITY FOR DAMAGES HEREUNDER WILL IN NO EVENT EXCEED THE AMOUNT OF FEES PAID BY LICENSEE UNDER THIS LICENSE.

7. General.

a No Assignment or Modification. This License is not assignable. None of the

Software or Documentation may be sublicensed, assigned, or transferred to any other party without QUANTUM’s prior written consent. Any effort contradictory with this is null and void. This License can only be modified by a written agreement executed by the parties.

b Governing Law and Venue. The laws of the state of Washington will govern this

license. All litigation between the parties, including all applications for injunctive relief, must be conducted before a court of competent jurisdiction in King County, Washington, USA and both parties consent to personal jurisdiction of such court. If any of the provisions of this License are held to be invalid under any applicable statute or law, they are, to that extent, deemed omitted.

c Entirety. The laws of the state of Washington will govern this license. All

litigation between the parties, including all applications for injunctive relief, must be conducted before a court of competent jurisdiction in King County, W ashington, USA and both parties consent to personal jurisdiction of such court. If any of the provisions of this License are held to be invalid under any applicable statute or law, they are, to that extent, deemed omitted.

StorNext Upgrade Recommendations

Whenever possible, StorNext systems should run the latest StorNext-supported operating system service pack or update level.

For the 3.1.4.1 release there are no additional upgrade recommendations.

StorNext Upgrade Recommendations 7

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Configuration Requirements

Before installing StorNext 3.1.4.1, note the following configuration requirements:

• In cases where gigabit networking hardware is used and maximum StorNext performance is required, a separate, dedicated switched Ethernet LAN is recommended for the StorNext metadata network. If maximum StorNext performance is not required, shared gigabit networking is acceptable.

• A separate, dedicated switched Ethernet LAN is mandatory for the metadata network if 100 Mbit/s or slower networking hardware is used.

• StorNext does not support file system metadata on the same network as iSCSI, NFS, CIFS, or VLAN data when 100 Mbit/s or slower networking hardware is used.

• The operating system on the metadata controller must always be run in U.S. English.

• For Windows systems (server and client), the operating system must always be run in U.S. English.

Caution: If a Library used by StorNext Storage Manager is connected via a

fibre switch, zone the switch to allow only the system(s) running SNSM to have access to the library. This is necessary to ensure that a “rogue” system does not impact the library and cause data loss or corruption. For more information, see StorNext Product Alert 16 Rev B.

This section contains the following configuration requirement topics:

• Library Requirements

• Disk Requirements

• Disk Naming Requirements

• SAN Disks on Windows Server 2008

Library Requirements The following libraries require special configurations to run StorNext.

DAS and Scalar DLC Network-Attached Libraries

Prior to launching the StorNext Configuration Wizard, DAS, and Scalar DLC network-attached libraries must have the DAS client already installed on the appropriate host control computer.

DAS Attached Libraries

For DAS attached libraries, refer to “Installation and Configuration” and “DAS Configuration File Description” in the

Guide

. The client name is either the default StorNext server host name or the

name selected by the administrator.

8 Configuration Requirements

DAS Installation and Administration

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

StorNext can support LTO-3 WORM media in DAS connected libraries, but WORM media cannot be mixed with other LTO media types in one logical library.

To use LTO-3 WORM media in a logical library, before configuring the library in StorNext, set the environmental variable XDI_DAS_MAP_LTO_TO_LTOW in the /usr/adic/MSM/config/envvar.config file to the name of the library. The library name must match the name given to the library when configuring it with StorNext. If defining multiple libraries with this environmental variable, separate them with a space. After setting the environmental variable, restart StorNext Storage Manager (SNSM).

Note: SDLC software may not correctly recognize LTO-3 WORM media in the

library and instead set it to “unknown media type.” In this case you must manually change the media type to “LTO3” using the SDLC GUI.

Scalar DLC Attached Libraries

For Scalar 10K and Scalar 1000 DLC attached libraries, refer to “Installation and Configuration” and “Client Component Installation” in the

Library Controller Reference Manual

(6-00658-04).

Scalar Distributed

The DAS client should be installed during the installation of the Scalar DLC attached libraries. Use this procedure to install the DAS client.

1 Select Clients > Create DAS Client.

The client name is either the default StorNext server host name or the name selected by the administrator.

2 When the DAS client is configured in Scalar DLC, select Aliasing.

3 Select sony_ait as the Media aliasing. 4 The default value is 8mm.

5 Verify that Element Type has AIT drive selected.

6 Click Change to execute the changes.

ACSLS Attached Libraries

Due to limitations in the STK ACSLS interface, StorNext supports only single ACS configurations (ACS 0 only).

Scalar i500 (Firmware Requirements)

For Scalar i500 libraries that do not have a blade installed, the library and drives must meet the following minimum firmware requirements. (These requirements apply

only

to Scalar i500 libraries that do not have a blade installed.)

• Scalar i500 minimum firmware level: 420GS.GS00600

• HP LTO-4 Fibre/SAS tape device minimum firmware level: H35Z

Caution: If you do not meet the minimum firmware requirements, you

might be unable to add a library to the Scalar i500 using the StorNext Configuration Wizard.

Configuration Requirements 9

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Disk Requirements Disk devices must support, at minimum, the mandatory SCSI commands for

block devices as defined by the SCSI Primary Commands-3 standard (SPC-3) and the SCSI Block Commands-2 (SBC-2) standard.

To ensure disk reliability, Quantum recommends that disk devices meet the requirements specified by Windows Hardware Quality Labs (WHQL) testing. However, there is no need to replace non-WHQL certified devices that have been used successfully with StorNext.

Disk devices must be configured with 512-byte or 4096-byte sectors, and the underlying operating system must support the device at the given sector size. StorNext customers that have arrays configured with 4096-byte sectors can use only Windows, Linux and IRIX clients. Customers with 512-byte arrays can use clients for any valid StorNext operating system (i.e., Windows, Linux, or UNIX).

In some cases, non-conforming disk devices can be identified by examining the output of cvlabel –vvvl. For example:

/dev/rdsk/c1d0p0: Cannot get the disk physical info.

If you receive this message, contact your disk vendors to determine whether the disk has the proper level of SCSI support.

Disk Naming Requirements

SAN Disks on Windows Server 2008

When naming disks, names should be unique across all SANs. If a client connects to more that one SAN, a conflict will arise if the client sees two disks with the same name.

SAN policy has been introduced in Windows Server 2008 to protect shared disks accessed by multiple servers. The first time the server sees the disk it will be offline, so StorNext is prevented from using or labeling the disk.

To bring the disks online, use the POLICY=OnlineAll setting. If this doesn’t set the disks online after a reboot, you may need to go to Windows Disk Management and set each disk online.

Follow these steps to set all disks online:

1 From the command prompt, type DISKPART

2 Typ e SAN to view the current SAN policy of the disks.

3 To set all the disks online, type SAN POLICY=onlineall.

4 After being brought online once, the disks should stay online after

rebooting.

5 If the disks appear as “Not Initialized” in Windows Disk Management after a

reboot, this indicates the disks are ready for use.

If the disks still appear as offline in Disk Management after rebooting, you must set each disk online by right-clicking the disk and selecting Online. This should always leave the SAN disks online after reboot.

Note: NOTE: If the disks are shared among servers, above steps may lead to

data corruption. Users are encouraged to use the proper SAN policy to protect data

10 Configuration Requirements

+ 22 hidden pages