English dropdown-ico

Quantum 2.4.1 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Quantum 2.4.1, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Quantum 2.4.1 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Quantum 2.4.1. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Quantum 2.4.1 should contain:
- informations concerning technical data of Quantum 2.4.1
- name of the manufacturer and a year of construction of the Quantum 2.4.1 item
- rules of operation, control and maintenance of the Quantum 2.4.1 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Quantum 2.4.1 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Quantum 2.4.1, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Quantum service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Quantum 2.4.1.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Quantum 2.4.1 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    Release Notes 6-00431-11 Rev A © Septembe r 2004, AD IC ® A DIC and Stor Next are register ed trademarks of Advanced Digit al Information Corporatio n. All other p roduct, company, o r service names m entioned her ein are the pr operty of th eir respecti ve owners. StorNext Management Suite 2.4.1 SNMS Server Operating Syst ems: SGI IRIX 6.5.19f, [...]

  • Page 2

    2 September 2 004, ADIC Contents Purpose of this Release This release contains information that should be used by client sites to utilize the latest releases of SNMS 2.4.1 and StorN ext FS. New features and functionality for SNM S 2.4.1 include: • Support for the following platforms: • Red Hat Ente rprise Linux Ad vanced Server 3.0 • SGI IRIX[...]

  • Page 3

    September 2004, ADIC 3 • Support for HP MSL tape library • Support for HP EVA 3000 Disk A r ray with HP SecurePath failover • Support for HP MSA 1000 Disk Arra y with HP SecurePath failover • Support for EMC Clariion CX Series fa ilover for dual- contr oller configuration • Support for STK 9840 C tape drive S pecial Configuration Requirem[...]

  • Page 4

    4 September 2 004, ADIC Using StorNext with Xsan StorNext is interoperab le with the Apple Xsan applicat ion. If you are testin g a heterogeneous mix of Apple Xsan and ADIC StorNext clients, the Xsan build must be 7N125 or greater. For information on supported hardware environments when runn ing Xsan, refer to the Apple Xsan do cumentation. To atta[...]

  • Page 5

    September 2004, ADIC 5 Certified System Components This table lists certified system co mponents that support SNMS 2.4.1. Component Descriptio n Browsers Netscape 4 .7x, 4.8x, 7.0 Microsoft Inter net Explorer 5.5 and later HBA Emulex LP8000, LP850, LP9 000, LP90002 QLogic: QLA2200, QLA2310, QLA2340, QLA23 42 FC Router ADIC FCR 250, SNC 3000, SNC 51[...]

  • Page 6

    6 September 2 004, ADIC System Requirements To successfully install SNMS 2. 4.1, th e requirements listed in the following tables must be met. StorNext FS Requirements For each StorNext FS mount, these requirements must be met. System/Component Req uirement AIX StorNex t FS client s: A minimum of 128 MB of RAM is required. IRIX StorNext FS clie nt [...]

  • Page 7

    September 2004, ADIC 7 StorNext Storage Manager Requirements Operating System Level Requirements These tables list the req uired operating system l eve ls required to successfully operate SNMS and StorNext FS 2.4.1. StorNext Management Suite Requirements Note S torNext SM only runs on SGI IRIX, Red Hat Linux, and Sun Solaris ope rating systems. Sys[...]

  • Page 8

    8 September 2 004, ADIC StorNext FS Requirements Server Plat form Operating System Levels AIX 5.2 (64-bit) IRIX 6.5.19, 22f and 6.5.19, 22 and 23m Solaris Solaris 8 and 9 Red Hat Linux Uniprocessor or Multiproce ssor , Red Hat Enterprise Linux Advanced Server 3.0, Update 2, kernel levels 2.4.21-15.0.x.EL and 2.4.21-15.0.x.ELsmp. T o build a loadabl[...]

  • Page 9

    September 2004, ADIC 9 Upgrade Instructions This section describes the following up grades: • Upgrading to SNMS 2.4.1 • Upgrading to StorNext FS 2 .4.1 • Upgrading SNMS from Red Hat Linux 8.0 to Red Hat Enterprise Linux Adva nced Server 3.0 on page 10 • Upgrading SNMS on IRIX on page 13 Upgrading to SNMS 2.4.1 Use the following instructions[...]

  • Page 10

    10 September 2 004, ADIC •F o r Solaris , type: pkgrm ADICcvfs •F o r Linux , type: rpm -qa|grep cvfs-client cvfs-client_<version information> rpm -ea cvfs-client_<version information> rpm -qa|grep cvfs-server cvfs-server_<version information> rpm -ea cvfs-server_< version information > •F o r Windows click: Start >[...]

  • Page 11

    September 2004, ADIC 11 4 Mount the backup med ia. a. From the StorNext Storage Manager (SNSM) Home Page, click Media > Library > Mount . This action enables media to moun t without requiring an opera tor to manually open the library and place backup media in the drive. b. Record the drive alias where the media is mounted. 5 Record the serial[...]

  • Page 12

    12 September 2 004, ADIC Post-Upgrade Tasks After upgrading to RHEL, use this procedure to complete post-upgrade tasks. 1 Reconnect all disconnected internal disks. 2 Mount the SNMS 2.4.1 installation CD and install the SNMS software. Type: inst.StorNext 3 Add SNMS environment settings to the shell. Type: . /usr/adic/.profile - or - source /usr/adi[...]

  • Page 13

    September 2004, ADIC 13 Upgrading SNMS on IRIX For instructions on upgrading an IRIX mach ine to SN MS 2.4. 1, contact AT AC. After upgr ading to SNMS 2.4.1, you must perform the followin g post-upgrade task to turn off mediaid . If you upgraded StorNext on a ma chine running IRIX (all suppo rted versions), use this procedure to turn off mediad for[...]

  • Page 14

    14 September 2 004, ADIC Known Issues This table lists known issues in this release of StorNext. Operating System CR Number Service Request Number Description W orkaround AIX 33986 N/A During a S torNext upgrade, if you encounter a DSM failure that resembles the following output: SNFS UPGRADE 2.4.1(48) Status 1) Upgrade 2.4.1(48) perl Complete 2) U[...]

  • Page 15

    September 2004, ADIC 15 Linux 34383 N/A FSM may p anic and deleting files is difficul t, after system reaches 100% capacity . 1 Add the following line (tempora rily) to the configuration file: MaxMBPerClientReserve 0 2 Restart FSM and ver ify that files can be re moved to free enough sp ace to continue operations. 3 Remove files. 4 Remove the line [...]

  • Page 16

    16 September 2 004, ADIC Windows 34699 N/A File system does not auto matically mount after a reboot due to GetByHostName failure. Do one of the following: • Add the server name to the etchosts file on the Windows client. - or - • Type the IP address of the machine in the fsnameservers tab instead of the machine name. All 3 4784 N/A Whe n perfo[...]

  • Page 17

    September 2004, ADIC 17 Resolved Issues This table lists resolved issu es in this release of SNMS. All 34571 N/A Displayed quotas are different than requested quot as. N/A 34720 N/A Breaking an Ethernet co nnection causes a disconnect that invalidates locks (file locking). N/A 34875 N/A All SNMS compone nts must be stopped and rest arted after a di[...]

  • Page 18

    18 September 2 004, ADIC Windows 15635 N/A S torNext FS errors when mapping a drive on Windows. 31013 N/A A daemon exce ption error was experienced on a Windows 200 0 client. 31952 N/A The call to PnVerifyWindowsCompatable() is failing with an VOP_EINVAL error . I18N support on Windows is non-functional. 33646 N/A Getting a exception on W2K client [...]

  • Page 19

    September 2004, ADIC 19 All 31977 N/A Af ter a file has been delet ed, the SNSM File Recover page returns an "undefined" st atus rather than the filename. 32150 N/A The drive moun t state is n ot updated for media that is missing fr om physical libraries during aud its. 32239 N/A When using the GUI, network-a ttached libraries display inc[...]

  • Page 20

    20 September 2 004, ADIC Limitations This table lists the limitations that have been discovered in this release of SNMS. Operating Sy stem/ Component Affect ed Description IRIX S torNext FS uses 64-bit inode numbers. Program s compiled without 6 4-bit support may expe rience problems wo rking with files with inode numbers greater than 2 GB. This is[...]

  • Page 21

    September 2004, ADIC 21 Linux S torNext FS is shipped as sepa rate, installable versions for the Uniprocessor (up) and Mu ltiprocessor (sm p) Linux kern el versions. Y ou need to select the correct kernel version of S t orNext FS. Otherwise you will encounter proble ms during inst allation and while running the product. Use the uname -v command to [...]

  • Page 22

    22 September 2 004, ADIC Solaris S torNext FS only supports 64-bit inod es for inst allations of the software on Solaris 8. (CR 8208). For LUNs there is a maximum limit of 850 GB. Recommendation : T o maximize support across all platforms, set LUNs to be no greater than 850 GB when you are using Solaris 8 or 9. On Solaris, by default, the /usr/lib/[...]

  • Page 23

    September 2004, ADIC 23 Documentation These documents are curr ently available for StorNext products: All Hot re-zoning of SAN fabrics is not supported. S torNext is incomp atible with CXFS. S torNext File System is incompat ible with third-party portmappers. The SNMS G UI does not support an is olated metadata networ k topology with a system confi[...]

  • Page 24

    24 September 2 004, ADIC[...]