locked
Recommendations for hot/hot datacenter scenarios RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    So I've read the recommendations that there is generally no need for a CAS if <100K clients and that reassigning clients from one primary site to another is a manual process.  My question then is what is the recommendation for clients that want to split all traffic between hot/hot datacenters?  If under a 100K just one Primary site at one datacenter and a remote DP with MP at the other.
    Tuesday, June 5, 2012 1:00 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I wouldn't say this is a recomended solution. Plus you are correct, you do not need a CAS for less than 100k clients but you must have a CAS in order to have multiple primary sites. I'd suggest you stear you clients clear of this scenario, frankly it makes no sense.

    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Wednesday, June 6, 2012 1:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    There is no load-balancing or failover solution in ConfigMgr. Clients can only be assigned to a single primary site and must be manually reassigned. The closest you can get to this is to use virtualization and the HA capabilities of whichever virtualization solution you choose (fail-over clustering in Hyper-V).

    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Thursday, June 7, 2012 2:31 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Not sure I understand your question. If you have two primary sites with no CAS then they are independant of one another. I don't think that's what you are looking for but I could be wrong. Can you please clairfy?

    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Tuesday, June 5, 2012 1:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you asking about a scenario with one standalone primary serving clients in two datacenters? That would defintiely work. You could place site roles (MP/DP) in the local datacenter to optimize traffic.
    Tuesday, June 5, 2012 5:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm seeing the trend where instead of using a DR site only in an emergency the clients want to use it all the time.  So you have datacenter A with active clients and datacenter B (aka DR site) with active clients.  So from an SC2012 perspective what is the recommended method to set this up?  2 primary sites, one at each datacenter.  Only 1 primary site at datacenter A and a remote DP at datacenter B.  My initial thoughts were you need a CAS and 2 primaries but then futher reading suggests dont bother with a CAS if under 100k and because there is no automated method to reassign a client from one primary to another just keep it simple and use 1 primary.

    Tuesday, June 5, 2012 8:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm asking if it is the best or recommended practice for this type of scenario.

    Tuesday, June 5, 2012 8:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I wouldn't say this is a recomended solution. Plus you are correct, you do not need a CAS for less than 100k clients but you must have a CAS in order to have multiple primary sites. I'd suggest you stear you clients clear of this scenario, frankly it makes no sense.

    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Wednesday, June 6, 2012 1:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    There is no load-balancing or failover solution in ConfigMgr. Clients can only be assigned to a single primary site and must be manually reassigned. The closest you can get to this is to use virtualization and the HA capabilities of whichever virtualization solution you choose (fail-over clustering in Hyper-V).

    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Thursday, June 7, 2012 2:31 PM