2017-02-22 01:24 AM
is there a way to limit the path length for cifs shares in data ontap (currently running 8.3.2P4)?
We've problems with our Intellisnap Backup on miltiple cifs shares cause of pathes > 260 digits.
As workaround we've configured Intellisnap to skip the catalog phase.
My idea was to limit the path length to < 260 digits for future cifs shares.
Is there any way to realise this?
Solved! SEE THE SOLUTION
2017-02-26 10:12 PM - edited 2017-02-26 10:14 PM
You can use a vscan server to setup path length limit. Refer http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=107770
2017-03-30 02:47 AM
thats a great idea, cause of Company requirements virus scanning
of our cifs shares is already enabled, but the requirement is to disable
mandatory scan. We had some issues with enabled mandatory scan in the past.
Is there a other way to limit path length?
2017-03-30 04:48 AM
By design the windows client will not allow the users to create / move files or folders that commulate to such long path.
when does it allow it? when it' can't determine it.
So you need to aim for having the Intellisnap to use the same path or shorter one then what the client uses. either by different share name. not using FQDN. setup a cname. get somehow Intellisnap to mount it, or maybe change how the clients accessing it to be long enough for windows to block it.
if you try to limit the path in the filer itself, that again relative to how the filer see the path, and not 1:1 match to how the user and not how Intellisnap exactly see it (unless you hard code it in your solution whatever it will be) .