This section presents the following overview information for the file systems included in OES:
See the MySQL documentation on the Web.
See the topics in iSCSI for Linux
in the SLES online documentation.
As shown in Figure 13-1, both OES and NetWare support Novell Storage Services as well as their traditional file systems.
Figure 13-1 File System Choices on OES and NetWare Servers
Table 13-1 summarizes OES file system types and provides links to more information.
Table 13-1 File Systems Available on OES and NetWare Servers
File System Type |
OES |
NetWare |
Summary |
Link for More Information |
---|---|---|---|---|
Linux POSIX File Systems |
Y |
N |
SLES 11 SP4 includes a number of different file systems, the most common of which are Ext3, Reiser, XFS, and Btrfs (requires the btrfsprogs package). OES 11 SP3 services are supported on Ext3, Reiser, XFS, and Btrfs. |
For an overview of the supported file systems in OES 11, see For an overview of Linux POSIX file systems, see Overview of File Systems in Linux in the SLES 11 SP4: Storage Administration Guide. |
NetWare Traditional File System |
N |
Y |
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) |
Y |
Y |
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 |
For an overview of NSS, see |
The following sections summarize key points regarding NSS:
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 11 SP3: NSS File System Administration Guide for Linux.
Because OES 11 supports a variety of file systems, you might want to compare their features and benefits as outlined in the following sections of the OES 11 SP3: NSS File System Administration Guide for Linux:
NSS Linux vs. NSS NetWare:
Comparison of NSS on NetWare and NSS on Linux
NSS Linux vs. Linux POSIX:
Comparison of NSS on Linux and NCP Volumes on Linux POSIX File Systems
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 11 SP3: NSS File System Administration Guide for Linux.
The following sections summarize storage basics for Linux and NetWare.
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 11 SP3: File Systems Management Guide.
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 11 SP3: File Systems Management Guide.
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.
The following sections summarize OES storage options.
Dynamic Storage Technology for OES 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 Novell CIFS users automatically see a merged view of the files and subdirectories on the shadow volume when they access a share on the primary volume. All the actions they take--renaming, deleting, moving, etc.--are synchronized by Dynamic Storage Technology across the two volumes. If you use supported native Linux file access protocols, such as Novell Samba, SSH, or Novell FTP (PureFTP-d), to access the DST volume, you can enable ShadowFS to provide a merged view location for LUM-enabled users of those protocols. Novell CIFS and Novell Samba cannot be used on the same server.
Backup tools can access the volumes directly and separately, instead of via the merged view shown to NCP and CIFS users. You can apply one backup policy to the primary volume 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.
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 11 SP3: Dynamic Storage Technology Administration Guide.
As shown in Figure 13-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 11 SP3: Storage and File Services Overview.
NSS volumes support the following advanced storage solutions, as documented in the OES 11 SP3: Storage and File Services Overview.
Network Attached Storage Solutions
A dedicated data server or appliance that provides centralized storage access for users and application servers through the existing network infrastructure and by using traditional LAN protocols such as Ethernet and TCP/IP. When Gigabit Ethernet is used, access speeds are similar to direct attached storage device speeds.
The disadvantage is that data requests and data compete for network bandwidth.
Storage Area Network Solutions
A separate, dedicated data network consisting of servers and storage media that are connected through high-speed interconnects, such as Fibre Channel.
You can create a SAN using Linux iSCSI.
Fault-Tolerant and High-Availability Architectures
Use one or more of the following technologies:
Multiple Path I/O: The Linux Device Mapper Multipath I/O tool helps prevent failure in the connection between the CPU and the storage device by automatically identifying multiple paths between each Linux server and its storage devices.
Software RAIDs: NSS supports software RAIDS to improve storage availability and performance by enhancing data fault tolerance and I/O performance.
For more information, see Managing NSS Software RAID Devices
in the OES 11 SP3: NSS File System Administration Guide for Linux.
Server Clusters: With Novell Cluster Services, you can configure up to 32 servers into a high-availability cluster where resources and services are dynamically allocated to any server in the cluster and automatically switched to another server if the hosting server fails.
By manually switching services, IT organizations can maintain and upgrade servers during production hours and eliminate scheduled downtime.
For more information, see the OES 11 SP3: Novell Cluster Services for Linux Administration Guide. To convert a NetWare cluster to an OES cluster, see the OES 11 SP3: Novell Cluster Services NetWare to Linux Conversion Guide.
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 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.