Running SharePoint 2016 in azure
•Download as PPTX, PDF•
1 like•169 views
This deck was a part of session delivered at the SharePoint Saturday Dubai event #spsdxb. In this session we covered the entire process of planning and successfully running SharePoint 2016 in the cloud. We covered topics related to Security, Performance, Scalability, High Availability, Backup & Restore and Disaster Recovery.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Running SharePoint 2016 in azure
Similar to Running SharePoint 2016 in azure (20)
More from Jasjit Chopra
More from Jasjit Chopra (16)
Recently uploaded
Recently uploaded (20)
Running SharePoint 2016 in azure
- 1. SharePoint 2016 on Azure JASJIT CHOPRA SHAREPOINT / OFFICE 365 / AZURE CONSULTANT PENTHARA TECHNOLOGIES
- 2. Don’t Do It If you can do it in Office 365 do it there WHY
- 3. Why do it? Retire existing datacenter / hardware Fresh start Evaluation Elasticity *
- 4. Scenarios Dev/test Pilot / Proof of Concept Production Disaster Recovery Hybrid
- 5. Design Process Identity Resource groups Connectivity Virtual Machines Storage Security
- 6. Resource Groups By Function / Role Life Cycle Project Based Department Based
- 7. 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
- 8. 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
- 9. 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
- 10. 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
- 11. 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
- 12. 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
- 13. 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.
- 14. Supportability Office Web Apps !!
- 15. Virtual network On-premises network Site-to-site VPN or ExpressRoute Gateway AD TCP 443 WEB1 WEB2 Subnet APP1 APP2 Subnet SQL1 SQL2 Subnet DC1 DC2 Subnet MN1 Internet pipe SP 2016 with SQL Always On
- 16. Thank You ! Twitter: @jasjitchopra LinkedIn: https://www.linkedin.com/in/jasjitchopra/ Email: jasjit@penthara.com
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