DFS redesign ideas?

hi,

basically looking few ideas on how redesign our file servers.

we have multiple physical file servers , few virtual servers , replicated , not quite confusing. total storage size around 6tb made of home directories, , shared resources - no particularly special file types etc. using dfs home directories mean need have single point of reference supported microsoft per:

http://blogs.technet.com/b/askds/archive/2010/09/01/microsoft-s-support-statement-around-replicated-user-profile-data.aspx

what thinking doing consolidating onto 4 servers.

we have large single site few remote sites. remote sites have had links upgraded 1gb , have been removing our server infrastructure these areas due not having environmental/physical space/security in place.

on our main site have 2 separate buildings each contain san (not linked each other).

microsoft's guides show concepts of using dfs failover cluster in main site replication single server @ remote site.

i model in 1 site, due fact have 2 equally sized san's on main site, issue spread load both san's. therefore if have running on single server primary i creating spof.

what thinking of doing create 2 x 2 node dfs failover clusters (one in each building connected building's san).

this means:

• i can load balance primary dfs shares at cluster level (san's)
• rapid failover can occur if needed between individual nodes within cluster
• the single point of failure (storage) in using single dfs cluster eliminated

however not sure if supported or recommended?

not sure if i'm misunderstanding things here, way see have 3 levels @ need provide redundancy

• dfs namespace servers - suggest host these on domain controllers have, actual file load minimal , provide adequate failover.  it has benifit of keeping namespaces under same parent domain.  \\domainname\share\foldertarget
• dfs folder targets - these point shares on actual file servers heavy lifting, 1 copy of each share per san dfs replication keep them in sync.
• the actual file servers - standard cluster running clustered file service role.

this way have each san servering files via 2 node file cluster.  (active/passive)

each file cluster replicating accross other via dfs replication. (active/active)

let domain controllers handle actuall exposing of dfs shares. (active/active)

the issue keeping on top of dfs replication between 2 file server clusters make sure users in same building not see differnet files depending on file server cluster using.

hope helps.

Windows Server  >  File Services and Storage