8.4 Guidelines for Junctions

Use the guidelines in this sections for planning for the junction and target volumes for DFS junctions.

8.4.1 Junction Volumes

The volume where the DFS junction resides must be an NSS volume on one of the following supported operating systems (or later versions):

  • OES 2 Linux and NetWare

  • OES 1 NetWare (DFS is not supported on OES 1 Linux.)

  • NetWare 6.5

IMPORTANT:A junction does not work if you mount its NSS volume on a server running an unsupported platform.

8.4.2 Junction Target Volumes

The target volume must be an existing volume within a DFS management context. For a DFS junction, the target volume can be an NSS volume or an NCP volume (an NCP share on a Linux traditional volume). When moving or splitting volumes, only NSS volumes are supported as target volumes.

The target volume for a junction can be an NSS volume on the following platforms:

  • OES 2 Linux and NetWare

  • OES 1 SP3 NetWare

  • OES 1 SP2 Linux

  • NetWare 6.5 SP7

The target volume for a junction can be an NCP volume (an NCP share on an Ext3 or Reiser file system) on an OES 2 Linux server.

Target volumes cannot be non-NCP Linux volumes primarily for security reasons such as enforcing file system trustees, rights, inherited rights filters, and file attributes. In addition, the target volume must be represented by a Volume object in Novell eDirectory in order to be tracked by the VLDB. Volume objects are created automatically in eDirectory when you create an NSS volume or an NCP volume.

8.4.3 Junction Target Directory

When using NSS volumes as the target volume and NCP as the file access protocol, a junction can point to the root of the target volume or to an existing directory on it. Users must use the latest version of the Novell Client.

8.4.4 Junctions

When planning and managing junctions, consider the following guidelines:

  • The junction’s volume and the target volume must be in the same Novell eDirectory tree.

  • Junctions can exist in or out of a DFS management context. If a junction is in a DFS management context, the context can be the same or different than the one for the target volume.

  • The target volume must be in an existing DFS management context where an instance of its VLDB service is up and running.

  • Before creating a junction, make sure the source and target volumes are mounted and active.

  • Junctions can be created only in existing directories. Make sure to create the directory path before attempting to create the junction.

  • Junctions can point only to existing volumes or existing directories. Make sure the target volume or target directory exists before attempting to create the junction.

  • The users must be defined with User objects in Novell eDirectory in order to be available as potential trustees. You can add trustees to a junction or junction target at any time.

  • Both the junction and target locations inherit trustees and trustee rights relative to their actual locations in accordance with the Novell Trustee Model. You must set explicit rights on the two locations to block any rights that you do not want to be inherited.

    For information about the Novell Trustee Model, see Understanding File System Access Control Using Trustees in the NW 6.5 SP8: File Systems Management Guide.

8.4.5 Creating Junctions in a Cluster Environment

If the volume you want to use as a junction or a target is in a clustered pool, and the pool is not on the pool’s original node, then the volume does not appear in the list of available volumes under the Cluster object or under a currently active node’s Server object. (This is a known defect and is planned to be resolved in a future release.) In order to create a junction on a clustered volume or to target a clustered volume, that volume’s pool must be currently active on the cluster node where the pool was originally created. After the junction is created, the pool and its volumes can fail over as usual without breaking the junction.