Running SP 2016 in Azure - The Do's and the Don'ts
•Download as PPTX, PDF•
0 likes•295 views
The document discusses running SharePoint Server 2016 in Azure, providing guidance on when it is appropriate and how to design and implement a SharePoint farm in Azure. It covers scenarios like development/testing, pilots, and production. Design considerations include using resource groups, ensuring proper connectivity, selecting appropriate virtual machines and storage, and implementing security correctly. The document also discusses supportability and provides deployment resources.
Recommended
More Related Content
Similar to Running SP 2016 in Azure - The Do's and the Don'ts
Similar to Running SP 2016 in Azure - The Do's and the Don'ts (20)
More from Jasjit Chopra
More from Jasjit Chopra (15)
Recently uploaded
Recently uploaded (20)
Running SP 2016 in Azure - The Do's and the Don'ts
- 1. @spsahmedabad #SPSAhmedabad Brought to you by: SPSAhmedabad 2018 A Community Event to Learn About Azure, Office 365 & SharePoint
- 2. @spsahmedabad #SPSAhmedabad Jasjit Chopra PENTHARA TECHNOLOGIES MS Cloud Solution Architect and Azure MVP with strong background in Azure, SharePoint and Office 365. As a SharePoint expert he has worked with many multinational clients including HP, Avanade, Accenture, Unistar Nuclear Energy, Warner Music Group, Syneos Health and iHeartMedia. Jasjit holds a Masters of Business Administration in Technology and Management from CERAM, Sophia Antipolis, France. Having worked for different clients across the United States Jasjit has gained insight knowledge on Business Processes for the State Government and Manufacturing, Nuclear, Pharmaceutical and Music industries. Email : Jasjit@penthara.com Twitter : @jasjitchopra Facebook : jasjitchopra LinkedIn : jasjitchopra Running SP 2016 in Azure – The Do’s and the Don’ts
- 3. @spsahmedabad #SPSAhmedabad WHY? Don’t Do It If you can do it in Office 365 do it there first
- 4. @spsahmedabad #SPSAhmedabad Why do it ? • Retire existing datacenter / hardware • Fresh start • Evaluation • Elasticity *
- 5. @spsahmedabad #SPSAhmedabad Scenarios • Dev/test • Pilot / Proof of Concept • Production • Disaster Recovery • Hybrid
- 6. @spsahmedabad #SPSAhmedabad Design Process • Identity • Resource groups • Connectivity • Virtual Machines • Storage • Security
- 7. @spsahmedabad #SPSAhmedabad Resource Groups • By Function / Role • Life Cycle • Project Based • Department Based
- 8. @spsahmedabad #SPSAhmedabad Connectivity • Express Route recommended • Be vary of Data costs • Latency based on location • IP address spacing • Static IPs • Azure Load Balancer • Not at par with F5 • Third party appliances for load balancing
- 9. @spsahmedabad #SPSAhmedabad Virtual Machines • Design limited by VM sizes in Azure • Use large memory sizes for un-precited usage patterns • Undersize issue • Disk Size limitation • Disk count limitation • IOPS limitations • Availability Sets • Sys prep supported • Pre-loaded Azure VM images – minimum supported version There is no PERFECT size for SharePoint
- 10. @spsahmedabad #SPSAhmedabad VM Costs Number of Server Cores Server SKU RAM in GB Approx Cost Per Month 4 Cores D12 Standard 28 $ 485 D3 v2 Standard 14 $ 417 D12 v2 Standard 28 $ 485 D3 v2 Promo 14 $ 286 D12 v2 Promo 28 $ 335 8 Cores D13 Standard 56 $ 870 D4 v2 Standard 28 $ 830 D13 v2 Standard 56 $ 870 D4 v2 Promo 28 $ 570 D13 v2 Promo 56 $ 670
- 11. @spsahmedabad #SPSAhmedabad Storage • Premium Storage (SQL and SP running Search Role) • 200 MBPS min IOPS requirement for Index • Not just IOPS but bandwidth limitations as well play a role • Separate storage accounts per VM recommended (2 VMs OK) • Diagnostics • Use the same RG as VM • Managed Disks • Disk as an ARM resource
- 12. @spsahmedabad #SPSAhmedabad Storage (Continued…) •Run SQL TempDB on Non-Persistent SSD drive •Extend Content DBs directly to blob storage (SQL 2014 onwards) • VM NICs have direct access – better performance • Easy disk management (less drive letters) •LRS Only supported
- 13. @spsahmedabad #SPSAhmedabad How? • PowerShell • ARM (ASM – No No) • DSC • Other Third Party Orchestration systems To get Started: SharePoint Server 2016 High Availability Farm in Azure Deployment Kit https://gallery.technet.microsoft.com/sharepoint-server-2016-3d3d9071 https://technet.microsoft.com/library/mt793552(v=office.16).aspx https://github.com/Azure/azure-quickstart-templates
- 14. @spsahmedabad #SPSAhmedabad Supportability • Non-production farms, such as those used for dev/test environments or for proof-of-concept • As a disaster recovery target using log shipping, SQL Server AlwaysOn Availability Groups, or Azure Site Recovery • Production farms, using Azure premium storage for servers running the search role Production farms running SharePoint 2013 are also supported. SharePoint 2010 is no longer in mainstream support, however it can be installed on Azure VMs for testing and validation of migration scenarios.
- 15. @spsahmedabad #SPSAhmedabad Supportability • Office Web Apps !!
- 16. @spsahmedabad #SPSAhmedabad SP 2016 with SQL Always On
- 17. @spsahmedabad #SPSAhmedabad THANK YOU ! Please give us your feedback Rate each session with SPS Events Portal from https://bit.ly/2DvoGMS
Editor's Notes
- Dev/Test – Automate scheduling of VM Shutdowns Production – Storage Type, operation workloads like backup, patching OS, AD SQL SP does not go away – power yes, hardware issues DR – RPO RTO, Passive Infra, Cold, Warm or Hot, Log Shipping Hybrid – Same MS Network - things work faster
- The Azure infrastructure services environment is different than on-premises data centers and requires additional planning. The following design process steps you through determining the following elements of Azure infrastructure: Mapping on premises SP infra to Azure will always be complex specially for HA production farms. Like on premises have 2 of everything in Azure as well. ID – bring your on premises AD. AD DS not supported (working on it in test right now) – people picker and AD import (Global Catalog lookup limitations) Follow best practices for AD in Azure – static IPs etc
- Apart from these – use same guidance as you would for on premises. Load test Availability sets – timer job config cache – SLA https://blogs.technet.microsoft.com/uspartner_ts2team/2016/11/22/azure-single-instance-virtual-machine-sla/ https://azure.microsoft.com/en-in/support/legal/sla/virtual-machines/v1_0/
- https://docs.microsoft.com/en-us/azure/storage/storage-faq-for-disks https://docs.microsoft.com/en-us/azure/storage/storage-managed-disks-overview Managed Disks – Only LRS, No Shrinking or downsizing option available yet