Source file system settings and network access point |
Destination |
||
|---|---|---|---|
Within the EVS |
Another EVS in the same cluster |
An EVS on another server or cluster |
|
SMB shares |
The path is modified. Clients that had the share mounted before the transfer of primary access do not have to remount the share after the transfer. |
The share is deleted from the source EVS and then added to the target EVS. Clients that had the share mounted before the transfer of primary access must remount the share after the transfer only if the share was not to a directory in the CNS. |
The share is added to the target EVS and then deleted from the source EVS. Clients that had the share mounted before the transfer of primary access must remount the share after the transfer. |
NFS exports |
The path is modified. Clients that had the export mounted before the primary access transfer must mount the export again after the transfer, as the NFS mount becomes invalid after the transfer. |
The export is deleted from the source EVS and then added to the target EVS. |
The export is added to the target EVS then deleted from the source EVS. |
FTP users |
The initial directory is modified. |
The initial directory is deleted from the source EVS and then added to the target EVS. |
The initial directory is added to the target EVS then deleted from the source EVS. |
Snapshot rules |
Where a file system is replicated from root (/) and all data and access points transferred to a new standalone file system. Where a file system is only replicated partially from sub-directories off the root of the file system (/), and only a subset of data and access points are transferred to the target file system, snapshot rules are not deleted and recreated on the target file system. |
||
CNS links |
If CNS entries already point to the replication source, then the CNS link is removed and a link to the new file system is added at the corresponding path. If the file system is linked to the cluster name space at a level higher than the root directory of the file system path being replicated, moving the CNS link is not possible. In such cases, the CNS link is reported as an error in the list of successful and failed transfers. You must manually create a CNS link to the file system in the new location. After a transfer of primary access, network clients will not be able to access the file system through the a CNS namespace if any of the following are true:
To access the file system in its new location, network clients must reconnect through SMB shares or NFS exports pointing to the relocated file system or to a CNS name space into which the file system is linked. NFS clients pointing to a CNS name space will not experience any interruption. Note: If clients will not access the relocated file system using CNS links, they must use new IP addresses to access it.
If transferring primary access to a different EVS, and either the source or destination EVS is using Individual EVS security context, the CNS link cannot be relocated. |
If CNS links exist, the relocation is not allowed to proceed. You must remove the links before proceeding. |
|
The following table describes how network access points on the source file system are moved or deleted: