I am in process of accomplishing a proof of concept of CIFS configuration and data migration services on IBM N series. The case history is as follows.
The customer is aiming to migrate the existing file server data from 3 node cluster to N series CIFS shares. The file server infrastructure is deployed also the DFS services. Some of the folders links are directly mapped to some share folders and some of the folders are just linked using DFS rules. The customer is also wanting to have DR for CIFS services. The failover should ensure that the CIFS services will resume from DR storage using production IP/FQDN.
We have proposed N series vFiler feature running with AD integrated CIFS services. To address the "DFS link emulation in CIFS" , widelinks are considered to implement. Be noted that the customer environment have very few DFS link translations rules the count is not more than 10.
The vFiler also configured with DR parameter and all volumes are replicating through snapmirror.
The Widelink are not working as expected. Although the widelink rules and configuration has already been tested in a demo environment on a NetApp simulator. But when it comes to run on actual vFiler it was not working at all.
Need your support to have answers of following questions.
1- What is the best way to simulate DFS kind of rules in NetAapp CIFS. As I understand sofar the widelinks is the answer
2- Can widelink redirect the user request to another folder (qtree) with in the same volume?
3- Can widelink be used to redirect user request from one share folder to another share folder with in same qtree or volume?
I think your symlink.translations syntax is off. The 1st argument should me the target of the symlink, and the 2nd should be the share to redirect to.
I'm unfamiliar with the netap_symlink.exe command, but assuming that it is like the unix ln command, it should be netap_symlink.exe <link_to_create> <existing_file_to_link_to>. So your 1st arg to Widelink should be the second arg to the symlink command.