Our virtual infrastructure wasn't there when we migrated to 2012. We've actually had to do 2 restores due to hardware failures - once on the CAS, and once on a primary. (I started 2 weeks before the migration and didn't have a say in the design. So please don't yell at me about the CAS.) I may be scarred for life.
We are in the middle of re-architecting to eliminate the CAS and all but 3 secondaries and will have everything but some of the remote DPs on virtual servers. I would recommend everyone take another look at your architecture. Especially with the new supported client counts there is generally no need for multitudes of site servers. ----- Dwayne Allen [email protected] (479) 310-0027 On Fri, May 29, 2015 at 9:25 AM, Marcum, John <[email protected]> wrote: > How many times have you, or anyone else for that matter, needed to > restore ConfigMgr? I use replicated VM’s and I don’t worry about restoring > ever. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Robert Spinelli > *Sent:* Friday, May 29, 2015 8:57 AM > *To:* [email protected] > *Subject:* RE: [mssms] SCCM 2016 TP2 - Questions > > > > I’ve worked for lots of big companies, made my voice heard for years on > how bad the restore process and HA is in the product. They did throw us a > bone and allowed you to restore the database to a server with a different > name, but the hard coding of servers names still being in the product after > all these years is a joke. > > > > SQL AlwaysOn still not being supported is insane. > > > > Whenever I go to a company and tell them here is the restore process, they > look at me like I’m insane. They all say this can’t be correct. Gives > SCCM a really big black eye for any new company looking to adopt it. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Friday, May 29, 2015 9:47 AM > *To:* [email protected] > *Subject:* RE: [mssms] SCCM 2016 TP2 - Questions > > > > Being an early beta, a lot of things just aren’t there yet, don’t work, > and/or simply haven’t been documented so there is no good answer to the > below. All of the below have been raised as “concerns” with various members > of the product group over the past few years but I have no idea if any of > the below are addresses in v.Next or not. Basically, if you want these, > file them on connect to make sure your voice gets heard. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Robert Spinelli > *Sent:* Friday, May 29, 2015 8:37 AM > *To:* mssms > *Subject:* [mssms] SCCM 2016 TP2 - Questions > > > > I haven’t played with SCCM 2016 TP2, was wondering if anyone knows is it > any better when it comes to disaster recovery / HA ? > > > > Please don’t tell me you still need to have the same server name for > CAS/Primary when doing a restore. > > > > Does it support SQL AlwaysOn? Any info is appreciated. > > > > Thanks > > > Rob > > > > > > > ------------------------------ > > > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you have > received this message in error, please notify the sender by replying to > this e-mail and then delete it from your computer. > >
