SPSAhmedabad #SPSAhmedabad. Brought to you by: A Community Event to Learn About Azure, Office 365 & SharePoint

Size: px
Start display at page:

Download "SPSAhmedabad #SPSAhmedabad. Brought to you by: A Community Event to Learn About Azure, Office 365 & SharePoint"

Transcription

1 SPSAhmedabad 2018 A Community Event to Learn About Azure, Office 365 & SharePoint Brought to you by:

2 Running SP 2016 in Azure The Do s and the Don ts 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. Jasjit@penthara.com Twitter Facebook : jasjitchopra LinkedIn : jasjitchopra

3 WHY? Don t Do It If you can do it in Office 365 do it there first

4 Why do it? Retire existing datacenter / hardware Fresh start Evaluation Elasticity *

5 Scenarios Dev/test Pilot / Proof of Concept Production Disaster Recovery Hybrid

6 Design Process Identity Resource groups Connectivity Virtual Machines Storage Security

7 Resource Groups By Function / Role Life Cycle Project Based Department Based

8 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 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 VM Costs Number of Server Cores 4 Cores 8 Cores Server SKU RAM in GB Approx Cost Per Month D12 Standard 28 $ 485 D3 v2 Standard 14 $ 417 D12 v2 Standard 28 $ 485 D3 v2 Promo 14 $ 286 D12 v2 Promo 28 $ 335 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 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 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 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

14 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 Supportability Office Web Apps!!

16 SP 2016 with SQL Always On

17 THANK YOU! Please give us your feedback Rate each session with SPS Events Portal from