Novell Distributed File Services (DFS) is installed automatically as part of the NSS file system. Dynamic Storage Technology supports using DFS junctions on the primary NSS volume in a shadow volume pair. The primary volume can also be the target of a junction. Primary NSS volumes that contain DFS junctions or are junction targets can reside in an Novell Cluster Services cluster.
DST does not support using DFS junctions on the secondary volume. The secondary volume cannot be the target of a junction.
Junctions that are created on a primary NSS volume behave normally as they would for a single NSS volume. The policy enforcer is designed to prevent junctions from being moved between the primary and secondary volumes when policies are run.
Table 5-4 summarizes the supported DST configurations for use with DFS:
Table 5-4 DST Support for Novell DFS Features
|
Novell DFS Features |
Primary NSS Volume |
Secondary NSS Volume |
Cluster |
File Access Protocol |
|---|---|---|---|---|
|
Junctions |
Yes |
No |
Yes |
NCP Novell CIFS. DFS support must be enabled in CIFS. See Linux Samba does not support DFS junctions for NSS volumes. |
|
Junction targets |
Yes |
No |
Yes |
Not applicable |
|
Move/split volumes |
No |
No |
No |
Not applicable |
When you use DST shadow volumes in combination with Novell DFS junctions, consider the following caveats:
Junctions are broken when they reside on secondary NSS volumes. If you use an existing NSS volume as a secondary volume, delete junctions on it before you create the shadow volume pair. Make a note of the paths of the junctions and their targets. After the shadow volume pair is working, you can re-create the junctions in the same path on the primary volume.
If you use an existing NSS volume as a secondary volume, any junctions pointing to it are broken when you create the shadow volume pair. You must create a new junction that points to the same location on the primary volume of that shadow relationship. After the new junction is working, delete the junction that points to the secondary volume.
Do not create a shadow relationship for an NSS volume if a DFS move volume or split volume job is in progress.
You must remove the shadow volume before you start a DFS move or split volume job.