ONTAP Discussions

Limit cifs path length in ontap 8.3.2

Tom29

Hi folks,

 

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?

1 ACCEPTED SOLUTION

GidonMarcus

Hi

 

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) .

 

Gidi

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK

View solution in original post

3 REPLIES 3

Sahana

Hi,

 

You can use a vscan server to setup path length limit. Refer http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=107770

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Tom29

Hi,

 

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?

GidonMarcus

Hi

 

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) .

 

Gidi

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK

View solution in original post

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public