How big are the sites you guys support?
I worked at a large financial that had over 300k clients. We couldn't get the performance we needed from the VM team, so we went physical for CAS/Primaries with directed attached storage and virtual for other roles. Doing restores were a nightmare. We had cold spares that we would do the backups/restores to which made it easier, but yeah it's not a pretty picture when you have no choice but to go physical. From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: Friday, May 29, 2015 10:37 AM To: [email protected] Subject: RE: [mssms] SCCM 2016 TP2 - Questions Agreed. How hard is it to have a server named the same? SCCM isn't something most people have running on a server dedicated to something else. With Hyper-V/VM it makes "moving" SCCM to another system very rare. Much easier to restore the backups right back into the cluster. I guess you could run into issues if it is a physical box and you name the servers after the asset tag. From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, May 29, 2015 10:26 AM To: [email protected] Subject: RE: [mssms] SCCM 2016 TP2 - Questions 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]] 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]] 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.
