Multiple Primary Sites to avoid OSD binaries replication over WAN

Hi,

We have a situation where our customer does not want any data replication over WAN(specially OSD). They are inclined towards having multiple primary sites to manages OSD locally and are ok with the admin overhead. Can this approach have any  big issues?

Regards..

May 18th, 2015 3:39am

Does that also mean that they want to connect the primary sites via a CAS? If so, that means they still will have a lot of data replication between the CAS and the different primary sites.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 3:44am

Yes, CAS is part of the plan. But data going to CAS from primaries will depend on the number of endpoints per site and should be around 500 kb per client per day. right?

but OSD involves a lot of replication even though at bigger intervals so that's what is the red zone for them for now.

May 18th, 2015 3:49am

It's not just client data that's being synchronized. Please have a look here for more information about the data that's being synchronized: https://technet.microsoft.com/en-us/library/gg712701.aspx#Planning_Inter_Site_Com

Also, please keep in mind that the database replication between a CAS and primary is known for causing problems. If possible, always try to avoid using a CAS.

Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 3:54am

Thanks Peter. But the replication data(Primary-CAS) will still be not that bad to choke a KBPS link as the OSD binaries replication would do. So if we say that we are ok with this and to localize OSD, is it justified to put 10 Primary sites under CAS for 10 sites with slow interlinks.

Regards,...

May 18th, 2015 4:04am

I would say, no. I would look at either scheduling the content distribution, or pre-staged content, rather than a CAS.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 4:07am

"and are ok with the admin overhead"

What about the admin latency that will affect everything that they do as well as the huge perf impact that every additional primary site causes?

I agree with Peter -- this is not a good choice.

Is there a reason they can't do everything centrally using a remote desktop session host and VMs located in close proximity to this host. I admit that's not ideal but is much more palatable that 10 primary sites (that makes me shiver).

Do they really have ten different IT groups creating their own OSD content?

May 18th, 2015 7:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics