Manuel d'utilisation / d'entretien du produit 2.4.1 du fabricant Quantum
Aller à la page of 24
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.
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.
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 • .
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.
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 .
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.
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.
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.
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.
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>.
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.
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.
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.
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.
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.
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.
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).
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 .
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.
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.
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.
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.
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.
24 September 2 004, ADIC.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté Quantum 2.4.1 c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du Quantum 2.4.1 - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation Quantum 2.4.1, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le Quantum 2.4.1 va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le Quantum 2.4.1, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du Quantum 2.4.1.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le Quantum 2.4.1. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei Quantum 2.4.1 ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
