Not sure if it would work, but DFS could be a possibility - then you won't have to use LUNs. Create a hidden CIFS share on the FAS and mount it on a Windows server with DFS.
The better solution is to educate those that don't know or understand how ONTAP works in a Windows network. That will take time, so maybe DFS can help buy that time and not unnecessary complication on the appliance.
On Sat, 2008-02-23 at 19:01 +0100, Milazzo Giacomo wrote:
Hi toasters,
I've a customer who's planning to adopt a FAS2020 with a lot of SATA space to use it for Windows file servicing (user data, roaming profiles...) BUT, here's the "but" he has to map this space with a LUN to a new physical server running W2K3 because, the people who manage his infrastructure "want to see" a "real" Windows server...I've explained him that they can manage roughly all using the MMC but he said me that they want to "see" services, RDP and so on :-(
So the only way you know, is to create some LUN and assign as drive or mount point (anyway this could make easier data migration using maybe Windows DFS etc...)
But I would to focus your attention to the NetApp side of issue: snapshots... You know that a volume containing some LUN has to have at least a size double of the LUN, when you create it using Snapdrive the size is autocalculated answering "y" or "n" to that question "do you want to reserve..." I'm asking myself what sense could have to take snapshots of a LUN for a file server usage (not a db!) and after all, what's the sense to restore a volume, so that an entire LUN...so that an entire windows disk!!! Maybe with inconsistencies too...
Another question: I've never had the change to try it...can I use Microsoft VSS options to make a little bit of versioning on this disks coming from NetApp LUNs?
And now the big issue. This customer want to reply using Snapmirror on a remote 2020, so I need snapshots area, so do I have to create a volume DOUBLE of those LUNs size? Or in this case the default of 20% or less is enough?
As usual, many thanks!