The content is sent to the secondary site server and the DP that co-exists on that site server just shares the content already sent to that secondary site server (if you also assign he content to that DP). So, the DP has the content, it just never had to have it explicitly sent across the network to it.
(clarifications inline as well) J From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Wednesday, January 4, 2017 11:09 AM To: [email protected] Subject: [mssms] RE: Rate limits / throttling to DPs Ok, so my comment was based on this: "as no content is ever truly sent to them". So, if no content is sent to the DP, my thought was, where do clients get the content if it's not at the DP. That's the only reason I brought up clients. >From a DP with the content based on boundaries and boundary groups, no >different. The content not being sent [across the network] to the DP does not >imply that the DP doesn't have the content, just that it gets it from another >source. As noted, the secondary site server already has the content in the >content library and since they share the content library due to their >co-existence, no need to do anything really for the DP to get the content. Think about it the other way. Wouldn't it be stupid if the secondary site had to gather the files for a package and somehow send them to the DP if the DP was co-located and the files were already there accessible to that co-located DP? So, to go back to my original question: Since my DPs are installed on secondary sites, is the throttling/rate limit set by the file replication section that I have found, or is there no rate limits set between the primary and secondary? What you found is the rate limiting between the site servers and has nothing to do with DPs. And, since the DP is installed on the secondary site, was your comment of "as no content is ever truly sent to them", meaning that the content is on the secondary site, but not in a specific location for the DP role? They share the content library when they are co-located so all that has to happen is the DP made aware that it should be serving the content - it's already there where the DP can access and serve the files. The content has to be there somewhere, right? Yes, the shared content library - shared because they are co-located. Sorry if I'm being dense here, it's been a long couple of weeks, and I'm trying to increase my understanding. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, January 04, 2017 7:21 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Rate limits / throttling to DPs No, not at all. Everything that's been said in this thread has nothing to do with clients. Rate limiting is about how the content gets to the DP and where the content is stored once it gets to the DP. Clients will always use DPs based on boundaries and boundary groups which as noted has nothing to do with rate limiting or the content library. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, January 3, 2017 3:59 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Rate limits / throttling to DPs Hmm. So, from reading that, it makes no sense to have a DP on a secondary site server? If no content is actually sent to the DP, then all the clients are still getting the content from the Primary site? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, January 03, 2017 11:47 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Rate limits / throttling to DPs Actually, those are rate limits to your secondary site, not the DPs. DPs not on site servers do in fact have rate limits tabs. As Michael pointed out below though, DPs on site serves don't because they share the content library with the site server and so having rate limits on the DP makes no sense as no content is ever truly sent to them. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, January 3, 2017 12:05 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Rate limits / throttling to DPs I found where the setting for Rate Limits is located. It is no longer on the DP properties. It is located under Hierarchy Configuration - File Replication. Go to the properties for those connections, and there is the Rate Limits tab. To answer your question, though: My DPs are on Secondary site servers. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schultz, Michael A Sent: Friday, December 30, 2016 11:53 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Rate limits / throttling to DPs Is the DP role in the screenshot a standalone DP or installed on a site server? And did you verify it is missing from all DPs? Rate Limit tab will not show on a DP installed on a site server. Michael Schultz Client Systems Engineering Information Systems Providence Health & Services [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Friday, December 23, 2016 9:37 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [mssms] Rate limits / throttling to DPs SCCM 1606, including the 3 hotfixes I know this has been discussed, and I know that I've asked a couple of questions. But I'm still a bit lost on what we can, and cannot do, as far as bandwidth throttling to DPs. 1) I don't have a throttling tab in the properties of my DPs: 2) My DPs are NOT setup as Pull DPs 3) If I look at my Distribution Point section, and add the Rate Limits column, it says No for all my DPs. [cid:[email protected]] So, knowing these things, is there a way to set throttling like there was back in 2007/2012? I know about the BITS throttling in Client Settings, but is that really where we set it for data going from the Primary out to the DPs? Thanks, Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284 Every Californian should conserve water. Find out how at: [SaveOurWater_Logo]<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsaveourwater.com%2F&data=01%7C01%7Cmichael.schultz%40providence.org%7C1144dec03bbd481f11a708d42b70d207%7C2e3190869a2646a3865f615bed576786%7C1&sdata=Dx4rg%2Bg0jKuwf3Rqth2qY8LeiqR5BFzEgzMyMmRMWPo%3D&reserved=0> SaveOurWater.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsaveourwater.com%2F&data=01%7C01%7Cmichael.schultz%40providence.org%7C1144dec03bbd481f11a708d42b70d207%7C2e3190869a2646a3865f615bed576786%7C1&sdata=Dx4rg%2Bg0jKuwf3Rqth2qY8LeiqR5BFzEgzMyMmRMWPo%3D&reserved=0> * Drought.CA.gov<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdrought.ca.gov%2F&data=01%7C01%7Cmichael.schultz%40providence.org%7C1144dec03bbd481f11a708d42b70d207%7C2e3190869a2646a3865f615bed576786%7C1&sdata=6zNPYLdPnhI1KVH9UfIrbpBdbfeIFrcfqSNClY5JiAU%3D&reserved=0> ________________________________ This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
