14.1 Overview of OES 2 Storage

This section presents the following overview information for the file systems included in OES:

14.1.1 Databases

See the topics in databases in the OES online documentation.

14.1.2 iSCSI

See the topics in iSCSI for Linux in the OES online documentation.

14.1.3 File System Support in OES

As shown in Figure 14-1, both OES 2 and NetWare support Novell Storage Services as well as their traditional file systems.

Figure 14-1 File System Choices on OES 2 Servers

Table 14-1 summarizes OES file system types and provides links to more information.

Table 14-1 File Systems Available on OES 2 Servers

File System Type


Link for More Information

Linux POSIX File Systems

SLES 10 includes a number of different file systems, the most common of which are Ext3, Reiser, and XFS.

OES 2 services are supported on Ext3, Reiser, and XFS.

For an overview of the supported file systems in OES 2, see File Systems Overview in the OES 2 SP3: File Systems Management Guide.

NetWare Traditional File System

This is a legacy file system on NetWare servers that supports the Novell file service trustee access control model.

For more information, see the NW6.5 SP8: Traditional File System Administration Guide.

Novell Storage Services (NSS)

NSS lets you manage your shared file storage for any size organization.

On Netware, NSS features include visibility, a trustee access control model, multiple simultaneous name space support, native Unicode, user and directory quotas, rich file attributes, multiple data stream support, event file lists, and a file salvage subsystem.

Most of these features are also supported on NSS on Linux. For a feature comparison, see Comparison of NSS on NetWare and NSS on Linux in the OES 2 SP3: NSS File System Administration Guide for Linux.

For an overview of NSS, see Overview of NSS in the OES 2 SP3: NSS File System Administration Guide for Linux.

Novell Storage Services (NSS)

The following sections summarize key points regarding NSS:

Understanding NSS Nomenclature

NSS uses a specific nomenclature to describe key media objects. These terms appear in both the NSS documentation and in NSS error messages.

For more information, see NSS Nomenclature in the OES 2 SP3: NSS File System Administration Guide for Linux.

Comparing NSS with Other File Systems

Because OES 2 supports a variety of file systems, you might want to compare their features and benefits as outlined in the following sections of the OES 2 SP3: NSS File System Administration Guide for Linux:

NSS and Storage Devices

NSS supports both physical devices (such as hard disks) and virtual devices (such as software RAIDs and iSCSI devices).

For more information on the various devices that NSS supports, see Managing Devices in the OES 2 SP3: NSS File System Administration Guide for Linux.

14.1.4 Storage Basics by Platform

The following sections summarize storage basics for Linux and NetWare.

Linux and File Systems

For a high-level overview of the file system on Linux, including the root (/) directory, mount points, standard folders, and case sensitivity, see Understanding Directory Structures in Linux POSIX File Systems in the OES 2 SP3: File Systems Management Guide.

NetWare Directories

NetWare uses volumes and directories (or folders) to organize data. NetWare file systems support directory paths, fake root directories, Directory Map objects, and drive mappings.

For more information, see Understanding Directory Structures for the NSS File System in the OES 2 SP3: File Systems Management Guide.

NetWare Storage Devices

NetWare lets you use many different kinds of storage devices, including server disks, single storage devices, arrays of storage devices, and virtual storage devices.

To understand how NetWare connects with and uses storage devices, see Overview of Server Disks and Storage Devices for NetWare in the NW6.5 SP8: Server Disks and Storage Devices.

14.1.5 Storage Options

The following sections summarize OES storage options.

Dynamic Storage Technology

Dynamic Storage Technology for OES 2 lets you present the files and subdirectories on two separate NSS volumes as though they were on a single, unified NSS volume called a shadow volume.

NCP client users and Samba/CIFS users who access the primary volume see the files and subdirectories from both volumes as if they were all on one volume. All the actions they take—renaming, deleting, moving, etc.—are synchronized by Dynamic Storage Technology across the two volumes.

Unlike the NCP client, backup tools see the volumes separately and can therefore apply one backup policy to the primary and a different backup policy to the secondary volume.

You can use Dynamic Storage Technology to substantially reduce storage costs by placing your less frequently accessed files on less expensive storage media. You can even employ a “move on demand” migration strategy by defining new, more expensive SAN or RAID storage that is initially empty as the primary volume, and then configuring Dynamic Storage Technology so that data is migrated to this primary storage only when it is accessed.

In addition, Dynamic Storage Technology doesn’t suffer the performance penalty that HSM solutions do.

For more information about Dynamic Storage Technology, see the OES 2 SP3: Dynamic Storage Technology Administration Guide.

Direct-Attached Storage Options (NSS and Traditional)

As shown in Figure 14-1, you can install traditional volumes and Novell Storage System (NSS) volumes on both OES platforms. These devices can be installed within the server or attached directly to the server through an external SCSI bus.

For more information, see Direct Attached Storage Solutions in the OES 2 SP3: Storage and File Services Overview.

Advanced Storage Options

NSS volumes support the following advanced storage solutions, as documented in the OES 2 SP3: Storage and File Services Overview.

14.1.6 NetWare Core Protocol Support (Novell Client Support) on Linux

Many organizations rely on Novell Client software and the NetWare Core Protocol (NCP) for highly secure file storage services.

Novell Storage Services (NSS) volumes are NCP volumes by nature, and you can also define Linux POSIX volumes as NCP volumes. The main difference in access control between NSS volumes and Linux POSIX volumes that are defined as NCP volumes is that NSS extended file and directory attributes are not available on Linux POSIX volumes.

The NCP server for OES 2 lets you attach to Linux POSIX volumes that are defined as NCP volumes using Novell Client software. For more information, see Section 18.6, NCP Implementation and Maintenance.