D.0 List of NSS Features

This section lists the features and capabilities of OES Storage Services on Open Enterprise Server (OES) servers.

Feature Description

NSS for OES 2023

Management interfaces

iManager

NSSMU for Linux

NLVM. For more information, see OES 2023: NLVM Reference.

Utilities in the terminal console (NSSMU, RIGHTS, NSSCON, ATTRIB, RAVSUI, RAVVIEW, nssquota, ncsinit, nbackup(1))

NSS commands in the NSS Console (NSSCON)

OES Remote Manager for Linux (for Dynamic Storage Technology shadow volumes and for managing NCP Server connections to NSS volumes)

File system trustees, trustee rights, and inherited rights filter to control access to directories and files

Files and Folders plug-in to iManager

Client for Open Enterprise Server

RIGHTS utility for Linux

File system directory and file attributes to control functions available for directories and files

Files and Folders plug-in to iManager

Client for Open Enterprise Server

Directory quotas management (requires the Directory Quotas attribute for the volume)

Files and Folders plug-in to iManager

User space quota management (requires the User Space Quotas attribute for the volume)

Storage plug-in to iManager

Default mount location for NSS pools

/opt/novell/nss/mnt/.pools/poolname

Default mount location for NSS volumes

/media/nss/volumename

File system type (as recognized and reported by the operating system)

nssvol

File access protocols

NCP

OES CIFS for Linux

Linux NFS (version 3)

Linux NFS requires users to be Linux-enabled with Linux User Management. The service must also be enabled.

Interface

64-bit

Character format

Unicode

Maximum device size recognized (physical or logical)

2E64 512-byte sectors

Maximum software RAID device size

8 TB (GPT) for NSS32 Pools

8 EB (GPT) for NSS64 Pools

2 TB (DOS) for NSS32 and NSS64 Pools

NOTE:The pools are currently limited to 8 TB for NSS32 and 8 EB for NSS64, RAID1 sizes for pool objects are also limited to 8 TB or 8 EB depending on the pool type.

Minimum software RAID segment size

12 MB per segment

Maximum partition size

8 TB for NSS32 and 8 EB for NSS64 pools

Valid Range: 12 MB to 8 TB for NSS32 pools, and 12 MB to 8 EB for NSS64 pools

NOTE:The Maximum segment size corresponds only to GPT partition. If all devices are partitioned using DOS, the size limits to 2TB.

Maximum number of partitions per pool

No practical limit

Maximum pool size

8 TB for NSS32 pools

8 EB for NSS64 pools

Minimum pool size

12 MB

Maximum size of a volume

Up to 8 TB for NSS32, depending on the pool size and available space in the pool.

Up to 8 EB for NSS64, depending on the pool size and available space in the pool.

Maximum file size

Up to 8 TB for NSS32, depending on the volume size and available space in the volume.

Up to 8 EB for NSS64, depending on the volume size and available space in the volume.

Maximum number of files per volume

Up to 8 trillion, regardless of how many name spaces are loaded.

NOTE:NSS can support this. You are limited by the browser and application ability, of course.

Maximum number of files open concurrently

No practical limit on the number of files open concurrently.

If any number is limited, it might be because of the system, file access protocols or any similar configuration. Other factors such as system resources can also influence this number.

Maximum number of volumes per server

No practical limit on the number of NSS data volumes.

Time to mount a volume

Requires only a few seconds, thanks to journaling.

Volume name space

Accommodates all name spaces (DOS, Macintosh, Long, and UNIX). Long is the default name space.

The Lookup Name Space attribute allows you to set the default name space used when mounting volumes.

Directory names and filenames are case insensitive with the Long name space.

Minimum server memory required to activate a volume

Requires only 4 MB available RAM to activate a single volume of any size and any number of files. Loads a file’s metadata into memory only as you access the file.

File access time

Same for each file, regardless of its location on the volume.

Error correction and data recovery time on system failure

Journaling file system logs changes.

On system failure, replays the most recent transactions to confirm validity, then repairs errors or rolls back to the original condition, typically in 15 to 60 seconds, unless the volume is corrupted.

Repair of corrupted pools and volume

Ongoing journaling of the file system; if the pool metadata structure is corrupted, use the RAVSUI utility to verify and rebuild the volume.

Time to repair corrupted volume

From a few seconds to several hours, depending on the volume size.

Multiple connection paths to storage media

Use a native Linux multiple path I/O solution.

Software RAID support

RAID 0 (striping)

RAID 1 (mirroring)

RAID 5 (striping with parity)

RAID 0+1 (mirroring RAID 0 devices)

RAID 5+1 (mirroring RAID 5 devices)

Volume encryption

Yes

You must mount encrypted volumes only from NSSMU on the first mount after a system reboot so that you can enter the password. The NSSCON utility does not support entering a password from the command line.

Data shredding

Yes, up to 7 times

File compression

Yes

Data migration

Yes

Directory quotas

Yes

User space quotas (user space restrictions)

Yes

Salvage or purge deleted files, directories, or volumes

Yes

Transaction Tracking System (TTS)

Not supported.

If you need content tracking and trustee support, use NCP volumes on Linux reiser, XFS, or ext3 file systems, then set the file system’s journaling mode to the Journaling option.

Read ahead blocks

Yes

File save time

Provides the group write options and timers. For information, see Section 28.3, Configuring or Tuning Group I/O.

File-level snapshot

(make a temporary snapshot copy of an open file for backup)

No

Modified File List

Yes

Pool snapshot

(retain point-in-time version of a pool using block-level copy on write)

Yes

The stored-on pool must be on a separate partition.

Pool snapshots are not supported for clustered NSS pools on Linux.

Backup systems support

OES 2023: Storage Management Services Administration Guide for Linux

For an overview of backup resources on Linux, see Section 27.0, Managing Backup and Restore for Data and Trustee Information.

Distributed File Services for moving and splitting NSS volumes

Yes

OES Archive and Version Services

Yes

Device maintenance support

Activate and deactivate devices by pool.

CD and DVD device recognition

No; use Linux POSIX file system options instead.

CD and DVD image files

No; use Linux POSIX file system options instead.

Ability to access DOS partitions on the NetWare server

No; use Native Linux file system options instead.

Operating system version detection

Default process

Cache balancing for NSS cache buffers

Yes; for information, see Tuning NSS Performance.

Tuning I/O write behavior

Set group I/O write parameters for NSS on Linux. For information, see Configuring or Tuning Group I/O.

Dynamic Storage Technology (DST)

For information about NSS volume attributes and features that are supported in DST shadow volumes, see Using NSS Volumes in DST Shadow Volume Pairs in the OES 2023: Dynamic Storage Technology Administration Guide.

DST supports NSS volumes on OES 2015 or later servers as the primary or secondary volume in the shadow volume.

For information, see the OES 2023: Dynamic Storage Technology Administration Guide.