A.13 NSS Media Upgrade Commands

Use the commands in this section for managing AD, Trustee Index and hard links media upgrade.

A.13.1 NSS Media Upgrade Commands

This section provides the commands to upgrade the NSS pools to AD or Trustee Index media.

AD Media

When an NSS32 pool is migrated to OES 2015 or later, all its active volumes are automatically media upgraded to support hard links. For more information, see Automatic Hard Link Media Upgrade

All NSS32 pools must be AD media upgraded in order to support AD users. NSS64 pools are by default Trustee Index media (includes AD media) upgraded. Use the commands in this section to upgrade the existing NSS32 media to support AD users or to enable all future NSS32 pool creation to be automatically created with the AD user support.

For the Existing NSS Pools

nss /PoolMediaUpgrade=poolname /MediaType=AD

Upgrades the specified NSS pool to support AD media.

NOTE: Media upgrading a shared NSS pool in a mixed-node cluster environment is not recommended. You can still force the upgrade using the /ForceMedia switch. After the forceful media upgrade, the pool will not load in nodes older than OES 2015.

The following commands can also be used to upgrade the existing NSS32 pool media to support AD users.

nss /ZLSSUpgradeCurrentPoolMediaFormatToAD=poolname

Upgrades the file system media format of a particular NSS32 pool to support AD users.

nss /ZLSSUpgradeCurrentPoolMediaFormatToAD=all /include=shared

Any NSS32 shared pools created after running this command will be AD media enabled.

nss /ZLSSUpgradeCurrentPoolMediaFormatToAD=all /include=local

Any NSS32 local pools created after running this command will be AD media enabled.

nss /ZLSSUpgradeCurrentPoolMediaFormatToAD=all

Any NSS32 pools (shared or local) created after running this command will be AD media enabled.

NOTE: Media upgrading a shared NSS32 pool in a mixed-node cluster environment is not recommended. You can still force the upgrade using the /ForceADMedia switch. After the forceful media upgrade, the pool will not load in nodes older than OES 2015. For more information, see Behavior of an NSS Pool Resource with Media Version 44.03 and Above in Mixed Node Cluster in the OES 2018 SP1: Novell Cluster Services for Linux Administration Guide.

For the Newly Created NSS Pools

The commands placed in the nssstart.cfg file persists across server reboots. If the NSS commands are added in the nssstart.cfg file, ensure those commands are not prefixed with nss.

If these commands are issued from the command line, it persists only till a server reboot.

nss /NewPoolMediaFormat=AD /include=all

Sets the file system media format of all the newly created pools (shared or local) to support AD media.

nss /NewPoolMediaFormat=AD /include=shared

Sets the file system media format of all the newly created shared pools to support AD media.

nss /NewPoolMediaFormat=AD /include=local

Sets the file system media format of all the newly created local pools to support AD media.

NOTE: Media upgrading a shared NSS pool in a mixed-node cluster environment is not recommended. You can still force the upgrade using the /ForceMedia switch. After the forceful media upgrade, the pool will not load in nodes older than OES 2015.

The following commands can also be used to enable all future NSS32 pool creation to be automatically created with the AD user support.

nss /ZLSSUpgradeNewPoolMediaFormatToAD=all

Upgrades the file system media format of all the newly created NSS32 pools (shared or local) to support AD users.

nss /ZLSSUpgradeNewPoolMediaFormatToAD=all /include=shared

Upgrades the file system media format of all the newly created NSS32 shared pools to support AD users.

nss /ZLSSUpgradeNewPoolMediaFormatToAD=all /include=local

Upgrades the file system media format of all the newly created NSS32 local pools to support AD users.

NOTE: Media upgrading a shared NSS32 pool in a mixed-node cluster environment is not recommended. You can still force the upgrade using the /ForceADMedia switch. After the forceful media upgrade, the pool will not load in nodes older than OES 2015. For more information, see Behavior of an NSS Pool Resource with Media Version 44.03 and Above in Mixed Node Cluster in the OES 2018 SP1: Novell Cluster Services for Linux Administration Guide.

Volume AD-enabling

Use the following commands to AD-enable the volumes. Only after AD-enabling, the AD users will be able to access the NSS resources based on the access rights assignment. Before running these commands, ensure that the pools on which these volumes exist are NSS AD media-upgraded.

nss /ADIdentities=volume_name

AD-enables the specified volume.

nss /ADIdentities=all

