SCCM 2012 SUP locations

Question

What is a best practice for SUP Installation.
I have read that if your SUP goes down , the clients will assign to another SUP and at that time re-scan for entire catalog (a lot of traffic)
So if we keep only one SUP in the primary location and it goes down , Clients will not fallback to other SUP as there in none in hierarchy , but rather fallback to Microsoft Updates.
Does anyone have suggestions for SUP placements in a environment of around 9K clients
PS1 - Clients 2500  (EMEA) --- 40 MB connection with HQ
PS2 - Clients 1800  (EMEA) --- 100 MB connection with HQ
PS3 - Clients 1700  (EMEA) --- HQ Primary location 
PS4 - Clients 1400  (EMEA) --- 100 MB connection with HQ
PS5 - Clients 800    (Americas) --- 100 MB connection with HQ
PS6 - Clients 425   (Asia)  --- 2 MB connection with HQ
PS7 - Clients 175   (EMEA) --- 100 MB connection with HQ
PS8 - Clients 170   (Africa) --- 4MB Connection with HQ

Answer 1

That's why you place two SUPs in the central location (avoid the use of the word "primary" unless you are actually talking about a primary site or primary site server other your meaning may be ambiguous) whose underlying WSUS instances use the same
DB. If one goes down, then the rescan penalty is almost nothing because they are using the same DB.
Note that the use of multiple SUPs within a single primary site is for availability only though. Also note that the SUP itself isn't anything the client's know about or use, they use the underlying WSUS instance. Thus, there are ways of controlling which
WSUS instance clients use via Group Policy Preferences but the less micro-management you do, the better things work.
Also, clients will *never* fallback to Microsoft Updates for scanning. That would make no sense because only your WSUS instances have your update catalog to scan against.
And finally, is high availability of update scanning truly something you need to worry about? What's exactly is your SLA for update scanning and isn't simply building a new SUP sufficient?
(Not trying to say it's not valid or that you shouldn't have multiple SUPs, just trying to make you think about what you're doing. Also, "best practice" implies there's only one good way to do something and that everyone should do it that way which means
everyone is the same which is not true. Thus you need to design things specific to your environment based on the knowledge of how the components work. Relying on so-called "best practices" effectively means you're just guessing.)
Jason | http://blog.configmgrftw.com