locked
ConfigMgr 2012 Service Pack rollback plan in a CAS hierarchy RRS feed

  • Question

  • I'm looking for some general guidance on rolling back a service pack upgrade gone wrong (nothing has gone wrong yet, just asking).

    I'm looking to upgrade a hierarchy with a CAS and 6 child primary site servers. Assuming I roll out a service pack upgrade to the cas and one primary site server and realize something is horribly wrong I'd like to know what disaster recovery looks like ....

    I know you can't just uninstall the primary site server and cas bits to roll back (it'll complain you have to remove all child infrastructure first). I *think* dropping the database will allow you to work around the "can't uninstall site" issue, but is that what I should do? Should I drop the site database, uninstall the new ConfigMgr bits, reinstall the old bits with the site recovery options?

    Should I recover the child primary or cas first? Or does it even matter?

    Thanks!

    Wednesday, November 11, 2015 6:03 PM

Answers

  • I think I found what I was looking for:

    https://www.microsoft.com/en-us/download/confirmation.aspx?id=44295

    This document covers things like how to conduct a hierarchy recovery and how to avoid deadlock issues where the freshly restored cas is waiting on the primaries and is in read only mode, but you can't restore the primaries without the cas (I ran into this in DR testing and it wasn't clear how to get around it).

    Friday, November 13, 2015 1:32 PM

All replies

  • There is no one-fits-all reply here, but I think that you cannot rollback after the CAS was upgraded at all (without major efforts though). You would have to fix the issue. I had to restore a child primary and were able to upgrade it afterwards.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 11, 2015 6:43 PM
  • Using the recovery options here https://technet.microsoft.com/en-us/library/gg712697.aspx?f=255&MSPPError=-2147217396#BKMK_RecoverSite would fall into the "major efforts" category that Torsten pointed out, but they are legitimate options for recovering from a failed upgrade.

    Ultimately, though, fixing the issue (involving CSS as needed) is the best option.

    Jeff

    Wednesday, November 11, 2015 6:48 PM
  • Torsten, 

    Thanks for the quick reply ... I noticed that rolling back a child primary via the ConfigMgr installer will not let you advance forward with the install process while the CAS is at a higher version rev. Is it recommended to upgrade child primaries before or after upgrading the CAS?

    Wednesday, November 11, 2015 6:50 PM
  • Jeff,

    I appreciate the link and reply, but this is for drafting a disaster recovery plan. Fixing the issues and opening a CSS case are certainly a priority, but I'm looking to draft a disaster recovery plan.

    I breezed through the link you provided (it's a lot more than I could originally find), but I don't see any complex scenarios included in the site recovery options (such as cas/multiple primary, etc?) ... or maybe I'm being dense and missing the point ...


    Wednesday, November 11, 2015 7:00 PM
  • I think I found what I was looking for:

    https://www.microsoft.com/en-us/download/confirmation.aspx?id=44295

    This document covers things like how to conduct a hierarchy recovery and how to avoid deadlock issues where the freshly restored cas is waiting on the primaries and is in read only mode, but you can't restore the primaries without the cas (I ran into this in DR testing and it wasn't clear how to get around it).

    Friday, November 13, 2015 1:32 PM