Windows 2008 R2 File Server Cluster vs. DFS

Solution 1:

http://blogs.technet.com/b/filecab/archive/2006/09/22/457319.aspx anaswers your question on quota behaviour on cluster nodes. Note this is for FSRM quotas. FSRM and NTFS quotas are apparently different. See http://support.microsoft.com/kb/915042. Which do you have? Also see http://technet.microsoft.com/en-us/library/cc770989(WS.10).aspx#BKMK_FSRMvsNTFS

Without wanting to sound like marketing I'd like to say DFS and clustering are complementary technologies. Clustering is for those that want quick recovery from server (node) failure. DFSR is for keeping multiple copies in several places in sync. This is why DFSR is supported on clusters starting with 2008 R2. See http://blogs.technet.com/b/filecab/archive/2009/01/19/dfs-replication-what-s-new-in-windows-server-2008-r2.aspx .

What are the issues you have with replicating permissions? Did you pre-seed content in supported ways before creating RG/RF? I wonder if a robocopy usage issue is the cause fo your permissions issue. See http://blogs.technet.com/b/askds/archive/2010/09/07/replacing-dfsr-member-hardware-or-os-part-2-pre-seeding.aspx

Solution 2:

Clusters work by moving actual NTFS volumes between nodes, so there isn't any replication needed. All of the data, which includes all of the metadata like ACLs, moves as a whole. Because of this, all rights and quotas (directory and user) follow the volume, as well as any Shadow Copy settings you may have on there. Unlike DFS, you can't mount the same data multiple places, it's always served by a single node. That node can change, but it is always one node.