I am attempting to create volume mount points to support Microsoft's best practices of 1 database per storage group. I will need about 30 storage groups for my company so obviously mount points are requied. I am running into a problem when I create the mount point using Netapp's Snap drive interface. The mount point is being created on both nodes in the cluster and will failover flawlessly. the only problem is the volume is READ-ONLY. I have worked with Netapp and they have never seen this before and of course are pointing at the OS. Anyone seen this before?

Issue description: The volume appears Read-Only in the CCR Yes, it will require volume mount point for 30 SGs as 2 LUNs per SG 1. When you said Read-Only, you mean it appears Read-Only for exchange task only, or Read-Only for all tasks against the volume, like create/add/remove a file in the volume? 2. Does the symptom show on all volume mount points? Both the LUNs on the active and passive nodes? I suggest that you may test to configure volume mount points based on KB [2003, 2008], and try to reproducethe issuewithout Netapp. In this way, we can isolate the issue to either side (Microsoft or Netapp) However, due to the level of the complexity of the issue, I suggested you to contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently Phone list [US, outside of US]

I resolved the issue by disabling the recycle bin for the root drive of the mount points. Apparently the recycle bin does not recognize mount points and requires you to hold down shift when deleting files. Thus bypassing the recycle bin. This is fine except for the fact I am using Netapp's SnapManager for Exchange that does not have that logic built into it and it requires the ability to move and or delete files. http://support.microsoft.com/kb/319368