AD-enables all the volumes. The volumes whose pools are not AD media-upgraded are ignored.

nss /(No)EnableNewVolumeToAD

Enables or disables the automatic AD-enabling of new volumes.

The commands placed in the nssstart.cfg file persists across server reboots. If this NSS command is added in the nssstart.cfg file, ensure this command is not prefixed with nss.

If this command is issued from the command line, it persists only till a server reboot.

Default: Off

Range: On or Off

Examples

To enable automatic AD-enabling of new volumes, enter

nss /EnableNewVolumeToAD

To disable automatic AD-enabling of new volumes, enter

nss /NoEnableNewVolumeToAD

Trustee Index Media

The Novell Storage Services (NSS) volumes use the Trustee Model to secure access to directories and files. The Trustee Model allows you to assign users as trustees of directories and files on the NSS volumes. The model’s inheritance feature allows the subdirectories and files to inherit rights from a parent directory or masks the rights that should not be inherited. The Trustee Index tree stores the list of directories and files in the NSS volumes that are having trustees and IRF (Inherited Rights Filter). The ZIDs (iNode number) in NSS consists of ACLs (with trustees and IRFs) that are stored in volumes in the Trustee Index tree. These ZIDs helps you to scan the trustee information for OES URM, NFARM, and so on at any given path in the NSS volume. Therefore, NSS requires a media upgrade to pool and volume to support Trustee Index. For more information on Trustee Model, see Section 6.5.3, OES Trustee Model.

Use the nsscon commands in this section to upgrade the existing NSS media to support Trustee Index or to enable all future NSS pool creation to be automatically created with the Trustee Index support.

For the Existing NSS Pools

nss /PoolMediaUpgrade=poolname /MediaType=TrusteeIndex

Upgrades the specified pool to support Trustee Index media.

For the Newly Created NSS Pools

The commands placed in the nssstart.cfg file persists across server reboots. If the NSS commands are added in the nssstart.cfg file, ensure those commands are not prefixed with nss.

If these commands are issued from the command line, it persists only till a server reboot.

nss /NewPoolMediaFormat=TrusteeIndex

Sets the file system media format of all the newly created pools (shared or local) to support Trustee Index media.

nss /NewPoolMediaFormat=TrusteeIndex /include=shared

Sets the file system media format of all the newly created shared pools to support Trustee Index media.

nss /NewPoolMediaFormat=TrusteeIndex /include=local

Sets the file system media format of all the newly created local pools to support Trustee Index media.

NOTE:Media upgrading a shared NSS pool in a mixed-node cluster environment is not recommended. You can still force the upgrade using the /ForceMedia switch. After the forceful media upgrade, the pool will not load in nodes older than OES 2015 SP1.

Pool and Volume Media Version

In NSS32 and NSS64 pool type, the pool status can be determined by the media version. Table A-1 provides information about the NSS32 and NSS64 pool type media version.

Table A-1 NSS Pool Media Version Details

Pool Media Version

Description

XX.YY

  • XX: Denotes the major version of the pool.

  • YY: Denotes the minor version of the pool.

43.02

  • 43: An NSS32 pool that does not support AD.

  • 02: Some volumes are not upgraded to support hard links.

43.03

  • 43: An NSS32 pool that does not support AD.

  • 03: All volumes are upgraded to support hard links.

44.02

  • 44: An NSS32 pool that supports AD.

  • 02: Some volumes are not upgraded to support hard links.

44.03

  • 44: An NSS32 pool that supports AD.

  • 03: All volumes are upgraded to support hard links.

45.00

  • 45: An NSS32 pool that supports Trustee Index.

  • 00: Some volumes are not upgraded to support Trustee Index.

45.01

  • 45: An NSS32 pool that supports Trustee Index.

  • 01: All volumes are upgraded to support Trustee Index.

51.00

  • 51: An NSS64 pool that supports AD by default.

  • 00: All volumes are upgraded to support hard links.

52.00

  • 52: An NSS64 pool that supports Trustee Index.

  • 00: Some volumes are not upgraded to support Trustee Index.

52.01

  • 52: An NSS64 pool that supports Trustee Index.

  • 01: All volumes are upgraded to support Trustee Index.

Similarly, the volume status can also be determined by the media version. Table A-2 provides information about the NSS volume media version.

Table A-2 NSS Volume Media Version Details

Volume Media Version

Description

