Yeah, this seems weird to me. Full disclosure I haven’t done much with SQL clusters and SCCM so maybe there is something I’m missing.
I know if you want to use another SQL server for SCCM you can perform a site reset and use the option to point to a new SQL server (I’ve done this in the past no issue). · https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/ Maybe others on the email list can chime in and maybe they know if there is some gotcha with a SQL cluster that I’m unaware of. Rob From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Monday, December 18, 2017 11:32 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] Upgrading Config Mgr The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a side-by-side migration as opposed to doing something like a backup and restore of the SQL database to a new cluster. Our SQL team wanted to do a simple backup and restore to the new cluster, but we burned some Premier hours and the PFE advised us that doing that risked corrupting the entire database and forcing us into a site recovery. He said the only way to properly do it was the migration. He said we could try the backup/restore but that the success rate for that was not good. So we’re spending months doing a side-by-side migration. Mike From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli Sent: Monday, December 18, 2017 2:11 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr You must have something else going on with your site. It doesn’t make sense you would need to do site by site over just moving to new SQL cluster. If your saying you’re doing it up to clean old crap that’s different. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Friday, December 15, 2017 7:12 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr Same here. We would never be able to just click “go” without a vetted plan in place and change management involved. With 35K clients we are by no means a large organization, but if something were to go sideways in the upgrade and we skipped the planning and control, there wouldn’t be enough time to update resumes once they came for us. On top of that there are other factors to figure in before you click “go”. For example, in our case we are going to have to do a side-by-side site migration because our SQL cluster is no longer supported (hardware is out of warranty). Best practices from the Microsoft PFE was to do a site migration as opposed to attempting to just moving the database to a new cluster. So we’re going to spend a great deal of time migrating content, collections, sequences, etc. to the new site servers, test and validate it all, then start migrating clients. Then we can click “go” and upgrade the new site to 18xx. Mike From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R. Sent: Friday, December 15, 2017 3:55 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr It’s the same here.. and, I’d hope everywhere have some form of change control. Although it obviously depends on how big the shop is. I think everyone who has been through a failed upgrade at some point in time, is always slightly more weary of the potential for downtime. Personally, I’ll upgrade my Dev environment a week or so after its out in Fast Ring.. then Prod a few weeks after its general release. But I’ll submit a change, and communicate its upcoming upgrade to all relevant teams long before and in the build up to it being done. Rich Mawdsley From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Heaton, Joseph@Wildlife Sent: 14 December 2017 16:35 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr My organization requires a more formal plan for any updates. And it goes through a weekly approval board, so I still have to line everything up nicely. I got the go-ahead to upgrade ADK today, but the server updates haven’t gone to the approval board yet. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Wednesday, December 13, 2017 12:19 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] Upgrading Config Mgr You must be using lots of new features if you need a plan :) :) Run the pre-requ check that would tell you if 1702 to 1706 will work (it will) With quarterly updates I wouldn’t spend to long planning ! Backup and press go……. Stuart On 12 Dec 2017, at 18:07, Heaton, Joseph@Wildlife <joseph.hea...@wildlife.ca.gov<mailto:joseph.hea...@wildlife.ca.gov>> wrote: I am currently running 1702. I’ve written up my plans and method for upgrading to 1706, but over the weekend 1710 showed up in my availables. I have seen some really cool stuff coming with 1710, but is it still too soon for production? Can I upgrade from 1702 directly to 1710? 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 ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
