Has anyone ever setup Widelinks in a CIFS only environment?
We have a FAS 3070 cluster, and I'm trying to re-direct users from a volume on one head to a volume on a different head (or possibly even on the same head). I was able to do this using NFS, but our NFS license was temporary, so to create any new ones, I need to do it using CIFS only.
I've read through the following documents, but they have been no help:
A more detailed explanation of what I'm trying to do:
We have several large file systems, over 2 TB each. The users need to be able to go to a single directory within an already established DFS root (which I'll call \\Domain.com\DFSRoot) and see each of these file systems as a subdirectory of that single directory. So, I've created a DFS link within the DFS root... we'll call it TopDirectory that points to a CIFS share/volume on Filer A with the same name. Using NFS, I had to mount that directory to a Unix machine along with all the volumes I wanted to appear as a subdirectory (I'll call them Volume01 - Volume10, and they each reside on Filer B). From the Unix machine, I then ran the command ln -s /mnt/Volume01 /mnt/TopDirectory/Volume01 for each of the volumes that I want to appear as subdirectories. This created a symbolic link for each of the directories within the TopDirectory volume.
Then I had to edit the /etc/symlinks.translations file on Filer A so that the symbolic links would point to a share on Filer B. So, the entries would look like this:
My question now is, how can I create the symbolic links if I don't have an NFS license? I've been told that I can use ln.exe to create them, but I can't get it to work. The copy of ln.exe that I have was apparently created by NetApp, but their help desk says they do not support it. Apparently there is a version that came with Windows Resource Kit, but I think it was an older version. I think it was replaced with linkd.exe, which I've tried, but I can't get that to work either. I've tested linkd by creating a link on windows server to a different directory, but if I try to use a UNC path, it fails.
Can anyone tell me how to do this, or if it can even be done?
Where/vol/volume09 is the path to the volume on the NetApp, and the second part is the UNC path to the volume/share where you want the symbolic link to be created.Note:You must map a drive to the destination of the link (i.e. \\FilerB\TopDirectory) and CD to that drive/directory before running the ln command, so the ln.exe will need to be in your path. The command will create a symbolic link in "TopDirectory" that redirects to the volume on the NetApp.
Add the following line to the symlink.translations file on the NetApp filer that the symbolic link resides on: Widelink /vol/volume09/* \\FilerB\volume09\*
Interestingly enough, I was also able to get this to redirect to a share on a different server as well.
ln.exe is part of the Windows Resource Kit, but the version I have specifically references NetApp in the help file, so I think I may have gotten a copy of it from our technical sales rep. I looked for a copy of it on NOW, but I wasn't able to find it anywhere.
I recently did a LOT of testing with Widelinks. The ONLY version of ln.exe that I could get to work at all is the version written by Oliver Krause of NetApp. The version I have is dated 2002 and I got it from a friend.
Does anyone know if this utility is being maintained by NetApp? Is Oliver still with the company?
I joined the ln.exe from Olivier Krause we use since 7 years I believe. It works since DOT 6.3 I think. It is not supported by netapp.
I post this ln.exe on now communities some years ago, but netapp change and my thread disapear.
We use it for 2 ways :
In a common share : to create a tree to allow access to every qtrees created on the volumes of the filers of a site + several widelinks to access other common shared localted on filers of differents sites
In "My shared" to create for every user a tree of qtree where a user have access, (it avoid to show to the user leaves where he have no access), on the filer of his site and on the filer of others site in the world.
We have 80 000 users and 100 filers like this.
The common share is also used to show our users, the same view under unix and under Windows. So the widelink we use have a meaning under unix too.
Using wireshark, you see when the workstation access the widelink, the filer send a DFS referal and then, the workstation access only to the target for the next access.
Microsoft on Windows 7/Windows 2008 provide mklink.exe to create a similar function. But if you made an wireshark trace you see that the workstation always access to the "link" before accessing to the target, so you get two requests instead of two. Even if SMB V2 is less chatty globaly, it's not optimized.
So Widelinks + SMB V2 is the best choice.
In fact, widelinks allow to create a global namespace.
(where XXXX is the name of the symlink file you will create in step 5b)
4) From a windows box (you must obtain a Windows binary port of the ln.exe command so that you can use the UNIX-like path that lives on the filer, or use the ntap_symlink, which seems to use OnTap's RESTful API over HTTP):
5a) Authenticate to the filer by mapping a drive:
net use p: \\FILER\_test$
5b) Create the symbolic link using the windows binary port of ln.exe:
ntap_symlink -l USER FILER /vol/VOLUME/_foo/XXXX/ /vol/VOLUME/_foo/XXXX
That was the most useful information I've been able to find anywhere on making Widelinks work! Thank you!
Now the trick question. Is it at all possible to make the entire CIFS share itself a Widelink?
Let me explain my need, I suppose.
We have a couple of particularly large fileservers with many shares on each server - some as many as 600 shares, including user shares. We want to migrate these fileservers over to the filer, naturally. But given the amount of data in question, a single forklift of the entire server and all shares at one time isn't practical. What would be ideal would be initially moving the hostname by DNS alias to the filer, and setting up a Widelink for each share that points back to the old server for the actual data. Then we go share by share migrating data and replacing the widelinks with actual data. If a Widelink can be created as the entire root of a filer CIFS share, that would be perfect. Otherwise, I'll have to create all of the CIFS shares to match the old fileserver, then create a Widelink beneath each share for each and every top level directory target. That's a bit daunting, but not necessarily a complete showstopper.
Shanehoover, have you had any luck getting this to work? I can try to help you out if I can, but I'm not sure I completely understand what you're trying to do. I can tell you that I have been able to create a volume on the NetApp that contained Widelinks to other volumes on the same filer and to a share that I had setup on our Celerra. So, it looked something like this:
Folder (A small volume on the NetApp)
SubFolder1 (A link created in "Folder" using the ln.exe tool, and redirected to a share on the same filer using the Widelinks entries)
SubFolder2 (A link created in "Folder" using the ln.exe tool, and redirected to a share on another filer using the Widelinks entries)
SubFolder3 (A link created in "Folder" using the ln.exe tool, and redirected to a share on a Celerra using the Widelinks entries)
It sounds like you want to have some real subfolders (ones that have been migrated), mixed in with other subfolders that are actually Widelinks back to the original server until they are migrated. I don't see why you wouldn't be able to do that.