I'm trying to find info on creating a symlink between two different shares on the same vserver.
Example:
I want to have \\vserver1\share1\folder by a symlink to \\vserver1\share2. Is there any documentation on how to do this if it's allowed? I know there's limitations on widelinks with MacOS clients, so trying to prevent using that if at all possible.
#Symlinks and different shares
1 messages · Page 1 of 1 (latest)
This might be a good place to start - https://kb.netapp.com/onprem/ontap/da/NAS/How_to_make_symbolic_links_(widelinks)_work_for_CIFS_clients_on_Clustered_Data_ONTAP
exactly, "widelinks" is the keyword to search for. It uses DFS redirects on CIFS, and absolute paths on NFS (so for it to work on NFS you need to mount all volumes at the same mount point on all clients)
Can you solve this with junction paths? I haven't tried this with CIFS but with NFS a junction-path mount should work.
Unfortunately we're trying to do SMB shares and widelinks are not supported on SMBv2 currently on MacOS. We ended up doing a lazy approach by making a windows shortcut and a macos alias to point to the share for our users and it just redirects for them. Not the most elegant solution, but did the job for us. So \\vserver1\share1\folder - windows link and \\vserver1\share1\folder - macos link. Unfortunately I don't have direct access to the OnTap instance to play around with to many settings as I'm in a university environment and central IT department is cautious on turning on/off various settings to play around with this as our use case for them has never come up before. So the above workaround got us where we needed to be. Thanks for all the pointers.
Widelinks should be supported by MacOS clients. Is there a KB, document, or something that says they are not? If so, can you provide it?
you could just use a flexcache volume and mount it in the right place too, probably
About this task
Widelinks are not accessible from Mac OS X clients if you use SMB 2.x. When a user attempts to connect to a share using widelinks from a Mac OS X client, the attempt fails. However, you can use widelinks with Mac OS X clients if you use SMB 1.
Why not use NFS?
Thanks for that. I know that there have been issues with different Mac OS versions over the years, such as Mac OS X that is mentioned in the documentation you provided. I can try to get some testing done to confirm what I see, but I thought this had gotten better with more recent macOS versions. I am fairly certain that we have customers using widelinks with Mac clients, and I highly doubt they are using SMB1.
We've got systems that rely on SMB shares due to legacy windows integration and certain apps.
If it's supported in newer MacOS versions, that would be great to have the documentation updated to mention it. The admins of our NetApp environment saw that and decided it wasn't even worth trying to see what would happen. I think they and I both assumed it would also be the case for newer versions of MacOS as well.