IMHO you can run CIFS out of your common, multi-tier pool, if you do not have a LOT of CIFS data. Sure a lot is ambiguous, sorry. I believe the "correct" way is to dedicate spindles to file, but it is not a hard requirement. I carve file up out of my "block" pool for smaller deployments all the time. If you decide you want to, simply carve up pairs of LUNs to make up the total you need. I peg mine to the lowest tier, NL-SAS, during creation and then set them to "No Data Movement". You then add each LUN to each SP, so if you wanted 100G file system, then carve two 50G LUNs and put one on SPA and one on SPB. Then add the LUNs to the ~filestorage Storage Group. Once that is done, you can go to "Storage / Storage Pools for File", then click on the wizard on the right "Rescan Storage Systems". This makes the LUNs you created avail for File. Then create a filesystem, CIFS server, and CIFS share. BTW, if you ever plan to replicate the CIFS data, make sure you create a virtual data mover (VDM) as this is necessary to replicate the environment. Hope this helps.
kelleg
6 Operator
•
4537 Posts
424
0
Posted February 13th, 2012 09:00
Have you looked at the Best Practices guides for VNX? These can all be found on PowerLink at the following location:
Home > Products > Hardware/Platforms > VNX Family > White Papers
EMC Unified Storage Best Practices for Performance and Availability - Common Platform and Block Storage 31.5 — Applied Best Practices.pdf
EMC Unified Storage System Fundamentals for Performance and Availability.pdf
EMC VNX Virtual Provisioning — Applied Technology .pdf
glen