UNSOLVED
P
packetboy2
28 Posts
0
1627
February 12th, 2009 04:00
Maximum CIFS shares per VDM?
Hi,
Does anyone know that the maximum number of CIFS shares supported on a NS-80 using a VDM?
The problem we have is when we put the celerra's in orginally we couldnt use the homedirectory feature and had to go with creating a cifs share for every user (homedirectory) now we are in a migration so each users home directory will now have two cifs shares each we have about 250 users on our NS80 so in total it will be about 500 cifs shares running on a single VDM on an ns 80 will this be OK?
Thanks for the feedback guys..
Packetboy.
Does anyone know that the maximum number of CIFS shares supported on a NS-80 using a VDM?
The problem we have is when we put the celerra's in orginally we couldnt use the homedirectory feature and had to go with creating a cifs share for every user (homedirectory) now we are in a migration so each users home directory will now have two cifs shares each we have about 250 users on our NS80 so in total it will be about 500 cifs shares running on a single VDM on an ns 80 will this be OK?
Thanks for the feedback guys..
Packetboy.
Rainer_EMC
6 Operator
•
8645 Posts
633
0
Posted April 21st, 2009 06:00
no, its per physical data mover / Celerra
from the Release Notes:
Number of CIFS shares
10,000 per Data Mover
40,000 per Celerra
You may notice a performance impact when managing a large number of shares.
I think the performance hit comment is more geared towards administration performance like with Celerra Manager or Windows MMC
If all of these share a visible you might also see an impact when browsing the list of shares- I have an NS42G that has 24,334 shares. The NS42G only has two DMs, one in standby so evidently I'm breaking the rule or best practice here. I can't say I have noticed any issue. Admin options are relatively smooth and the user community hasn't mentioned issues.
Should I be overly concerned here or do we think I am ok to just monitor and proceed cautiously? Can't say I have too much of a choice here besides getting another Celerra. umichklewis_ac7b91
300 Posts
446
0
Posted April 22nd, 2009 06:00
I hope you don't mind me being nosy - I was curious why you couldn't use the home directory feature. We've got just under 10,000 home dirs (on ten filesystems) with M$ Roaming Profiles, which people really seem to like. Is there a performance advantage or other benefit to putting users on each share? Thanks much!Rainer_EMC
6 Operator
•
8645 Posts
634
0
Posted April 22nd, 2009 09:00
if you dont have problems right now I wouldnt worry
of course using the home directory feature to reduce the number of shares is always a good idea - it will also help on the client side burdenRainer_EMC
6 Operator
•
8645 Posts
634
0
Posted April 22nd, 2009 09:00
yeah, we just share root directory and use ABE to "hide" other user's home directories.
I dont think that helps much on the Celerra side - you still have loads of shares
whereas (If I remember correctly) with the Celerra home directory implementation the shares get dynamically created/removed as needed when a user connects
since you typically have less users connected than provisioned the data mover has to maintain less sharesRainer_EMC
6 Operator
•
8645 Posts
303
0
Posted April 22nd, 2009 10:00
thanks - that makes a lot of sense
I keep forgetting that ABE is for directories as well and not just shares- i only have one folder named "HOMEDIR", this folder is shared as HOME. Underneath HOME i have a subfolder for each user that corresponds to their active directory username. ABE is set on share HOME. When user maps their home drive they map to \\server_name\HOME. Once connected they only see their directory, they double click on their username and voila.
Peter_EMC
674 Posts
633
0
Posted February 12th, 2009 05:00
Note: You may notice a performance impact when managing a large
number of shares.
but 500 is nothing to worry about