Skip to main content
RealSharePoint.com

RealSharePoint.com

Go Search
RealSharePoint.com
Other Resources
  

RealSharePoint.com > Posts > How Granularity can Further Optimize Data Replication
How Granularity can Further Optimize Data Replication

So I have a distributed farm topology, spread out across various different locations around the globe. I’m replicating content across the pipe, so that each farm receives a copy of the most updated content, and local users can simply access their local farms to retrieve this content. All is fine and dandy, but how can I further optimize this process? Even if replication processes are executed incrementally, do I still want to propagate over everything? What if only access permissions were changed? For example, our employee manuals are not frequently update on our HR site, yet they are replicated to the respective local farms. However, with multiple changes in HR personnel, the securities and access permissions are updated more frequently than the largely static content.

 

This is where granularity plays a big part when designing an optimal replication plan. You would want to take into consideration the frequency of change of the content, the access permissions, and the associated configurations. What if you only wanted to replicated over updated content types? With an appropriate replication solution that allows you to granularly AND independently select what needs to be replicated over, you will have full control. Not only will this further minimize your bandwidth consumption, but you will be streamlining your replication process to only propagate the assets that need to be moved over.

Comments

There are no comments yet for this post.