NSS volumes are automatically mounted by default on system restart in NSS, then in NCP Server. This is the desired behavior for all independent NSS volumes that are not in shadow volumes, and for NSS volumes that you use as primary storage locations in a DST shadow volumes. When an NSS volume is used as the secondary storage area in a DST shadow volume, you want the NSS volume to be mounted in NSS, but not in NCP Server. This allows DST to control access to the secondary storage area via the primary storage area. Files in the secondary storage area cannot be directly accessed by users.
The NCP/NSS Bindings parameter for an NSS volume governs whether the volume is automatically mounted on system restart in NCP Server. When the parameter is enabled, the NSS volume is automatically mounted for NCP Server. When it is disabled, the NSS volume is not mounted for NCP Server. The NCP/NSS Bindings parameter is enabled by default, making the volume NCP accessible.
In the NCP/NSS Bindings dialog, NSS volumes are enabled by default to be
, and have a setting of .For example, if you plan to create a DST shadow volume that uses VOL1 as the primary storage location and ARCVOL as the secondary storage location, set to for VOL1, and set it to for ARCVOL.
After you remove a shadow volume, the NCP/NSS Bindings parameter for the NSS volume that was used as the secondary storage area remains disabled until you enable it. You must enable the bindings and mount the volume in order to enable users to access the now independent volume.
The volume’s NCP/NSS Bindings parameter must be enabled for NSS volumes that you use as primary storage locations in a DST shadow volumes, and for all independent NSS volumes that are not in shadow volumes. This is the default.
In Novell Remote Manager for Linux, select
> .In the
area of the NCP Shares page, click to open the NCP/NSS Bindings page.In the
list, locate the NSS volume that you want to enable.If the volume’s
setting is , click to make the NSS volume accessible to NCP so that the volume is automatically mounted in NCP after it is mounted in NSS.Beneath the volume’s setting for
, click to save and apply the new setting.Verify that the NSS volume is available for NCP by selecting
> to view a list of active volumes.If the NSS/NCP bindings are enabled, the NSS volume appears in the
list, and a button is displayed next to it.If you want users to be able to access the volume at this time, click
.When the volume is successfully mounted, the volume’s name is hyperlinked, and an
button is displayed next to it.The volume’s NCP/NSS Bindings parameter must be disabled for NSS volumes that you use as secondary storage locations in a DST shadow volumes.
In Novell Remote Manager for Linux, select
> .In the
area of the NCP Shares page, click .In the
list, locate the NSS volume that you want to disable.In the
column, click to make the NSS volume not accessible to NCP so that it is not mounted in NCP after it is mounted in NSS.Beneath the volume’s setting for
, click to save and apply the new setting.Verify that the NSS volume is not available for NCP by selecting
> to view a list of active volumes.If the NCP/NSS bindings were successfully disabled, the NSS volume should not appear in the
list.