Home
%3CLINGO-SUB%20id%3D%22lingo-sub-423175%22%20slang%3D%22en-US%22%3EMore%20on%20DFS%20Replication%20Limits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-423175%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Feb%2009%2C%202006%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20A%20customer%20recently%20asked%20us%20to%20clarify%20the%201-TB%20DFS%20Replication%20limit%20described%20in%20an%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Ffilecab%2Farchive%2F2005%2F12%2F12%2F415942.aspx%22%20mce_href%3D%22http%3A%2F%2Fblogs.technet.com%2Ffilecab%2Farchive%2F2005%2F12%2F12%2F415942.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20earlier%20post%20%3C%2FA%3E%20.%20Shobana%20Balakrishnan%2C%20our%20DFS%20Replication%20program%20manager%2C%20explains%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20There%20are%20no%20architectural%20underpinnings%20of%20the%201TB%20limit%20%E2%80%93%20it%20is%20merely%20what%20we%20tested.%26nbsp%3B%20The%20Jet%20limits%20are%20much%20larger.%26nbsp%3B%20The%20theoretical%20limit%20comes%20from%20the%20number%20of%20files%20under%20a%20volume%20scope%20due%20to%20Jet%20limits%20and%20of%20course%20recovery%20times.%26nbsp%3B%20Theoretically%20the%20Jet%20DB%20can%20grow%20as%20large%20as%2032%20TB%20and%20assume%20%C2%BC%20used%20for%20ID%20records%20-%26gt%3B%208TB.%20Assuming%20an%20ID%20record%20is%201KB%20worst%20case%2C%20that%20is%208*10%5E9%20files%20on%20the%20volume.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20On%20a%20practical%20note%2C%20we%20have%20tested%20over%2050%20million%20files%20taking%20approx%201%20TB%20of%20disk%20space.%20The%20database%20in%20this%20case%20was%20approx%2020%20GB.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20I%20should%20also%20clarify%20bullet%20(5)%3A%20A%20replication%20group%20can%20contain%20up%20to%20256%20members.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20This%20is%20actually%20not%20a%20global%20replication%20group%20limit.%20A%20replication%20group%20can%20be%20arbitrarily%20large%20scaling%20to%20several%20thousands%20of%20members.%26nbsp%3B%20Each%20member%20must%20however%20only%20be%20connected%20to%20at%20most%20256%20partners%20-%20and%20actually%20this%20translates%20to%20bullet%20(3)%20where%20each%20server%20should%20have%20at%20most%20128%20partners%20(replicating%20in-and%20out).%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CP%3E--Shobana%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-423175%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Feb%2009%2C%202006%20A%20customer%20recently%20asked%20us%20to%20clarify%20the%201-TB%20DFS%20Replication%20limit%20described%20in%20an%20earlier%20post.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-423175%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edfs%20replication%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Not applicable
First published on TECHNET on Feb 09, 2006
A customer recently asked us to clarify the 1-TB DFS Replication limit described in an earlier post . Shobana Balakrishnan, our DFS Replication program manager, explains:

There are no architectural underpinnings of the 1TB limit – it is merely what we tested.  The Jet limits are much larger.  The theoretical limit comes from the number of files under a volume scope due to Jet limits and of course recovery times.  Theoretically the Jet DB can grow as large as 32 TB and assume ¼ used for ID records -> 8TB. Assuming an ID record is 1KB worst case, that is 8*10^9 files on the volume.

On a practical note, we have tested over 50 million files taking approx 1 TB of disk space. The database in this case was approx 20 GB.

I should also clarify bullet (5): A replication group can contain up to 256 members.

This is actually not a global replication group limit. A replication group can be arbitrarily large scaling to several thousands of members.  Each member must however only be connected to at most 256 partners - and actually this translates to bullet (3) where each server should have at most 128 partners (replicating in-and out).

--Shobana