DFS Replication DAS VS SAN?


hello,

we have 1 doubt best implementation of dfs replication solve exponential growth of data our company has experimented.

now have 2 branch office (barcelona , madrid) , have 1 storage server support current work files. 2 servers twin , have 1.36 tb mounted 5 array level , replicating mesh topology 24 h window. servers reaching limit of storage capacity , want implement best scalability , performance solution .

our doubt next information tested scalability dfs replication, realized microsoft engineers:
  • a volume can contain to 8 million replicated files, , server can contain 1 terabyte of replicated files.
what want "a server can contain 1 tb of replication files"?
  • that server contain root of dfs can manage 1 tb of replication files possible server use 1 lun of 1 tb , other server other lun of 1 tb, both located same san (iscsi connection) or physical machine storage files can have 1 tb of available space.

i know best:
  1. to put 2 servers. 1 server in barcelona , other server in madrid. solution want next year having 2 servers more, , gowing ... have 1 server more backup every main storage server.
  2. to put 2 san (one in barcelona , other in madrid) storage size required in moment,  put 2 servers , manage new lun, , put data of old servers other lun , map lun server. old server , new server of every branch office manage replication files of our mapped lun , internal storage can used backup mapped lun.
the solution 2 involving san storaging more 1 tb of information replicating dfs replication technology.

thank helping.




ivan fraixedes

ivan fraixedes said:

our doubt next information tested scalability dfs replication, realized microsoft engineers:

  • a volume can contain to 8 million replicated files, , server can contain 1 terabyte of replicated files.
what want "a server can contain 1 tb of replication files"? 

a: actually, not hard limit on number of files can replicated. detailed information, may find explanation dfs replication program manager via following link (microsoft storage team blog)

 

more on dfs replication limits

http://blogs.technet.com/filecab/archive/2006/02/09/more-on-dfs-replication-limits.aspx

 

understanding dfs replication "limits"

https://blogs.technet.com/filecab/archive/2005/12/12/415942.aspx



  • that server contain root of dfs can manage 1 tb of replication files possible server use 1 lun of 1 tb , other server other lun of 1 tb, both located same san (iscsi connection) or physical machine storage files can have 1 tb of available space.

a: theoretically, possible make server1 , server2 (which located in 2 different sites) use lun1 , lun2 belongs same san. however, not recommend perform this. because iscsi san depends on tcp/ip network, may need verify network devices between 2 sites (barcelona , madrid) support iscsi protocol. meanwhile may confirm iscsi related port not blocked on firewall between 2 site. moreover, need ensure network stability make servers connect lun continuously. in way, consideration of business consistency, if possible, i'd suggest implement second proposal.




  1. to put 2 san (one in barcelona , other in madrid) storage size required in moment,  put 2 servers , manage new lun, , put data of old servers other lun , map lun server. old server , new server of every branch office manage replication files of our mapped lun , internal storage can used backup mapped lun.
hope explanation helpful.




david shen - msft


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

DCOM received error "2147746132" from...

DFSR RPC replication errors 5014 1726 with large files over VPN

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B