Novell Storage Services New Features of Netware 5

Total Page:16

File Type:pdf, Size:1020Kb

Novell Storage Services New Features of Netware 5 BY JOHN E. JOHNSTON NewNew FeaturesFeatures etWare 5's brand new Ndata storage system, Novell Storage Services, already offers several advantages over ofof NetWareNetWare 5:5: its predecessor, the 32-bit NetWare File System (NWFS), while also laying the ground- NovellNovell StorageStorage work for a dramatic conceptual leap in the way network data ServicesServices is stored. G While NWFS could support 64 simultaneously mounted volumes with a maximum volume size of 1TB, NSS can support up to 253 visible volumes with a maximum volume size of 8TB for a 32-bit system. If you are using a 64-bit system, however, NSS will permit a gigantic volume of up to a whopping 8 exabytes. G Less RAM is required to support volumes. G Faster volume mounting. G DOS partitions can be accessed on the file server. G Capability of defining new name spaces (in addition Storage Services (NSS) is a new 64-bit data to DOS, Mac and Long). NOVELL storage system that comes bundled with G CD-ROMs can be mounted as NSS volumes, making the NetWare 5 product. Because it features 64-bit operation, the CDs easier and faster to mount. NSS provides the ability to store larger files (up to 8 terabytes), and can mount larger volumes and a greater number of volumes While all of these advantages are certainly practical, what than its predecessor, the 32-bit NetWare File System (NWFS). really makes NSS so revolutionary is its new conceptual design. The NSS architecture also provides significant enhancements By introducing the idea of logical storage to NetWare data over NWFS in both conceptual design and system performance. storage structures, NSS continues to lead network technology This article will explore the benefits you can expect from away from limitations based on physical location and the an NSS implementation, the limitations of NSS in its current characteristics of individual devices. For example, up until now configuration, and what new doors NSS may open for network the size of a NetWare partition was limited by how large a design down the road. single hard drive on that server was. If a server had more than one hard drive, the size of its partition could still be no greater NSS BENEFITS than the size of its largest hard drive; multiple partitions had to be created in order to exploit the storage space provided by the The range of immediate benefits provided by NSS will additional hard drives. This sometimes led to a design that was likely prove useful to both large and small NetWare shops. cumbersome to work with and even more difficult to manage. Some of these benefits are a direct result of the 64-bit design, NSS eliminates this inefficiency by creating logical partitions, while others stem from alterations made to individual com- partitions not restricted by the physical limitations of a single ponents in the NetWare data storage structure. The advantages device. The logical NSS partitions are created from storage of NSS deployment are as follows: pools, which are comprised of all the unallocated free space available on all of the devices attached to a particular server. This G NSS can store large (up to 8TB) files and can also store way, it is possible to have a single NSS partition that utilizes a large number of files on a single NSS volume (up to space from more than one hard drive on a server, maximizing 8 trillion files). all available storage space while also maintaining ease of use G A single server can have up to a million files open and the highest level of manageability by centralizing the at the same time. administration of storage devices. TECHNICAL SUPPORT • AUGUST 1999 ©1999 Technical Enterprises, Inc. Reproduction of this document without permission is prohibited. Unfortunately, the current release of NSS is only capable of locating NSS Partitions available space on server hard drives. However, the full potential of Just as with the standard NetWare file system, NSS uses disk logical storage promises to be realized with future releases of NSS, partitions to hold volumes. The difference is that, as a logical partition for which support of other storage devices is planned. rather than a disk partition, the NSS partition can span multiple hard drives and, in future releases of NSS, several other types of NSS LIMITATIONS storage devices as well. For example, when you set up a standard NetWare file server, you first create a small DOS partition on the file NSS brings with it some liabilities and incompatibilities which server's hard drive with the remaining space on the server's hard drive are common with any new technology. Novell is working on often being allocated as a NetWare partition. One or more NetWare addressing some of these deficiencies, but for the moment NSS volumes are placed in this NetWare partition. NSS works in a similar does not support any of the following functions: manner, though the terminology and mechanisms are different. The process of establishing an NSS partition begins with programs SYS: volume - The SYS: volume cannot reside on an NSS volume. called providers, which search your server's devices to find free This means that you must still have a standard NWFS partition on storage space. There are currently two providers to choose from in your server in order to hold the SYS: volume. NSS, the NSS Media Manager for IBM partitions (MMPRV) and the NSS File Provider for NetWare (NWPRV). The MMPRV FTP - Currently, you cannot place the File Transfer Protocol on an provider will search the storage devices attached to a server looking NSS volume. Novell has stated, however, that future versions of NSS for all of the unallocated free space available in standard IBM- should be modified to support the Novell File Transfer Protocol service. compatible partitions; the NWPRV provider is used for finding free space available in existing NetWare volumes. When ini- File compression - This space-saving feature of tiating the NSS partition creation process, you will standard NetWare volumes is not currently sup- have to select which of the providers you will ported on NSS volumes. While all of use for locating your free space. All of the free space a provider finds is Block sub-allocation - The block size for these advantages are collected into a single storage pool. The NSS volumes is fixed at 4K, making block certainly practical, administrator must then indicate how sub-allocation impossible. much of this storage pool is to be utilized what really makes NSS as an NSS partition. Once this is done, Transaction Tracking System (TSS) - NSS components called consumers take TSS is not supported on NSS volumes. so revolutionary control of the indicated storage space, preparing it for use by NSS. In NSS termi- Disk mirroring and duplexing - You cannot is its new conceptual nology, this process is known as claiming mirror or duplex NSS volumes, which can be design. ownership of the storage space. Once NSS a real problem when trying to build a fail-safe, claims ownership of a chunk of unallocated fault tolerant environment for your organization. disk space, an NSS Managed Object is created to represent that chunk of space. Disk striping - NSS does not support disk striping as of yet, As indicated, the NWPRV provider will create your NSS although Novell has announced that future NSS versions might be partition from unused disk space within an existing NetWare modified to provide disk striping support. volume. For example, if the VOL1: NetWare volume on your server contains 4GB of unused space, you can allocate this space Auditing - You cannot use the NetWare auditing facility on NSS to an NSS partition. If you choose this option, a file named volumes, although Novell has also indicated that the auditing function $$NSS$$.PRV will be created on the NetWare volume by NSS may be supported in upcoming versions of NSS. to reserve the space. NetWare will then recognize that the remaining space in the volume is being taken up by an NSS Obviously, with its inability to host a SYS: volume, NSS is currently partition. You must take a couple of precautions if you elect to designed to exist alongside a functioning NWFS partition. This utilize this facility: means that your server will require at least three partitions if you wish to utilize NSS: the DOS disk partition, the NWFS disk partition G Although technically feasible, you should try to avoid for the SYS: volume, and the NSS logical partition. One can only creating an NSS partition using free space from both a hope that future versions of NSS and NetWare will work toward NetWare volume and a disk partition. This will create consolidation. But for now, this somewhat clumsy structure must be unpredictable results and can even result in lost data. tolerated in order to enjoy the advantages of NSS. Perhaps this instability when mixing the two sources will be corrected in future versions of NSS. But for now, you NSS COMPONENTS should try to restrict the source of your storage space to either one or the other whenever possible. NSS utilizes three components — NSS partitions, storage groups and NSS volumes — to define and manage NSS functionality. Let’s G Should the NetWare volume on which an NSS partition is created take a closer look at the functions of each component. be deleted, the NSS partition will be deleted also. ©1999 Technical Enterprises, Inc. Reproduction of this document without permission is prohibited. TECHNICAL SUPPORT • AUGUST 1999 Storage Groups FIGURE 1: THE NETWARE CONFIGURATION MAIN MENU Once one or more NSS Managed Objects have been created, these Managed Objects are used in the construction of NSS storage groups.
Recommended publications
  • Migrating from Netware to OES 2 Linux
    Best Practice Guide www.novell.com Migrating from NetWare to OES 2 prepared for Novell OES 2 User Community Published: November, 2007 Disclaimer Novell, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Trademarks Novell is a registered trademark of Novell, Inc. in the United States and other countries. * All third-party trademarks are property of their respective owner. Copyright 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of Novell, Inc. Novell, Inc. 404 Wyman Suite 500 Waltham Massachusetts 02451 USA Prepared By Novell Services and User Community Migrating from NetWare to OES 2—Best Practice Guide November, 2007 Novell OES 2 User Community The latest version of this document, along with other OES 2 Linux Best Practice Guides, can be found with the NetWare to Linux Migration Resources at: http://www.novell.com/products/openenterpriseserver/netwaretolinux/view/all/-9/tle/all Contents Acknowledgments.................................................................................. iv Getting Started...................................................................................... 1 Why OES 2?..............................................................................................1 Which Services Are Right for OES 2? ................................................................4
    [Show full text]
  • Netinfo 2009-06-11 Netinfo 2009-06-11
    Netinfo 2009-06-11 Netinfo 2009-06-11 Microsoft släppte 2009-06-09 tio uppdateringar som täpper till 31 stycken säkerhetshål i bland annat Windows, Internet Explorer, Word, Excel, Windows Search. 18 av buggfixarna är märkta som kritiska och elva av dem är märkta som viktiga, uppdateringarna finns för både servrar och arbetsstationer. Säkerhetsuppdateringarna finns tillgängliga på Windows Update. Den viktigaste säkerhetsuppdateringen av de som släpptes är den för Internet Explorer 8. Netinfo 2009-06-11 Security Updates available for Adobe Reader and Acrobat Release date: June 9, 2009 Affected software versions Adobe Reader 9.1.1 and earlier versions Adobe Acrobat Standard, Pro, and Pro Extended 9.1.1 and earlier versions Severity rating Adobe categorizes this as a critical update and recommends that users apply the update for their product installations. These vulnerabilities would cause the application to crash and could potentially allow an attacker to take control of the affected system. Netinfo 2009-06-11 SystemRescueCd Description: SystemRescueCd is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system tools (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools). It is very easy to use: just boot the CDROM. The kernel supports most of the important file systems (ext2/ext3/ext4, reiserfs, reiser4, btrfs, xfs, jfs, vfat, ntfs, iso9660), as well as network filesystems (samba and nfs).
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • Netware 6 Installation C4882-4 Ch01.F 2/4/02 9:53 AM Page 4
    c4882-4 Ch01.F 2/4/02 9:53 AM Page 3 CHAPTER 1 NetWare 6 Installation c4882-4 Ch01.F 2/4/02 9:53 AM Page 4 Instant Access ● Preparing to install There are four recommended tasks to prepare your network for NetWare 6: ᮣ Back up your data ᮣ Update eDirectory (if necessary) ᮣ Update eDirectory schema (if necessary) ᮣ Update Certificate Authority object in eDirectory Installing ᮣ To install a new server, run INSTALL from the root of the NetWare 6 Operating System CD-ROM. Upgrading ᮣ NetWare 4.x or 5.x — To upgrade to NetWare 6 choose one of these options: • Perform an Accelerated Upgrade by running ACCUPG.exe from the root of the NetWare 6 Operating System CD-ROM. This requires that you first copy the entire NetWare 6 Operating System CD-ROM to a NetWare server that will function as the Staging server. • Perform an In-Place upgrade by running INSTALL from the root of the NetWare 6 Operating System CD-ROM. • Perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NetWare 3 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NT v3.51 or v4 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation.
    [Show full text]
  • Netware 6 Server Management CHAPTER 3
    04 9814 ch03.qxd 8/19/04 9:32 AM Page 165 CHAPTER 3 NetWare 6 Server Management CHAPTER 3 This chapter covers the following testing objectives for Novell Course 3004: Novell Network Management: . Use NetWare Remote Manager . Identify What iMonitor Is and How to Use It . Use iMonitor to Diagnose and Repair eDirectory Problems . Set Up and Configure NSS . Monitor, Manage, and Rebuild NSS Storage Space . Set Up SMS for SBCON and NWBACK32 . Back Up Data with SBCON and NWBACK32 . Restore Data with SBCON and NWBACK32 Novell is directing the construction of the world’s central information super- highway with the help of you, me, and thousands of other electronic transit workers (orange vest optional). NetWare 6 further revolutionizes Novell’s oneNet strategy with the introduction of Web-enabled administration tools, highly scalable networking protocols, and multiprocessor support. Implementing these components makes your job easier and provides your users with more reliable network access. Welcome to anytime, anywhere advanced administration via NetWare 6. As a network administrator, it’s your responsibility to focus on the NetWare 6 network to ensure that it stays fine-tuned and in peak condition. In Chapter 1, “NetWare 6 Installation,” and Chapter 2, “NetWare 6 Upgrade and Migration,” we began our NetWare 6 CNE journey by building the cor- nerstone of your network—the NetWare 6 server. Now it’s time to super- charge the network. 04 9814 ch03.qxd 8/19/04 9:32 AM Page 166 166 PART I Novell Network Management for NetWare 6 This chapter focuses on three key areas related to managing your NetWare 6 server: .
    [Show full text]
  • An Overview of the Netware Operating System
    An Overview of the NetWare Operating System Drew Major Greg Minshall Kyle Powell Novell, Inc. Abstract The NetWare operating system is designed specifically to provide service to clients over a computer network. This design has resulted in a system that differs in several respects from more general-purpose operating systems. In addition to highlighting the design decisions that have led to these differences, this paper provides an overview of the NetWare operating system, with a detailed description of its kernel and its software-based approach to fault tolerance. 1. Introduction The NetWare operating system (NetWare OS) was originally designed in 1982-83 and has had a number of major changes over the intervening ten years, including converting the system from a Motorola 68000-based system to one based on the Intel 80x86 architecture. The most recent re-write of the NetWare OS, which occurred four years ago, resulted in an “open” system, in the sense of one in which independently developed programs could run. Major enhancements have occurred over the past two years, including the addition of an X.500-like directory system for the identification, location, and authentication of users and services. The philosophy has been to start as with as simple a design as possible and try to make it simpler as we gain experience and understand the problems better. The NetWare OS provides a reasonably complete runtime environment for programs ranging from multiprotocol routers to file servers to database servers to utility programs, and so forth. Because of the design tradeoffs made in the NetWare OS and the constraints those tradeoffs impose on the structure of programs developed to run on top of it, the NetWare OS is not suited to all applications.
    [Show full text]
  • Copyrighted Material
    4023indx.qxd 2/11/02 11:59 AM Page 789 Index Note to the reader: Throughout this index boldfaced page numbers indicate primary discussions of a topic. Italicized page numbers indicate illustrations. Symbols & Numbers addressing, disk channel, 744 # command in login scripts, 175 addressing space, 744 %GREETING_TIME identifier variable, 177 Admin object in NDS, 47, 115, 243–244, 744 %LOGIN_NAME identifier variable, 177, 178 password, 51 %MACHINE identifier variable, 177 Admin user, 285 %OS identifier variable, 177 administrative duties %OS_VERSION identifier variable, 177 container and leaf object management, 301–319 %STATION identifier variable, 177 daily tasks, 283–285 10BaseT/100BaseT/1000BaseT, 744 antivirus protection updates, 284 backup, 284 A system log file checks, 285 management slogans, 279–280 abend (abnormal ending), 603, 680, 744 NDS eDirectory management, 398–419 ABEND.LOG file, 665 deleting NetWare server object from NDS, 415 Abort Partition Operation command, 401 DSMERGE for tree management, 408–415 Access Control right, 246, 247 fixing mess, 407–408 Account Manager, 114 partitions and replicas, 398–407 accounting, 744 with Tree Walker, 416, 416–417 for user objects, 139–140, 320, 320–321 UIMPORT to move database records into ACL (access control list), 257, 744 NDS, 417–419 ACONSOLE, 376–377, 744 Novell licensing services management, 419–423 acronyms, 740–743 report on license usage, 423, 423 ACU (Automatic Client Update), 105–106, 745 user access licenses, 420–423, 421 adapters, memory and old, 607–608 planning, 276–283
    [Show full text]
  • Specialized Servers in Local Area Networks
    ELEKTROTEHNIČKO DRUŠTVO ZAGREB HR - 41000 ZAGREB, Berislavićeva 6 IV MEĐUNARODNI SIMPOZIJ O NOVIM TEHNOLOGIJAMA PULA, 25. - 27. 10. 1993. HRVATSKA mr. Dragutin Vuković MicroLAB, d.o.o. Savska cesta 41/VII 41000 ZAGREB SPECIALIZED SERVERS IN LOCAL AREA NETWORKS SPECIJALIZIRANI POSLUŽITELJI U LOKALNOJ MREŽI Summary: This paper discusses the idea of LAN attached computers' specialisation for narrow set of functions, offering specialised services to LAN participants. Case study of specialised server for CD- ROM contained databases is given. Sažetak: Obrazlaže se ideja specijalizacije računala u lokalnoj mreži za obavljanje posebnog skupa funkcija i pružanje specijaliziranih usluga ostalim sudionicima mreže. Prikazana je izvedba specijaliziranog poslužitelja koji pruža usluge korištenja baza podataka smještenih na CD-ROM diskovima. Introduction supporting complete commercial computing systems. While no vendor has yet succeeded to completely replace the For more than 30 years, the basic model of computing has traditional computing environment, the more nimble ones were revolved around large monolithic applications running on able to establish dominance in a substantial number of large, centralised mainframes. No matter what other technical computing niches that had not previously been effectively or architectural innovations have become available, they addressed. The most prominent of these niches, desktop either have been adapted to work with this basic model or computing, is now larger than mainframe comput-ing itself. discarded by mainstream information systems management. The proliferation of so many new kinds of computing system The reasons for the overwhelming loyalty of most IS inevitably raised the demand among users for these systems professionals to this traditional model are no mystery. For to be interconnected allowing data exchange and most of the history of computing, hardware was complex and synchronisation of their activities.
    [Show full text]
  • OES 2015 SP1: NSS AD Administration Guide
    Open Enterprise Server 2015 SP1 NSS AD Administration Guide June 2016 Legal Notices For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.novell.com/company/legal/. Copyright © 2016 Novell, Inc., a Micro Focus company. All Rights Reserved. Contents About This Guide 5 1 Overview of NSS AD Support 7 1.1 Understanding What Changed to Enable NSS AD Support in OES . 7 1.1.1 Novell CIFS Access Changes . .8 1.1.2 OES Service Changes For NSS AD . 9 1.1.3 Multi-Forest Support for AD Users. .9 1.1.4 Utility and Management Tool Changes . 10 2 Preparing to Deploy NSS AD 13 2.1 Software and Hardware Requirements . 13 2.2 Meeting NSS AD Infrastructure Requirements. 13 2.3 Joining OES to AD Domain When OES and AD are Present in Different DNS Domain . 14 2.4 Planning to Assign AD User and Group Trustee Rights . 15 2.5 Coexistence with NSS AD . 15 2.5.1 Incompatiblities at a Server Level . .15 2.5.2 NSS AD Is Network-Compatible with All OES Services. 16 2.5.3 NSS AD Doesn’t Affect Backward Compatibility . 16 2.5.4 Ensuring DST Support for NSS AD . 16 2.5.5 DFS Deployment with NSS AD . 16 2.6 Caveats for Deploying NSS AD . 17 2.6.1 Clustered Node Issue . 17 2.6.2 Recommendations During Upgrade . 18 3 Installing and Configuring NSS AD Support 19 3.1 Installing a New OES Server and Deploying NSS AD .
    [Show full text]
  • Netware 6.5 Storage Management Services Administration Guide
    Novell Confidential Manual (99a) 15 April 2004 Novell NetWare® 6.0 www.novell.com STORAGE MANAGEMENT SERVICES June 30, 2004 ADMINISTRATION GUIDE Novell Confidential Manual (99a) 15 April 2004 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright © 1999-2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,854; 5,671,414; 5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344;
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • OES 11 SP3: Novell Cluster Services for Linux Administration Guide 5.7.1 Prerequisites for Installing Or Updating the Clusters Plug-In
    Open Enterprise Server 11 SP3 Novell Cluster ServicesTM for Linux Administration Guide July 2016 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.novell.com/company/legal/. Copyright © 2014 - 2016 Novell, Inc. All Rights Reserved. Contents About This Guide 15 1 Overview of Novell Cluster Services 17 1.1 Why Should I Use Clusters? . 17 1.2 Benefits of Novell Cluster Services . 18 1.3 Product Features . 18 1.4 Clustering for High Availability . 18 1.5 Shared Disk Scenarios. 20 1.5.1 Using Fibre Channel Storage Systems . 21 1.5.2 Using iSCSI Storage Systems . 22 1.5.3 Using Shared SCSI Storage Systems . 23 1.6 Terminology . 23 1.6.1 The Cluster . 23 1.6.2 Cluster Resources . 24 1.6.3 Failover Planning . 26 2 What’s New or Changed for Novell Cluster Services 29 2.1 What’s New (OES 11 SP3). 29 2.2 What’s New (OES 11 SP2). 29 2.3 What’s New (OES 11 SP1). 34 2.4 What’s New (OES 11) . 37 3 Planning for a Cluster 41 3.1 Determining Your Design Criteria. 41 3.2 Using Cluster Best Practices . 41 3.3 Planning the LAN Connectivity. 42 3.3.1 VLAN . 42 3.3.2 Channel Bonding . 42 3.3.3 Spanning Tree Protocol . 43 3.3.4 IP Addresses . 43 3.3.5 Name Resolution . 43 3.4 Planning the Shared Storage Connectivity. 43 3.5 Planning the Shared Storage Solution .
    [Show full text]