38.05

  • 38: An NSS volume that supports Hard Link.

  • 05: An NSS volume is upgraded to support hard links.

41.00

  • 41: An NSS volume that supports Trustee Index.

  • 00: An NSS volume is not upgraded to support Trustee Index.

41.01

  • 41: An NSS volume that supports Trustee Index.

  • 01: An NSS volume is upgraded to support Trustee Index.

A.13.2 Automatic Pool Media Upgrade Commands

Use the following command to automatically upgrade the NSS32 and NSS64 pools to latest pool media (Trustee Index). The automatic pool media upgrade happens only if the pool is AD media enabled. Whenever an AD media enabled pool is activated, the pools are automatically upgraded to support latest media.

Media upgrading an NSS32 pool to AD, automatically upgrades the pool to latest media. However, creating an NSS64 pool, will automatically creates the pool with latest media.

The commands placed in the nssstart.cfg file persists across server reboots. If this NSS command is added in the nssstart.cfg file, ensure this command is not prefixed with nss.

If this command is issued from the command line, it persists only till a server reboot.

nss /(No)PoolMediaAutoUpgrade=value

Enables or disables the pool media to upgrade automatically. If enabled, the pools are automatically upgraded to support the latest media (Trustee Index).

Default: Off

Range: ZLSS, ZLSS64, or both (with comma separated)

Examples

To enable the pool media to upgrade automatically for NSS32 pool, enter

nss /PoolMediaAutoUpgrade=ZLSS

To enable the pool media to upgrade automatically for NSS64 pool, enter

nss /PoolMediaAutoUpgrade=ZLSS64

To enable the pool media to upgrade automatically for both NSS32 and NSS64 pool, enter

nss /PoolMediaAutoUpgrade=ZLSS,ZLSS64

To disable the pool media to upgrade automatically for NSS32 pool, enter

nss /NoPoolMediaAutoUpgrade=ZLSS

To disable the pool media to upgrade automatically for NSS64 pool, enter

nss /NoPoolMediaAutoUpgrade=ZLSS64

To disable the pool media to upgrade automatically for both NSS32 and NSS64 pool, enter

nss /NoPoolMediaAutoUpgrade=ZLSS,ZLSS64

NOTE:For clustered pools, the automatic pool media upgrade occurs only in homogeneous cluster environment. For local pools, the automatic pool media upgrade occurs both in homogeneous and mixed-node cluster environment.

A.13.3 Hard Links Commands

Use the commands in this section for managing hard links capability for NSS volumes.

Automatic Hard Link Media Upgrade

When an NSS32 pool is migrated to OES 2015 or later, all its active volumes are automatically media upgraded to support hard links.

Once all the volumes in the pool are upgraded to support hard links, the pool media version is incremented. If there are deleted and inactive volumes, they are not media upgraded; therefore, the pool media version is not incremented. To know the pool media version, execute the PoolMediaVersion command in NSSCON.

Hard Links Attribute Commands

Use the commands in this section to enable or disable the Hard Links attribute for an NSS volume. The Hard Links attribute cannot be set or viewed in NSSMU or in the Storage plug-in to iManager.

nss /HardLinks=volumename

Enables the Hard Links attribute for the specified volume. This enables hard links to be created on the volume.

nss /HardLinks=all

Sets the Hard Links attribute for all NSS volumes on the server. This enables hard links to be created on any volume on the server. Any given hard link can point only to a file on the same volume.

nss /NoHardLinks=volumename

Disables the Hard Links attribute for the specified volume. Existing hard links continue to function, but no new hard links can be created on the specified volume.

nss /NoHardLinks=all

Disables the Hard Links attribute for all NSS volumes on the server. Existing hard links continue to function, but no new hard links can be created on any NSS volume on the server.

Hard Links Management Commands

You can view a report of hard links for a file to identify its primary link and the hard link that becomes the primary link if the primary link is deleted. For information, see Section 25.7, Viewing Hard Links for a File.

/nss /ListHardLinks=vol:path\filename.ext

View information about the primary link and hard links for a file on an NSS volume.

Replace path with the file’s primary link path or one of its hard link paths where you want to start the search. Replace filename.ext with the actual filename of the file, including the extension.

Use the /volumes option to verify that the Hard Links attribute is enabled.

nss /volumes

View a list of NSS volumes on the server and information about them. In the Attributes column, the HardLinks attribute is listed if it is enabled for the volume.