Subscribe
Accepted Solution

vfiler limits ?

Currently have a set of 6080's clustered. with about 100TB worth of disk space. My requirement is to share out all that space via cifs to about 20k folks (with about 2% usage at a time) and i was thinking of using vfilers to have a better dr setup. However, can the vfiler handle that many cifs sessions ? or would it be better to run cifs directly on the 6080, and just use snapmirror for DR ?

looking for recommendations here.

Thank you

Re: vfiler limits ?

There is no specific limit per vfiler.. The 6080 limits for the entire controller are in effect and the total number of connections are based on the total of all vfilers.  The 6080 can handle 96k user connections and 384k share connections and that can be split across the entire controller regardless of vfilers.

The default number of vfilers is 11, but you can increase to 65 (reboot needed).  Each vfiler reserves about 400k of ram, so using vfilers (even to the max) won't be noticeable to performance.

So, it makes sense to create source vfilers then you can vfiler dr and have all your cifs shares updated on the target (since the vfiler has its own /etc in the replication).

Re: vfiler limits ?

Cool Scott,

Would you please also share similar vFiler limitation on FAS3250 as well?

Thanks

Henry

Re: vfiler limits ?

65 per controller including vfiler0. So 64 vfilers per controller on top of the physical controller.

Sent from my iPhone 5

Re: vfiler limits ?

Wow Scott,

YOU're quick:>)

Would you please also share your take on put 64 vFiler on a FAS3250 pros/cons as well?

Thanks

Henry

Re: vfiler limits ?

The limit has been unchanged on controllers since it was based on RAM and won't change in 7-mode… most don't go near the 64 limit.