SCCM central site High Availability

Hi All,

In our SCCM infrastructure we have one central site server and five primary site servers. All the five primary site servers are connecting to one central site server. I have to plan high availability for my central site server, it means that central site server should always be online , may be by clustering if possible or may be by any other method.

Please suggest what could be the best plan?

Rgs,

June 19th, 2013 5:49am

Why? What does having the central site always on give you? High Availability is about functionality, not a whole server.
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2013 7:04am

Hi,

I suggest you read the following document first.

http://technet.microsoft.com/en-us/library/hh846246.aspx#BKMK_HASiteRole 
June 19th, 2013 12:21pm

Hi All,

Thank you for the comments , but i want to know what happens when the central site server goes down.

I know all the above links and other details that are mentioned above, but my question is" if central site server goes down can i have redundancy or high availability of the central site server"?

Rgs,

Free Windows Admin Tool Kit Click here and download it now
June 20th, 2013 10:46am

Nothing really. That's the point though. *You* need to define what functionality you need highly available and then from there design your sites, hierarchy, and roles based upon these requirements. Simply saying I want the server highly available is not really valid and not technically achievable anyway.
June 21st, 2013 12:48am

hi all,

Can any one elaborate on the changes that will happen to Clients lets say we have two environment A and B both having SCCM servers installed and something goes wrong to A environemnt , than how the clients of A are goin to fail-over or go to SCCM site code of B. Is it even possible or not? Please let me know if my view is wrong and we have any other alternative at all?

Rgs

Free Windows Admin Tool Kit Click here and download it now
July 1st, 2013 5:58pm

They won't.

Why do you need them to? Are you expecting Site A to be hit by a meteor and never available again?

July 1st, 2013 6:13pm

Than how are you going to achieve diaster recovery plan , also lets try to keep the conversation to the subject , if solution not possible to this situation, now, than  may be this could be an idea for MS to include it in its forth coming version of SCCM

Rgs,

Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2013 9:20am

I'm with Jason on this one. It doesn't make sense to have clients from site A automatically migrate over to B. Why would you want them to? Wouldn't it be faster to rebuilt site A?
July 2nd, 2013 1:10pm

While walking our dog this morning, I thought of a great example as to why this is a BAD idea.

  • Let assume that you DNS team make a change and goes for lunch.
  • You have 15000 PCs at Site A
  • You have both HW and SW inventory enable, each will send a minimum of 5 MB each to the site server
  • Assume that SW inventory take the full 4 hours to run
  • 68 minutes for the DNS team to fix the problem
  • CM07/CM12 client will automatically fail over to Site B after missing 1 attempt at contacting the CM site server.
  • CM07 PC can resolve the Site B CM07 site server.

Based on the above, this will mean ALL clients from Site A will fail over to Site B, It will also mean that all client will be FORCE to generate a full inventory for everything (HW, SW, DCM. HB, SU, etc).

(15000 * 5 MB) for HW Inv + (15000 * 5 MB) for SW Inv + (15000 * ?? KB) for each DCM rule + (15000 * 1KB) for Heartbeat Inv  = minimum of 150015 MB or 150 GB if you fail it back to the old site once the DNS is fixed you will end up with yet another 150GB of bandwidth consumed and all of this because the DNS team make a mistake.

The question about HA is:

  • What feature of CM07/CM12 does you requite up and for why?
  • What does downtime really mean?
  • What is affected by the downtime?
  • How much down time can you afford? 1 hours hour, 1 Day, 1 week???
  • Do you have other options to temporally solve you needed during a outage? (1 hours, 1 day, 1 week?)
  • Do you have a plan to migrate client in the event of a DR or Emergency?
  • Can you re-build the site in the allowable downtime?

Without answer these question, you cant design an HA / DR solution. I have yet to find a client where they cant live without CM07/CM!2 for at least 48 hours and most agree that 1 week is acceptable! As such they can easily rebuild CM07/CM!2 in that time frame and still meet all SLA.

Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2013 3:33pm

Thankyou Garth i really appreaciate your detailed explaination , as i got what exactly searching for....in couple of your sentences.

May be next time i need to do the trick of walkin the dog ealry morning....just on a good humor and with all the respect you answered my question in totality.

Thanks again...

Rgs,

July 3rd, 2013 2:20am

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

Other recent topics Other recent topics