When planning your DFS environment, consider the guidelines in this section for the supported combinations of platforms, volumes, and protocols.
DFs junctions point to data that is stored on a different NSS volume or NCP™ volume. Table 8-1 summarizes the requirements for the junction, junction target location, and the users’ file access. Consider the following additional requirements:
Both the junction and junction target servers must use the same file access protocol for users.
You must configure file system trustee rights for users on the junction and the junction target location. For visibility, users must have at least Read and File Scan rights on the target location.
When you create a junction, the target volume or subdirectory must already exist.
Multiple levels of junctions are allowed when the junction points to the root of a target volume, except for Samba users.
IMPORTANT:Samba does not support DFS junctions. When a target volume is configured for Samba, any junctions on the target volume are broken for Samba users.
The junctions on the target volume must also be supported by the protocol the users are using to access data. For example, CIFS users would be able to follow subsequent junctions only if they point to the root of the volume, not to subdirectories.
In the following table, the NetWare® and Linux platforms represent only the explicitly supported versions of NetWare and Linux as defined in Section 3.1, Requirements for OES 2 Services.
Table 8-1 Supported Combinations for Junctions
The DFS task moves data from an NSS volume to a new NSS volume in the same or different pool. If it is a different pool, the destination pool can be on the same server or on a different server in the same DFS management context. Table 8-2 summarizes the requirements for the original and destination servers.
During the move process, the original and destination servers must both use the NCP protocol. Users can continue to access data via NCP or CIFS/Samba in the original location while data is being copied to the new location. After the move, you can configure the destination server to use NCP, CIFS, or Samba, as appropriate for your environment.
IMPORTANT:Samba does not support DFS junctions. If you move a volume from NetWare to Linux, junctions on the volume are broken for Samba users.
After the move is complete, the volume location is automatically updated in the VLDB. This ensures that junctions that point to the volume are not broken. No junctions are created in the move process.
In the following table, the NetWare and Linux platforms represent only the explicitly supported versions of NetWare and Linux as defined in Section 3.1, Requirements for OES 2 Services.
Table 8-2 Supported Combinations for the Move Volume Task
The DFS task splits data from a directory on an NSS volume to a new NSS volume. You can split the volume at any subdirectory. The target location is the root of a new NSS volume. The task does not allow you to split a volume to a subdirectory. Table 8-3 summarizes the requirements for the original and destination server.
During the split process, the original and destination servers must both use the NCP protocol. Users can continue to access data via NCP or CIFS/Samba in the original location while data is being copied to the new location. After the split is complete, a junction is created in place of the directory in the original volume. Users access data in the target location via that junction.
IMPORTANT:Samba does not support DFS junctions. If you split an NSS volume on Linux, the junction works only for NCP users.
Before you split the volume, set explicit trustee rights on the directory that you want to be copied automatically to the junction and the target volume. After the split, you can modify the trustee rights for the junction and target location, as desired. For visibility, users must have at least Read and File Scan rights on the target location.
In the following table, the NetWare and Linux platforms represent only the explicitly supported versions of NetWare and Linux as defined in Section 3.1, Requirements for OES 2 Services.
Table 8-3 Supported Combinations for the Split Volume Task