NetWare 5.1 Advanced Administration

Chapter 6: Setting Up a Novell Storage Service (NSS) File System

 

Objectives:

This chapter introduces the management aspects of a file system, and discusses organizing one. The objectives important to this chapter are found on page 6-1:

  1. Define NSS and Its Components
  2. Describe the NSS Architecture
  3. List the Advantages and Disadvantages of Using NSS
  4. Implement NSS
  5. Manage Storage Groups and NSS Volumes
Concepts:
Define NSS and Its Components

Novell Storage Services (NSS) is discussed next.  This is an enhanced, improved file system, compared to previous versions of NetWare. It is optional: you don't have to install or use it. If you do install it, it does not have to replace the traditional NetWare File System: NSS can coexist with NFS.

The NSS service first scans hard drives for unused space. Whatever space is found is marked off, labeled as available to NSS, and recorded in a pool called the NSS object bank. This action is registering the space. Each of several hard drives may have free space available. The space that is marked, labeled, and recorded from each hard drive can be called a storage deposit. When NSS starts to used some of this space the storage deposit becomes a managed object.

NSS can register space in NetWare partitions and in IBM-formatted (DOS) partitions.

However, note that this action is essentially creating an NSS partition on the hard drive, and that there is a limit of four partitions within any IBM-formatted partition. If an IBM/DOS partition already has four partitions in it, you cannot make an NSS partition in it. This is why you do not want to create partitions within your DOS partition on the server.

When NSS takes free space from a NetWare partition, NFS sees the new NSS partition as a file.

NSS can mount a CD as a read-only volume. This has the advantage of making it available to users on your system. To make it possible to do so, load CDROM.NLM on your server.

NSS takes its registered partitions and combines them into logical storage groups. Storage groups are combined into logical NSS volumes. The text cautions you not to combine space from inside NetWare volumes and space from outside NetWare volumes into one NSS volume.

NSS volumes may be physically located on several servers, and on several hard drives. They act as though they are on one server. Storage groups may be combined. More storage groups may be added to NSS volumes after the volumes are created.


Describe the NSS Architecture

The NSS system is composed of five layers, each of which has components:

  • Media Access Layer (MAL) - hardware interface
  • Loadable Storage Subsystem (LSS) - for fault recovery and adding new storage
  • Object Engine (OE) Layer - location of the object bank
  • Semantic Agent (SA) Layer - drivers for various clients that might use NSS
  • Common Layer Interface (CLI) - similar to SA, works with it

The Media Access Layer is most closely associated with hardware (storage devices). Providers and Consumers operate on this layer:

  • Provider - scans storage devices for free space, registers it, and places it in the object bank. Two providers are available:
    • NSS Media Manager (MMPRV) - scans for space on IBM-formatted partitions
    • NSS File Provider (NWPRV) - scans for space in NetWare partitions
  • Consumer - manages registered free space by creating a deposit object (a collection of space), builds logical paths to the space and registers (marks) the free space for its own use.
  • Storage Group - the MAL layer creates storage groups and volumes, after sharing information with the LSS layer.

The Loadable Storage Subsystem (LSS) reads the information about available space registered by MAL. Two features of LSS are listed:

  • Rapid Recovery - LSS provides a log of NSS volume transactions, both completed and not completed. This means that if a server crashes, you may be able to complete the transaction, or at least back out of it without having to restore the entire volume. (A transaction is a write, copy, erase, or other file related action.)
  • Modularity - LSS is the layer that allows adding new storage devices to the existing system.

The Object Engine (OE) Layer is the location of the object bank. It uses balanced trees (B-trees) for storage, which are more efficient than standard directories. This layer is responsible for the fact that NSS can have larger and more numerous volumes and files than NFS.

The Semantic Agent (SA) layer contains loadable software modules for NetWare, the Internet, and other clients that define how specific clients communicate with stored NSS objects. Think of it as a driver or interpreter section for NSS.

The Common Layer Interface (CLI) contains a set of APIs that define how SAs access the object engine for the following NSS services:

  • Naming services - object naming and lookup operations, name space service, and context management services
  • Object services - creation, deletion, storage, and definition of objects
  • Management services - other types of NSS management, such as registration, file locking, transactions, and management of storage pools and NSS volumes

 


List the Advantages and Disadvantages of Using NSS

Advantages:
NFS NSS
User files can grow no larger than 2 GB very large files, up to 8TB (terabytes)
Directories are limited to 16 million entries NSS allows trillions of files in a single directory.
Traditional volumes might take several minutes to mount and to repair NSS volumes mount and repair much more rapidly
Only eight volumes are allowed per NetWare partition NSS allows unlimited volumes per NetWare partition
Only one NetWare partition is allowed per disk NSS allows up to four NetWare partitions per disk
  NSS has better support for CD-ROMs, for memory use and for other storage devices.

Now the bad news. Disadvantages:

  • NSS cannot be used on the SYS: volume.
  • NSS does not support Transaction Tracking, disk striping, disk mirroring, HSM, RTDM, or file compression.

Neither good nor bad: NSS uses new utilities, REBUILD and VERIFY, instead of VREPAIR.

 


Implement NSS

NSS can be installed when you create a server, or it can be done later. Some cautions are given:

  • NSS will need at least 10 MB of space for each volume.
  • Since NSS volumes will typically span multiple devices, faster backup methods are preferred.
  • Novell recommends using a smaller SYS: volume if you plan to store most of your files on NSS volumes.

Minimum requirements for loading NSS:

  • A server running NetWare 5
  • A minimum of 10 MB of free space to create an NSS volume
  • 1.5 MB of RAM (300 cache buffers) for loading the modules
  • 2 MB of memory (500 cache buffers) for running NSS

The NLM that provides NSS services is NSS.NLM. It can be configured with NWCONFIG or with its own administration menus.

NSS has three menus: Configure, View, and Utilities. To access them enter the following command at the server console:

  NSS /MENU

To use NSS on an existing system, you can convert existing NetWare volumes to NS volumes, you can create NSS volumes in space not being used by existing volumes, you can repartition your hard drive, or you can install a new hard drive.

To create an NSS volume, you first scan for free space, assign the free space to NSS, then create a storage group and/or volume out of that space.

 


Manage Storage Groups and NSS Volumes

NSS storage groups and volumes can be viewed with NWCONFIG or with NSS Administration Menus.

The same two utilities may be used to increase the size of (add storage groups to) an NSS volume.

NFS volumes are repaired with a console utility called VREPAIR. This is not used with NSS volumes. To repair NSS volumes, use the REBUILD utility, available from the server console, and from the NSS Menus. (Note: REBUILD does not work with NFS volumes. Fair is fair...) From the console you can issue the command with a comma delimited list of volumes to repair. NetWare can only rebuild 5 volumes at a time. The command would look like this:

  NSS /REBUILD=NSS volume_name, NSS volume_name

Volumes should be verified after rebuilding, and must be mounted before they can be used.

If you use NWCONFIG to create NSS volumes, they are automatically added to NDS. If you create them in the NSS Menus, you will need to manually add them to NDS through NWCONFIG or NetWare Administrator. This sounds like an argument for using NWCONFIG.

NSS volumes can be released/destroyed through NWCONFIG or the NSS Menus. Doing so will release all the storage groups in the volume, destroy the data in them, and make the space available to the NFS system.