Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Cargando en…3
×

Eche un vistazo a continuación

1 de 61 Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

A los espectadores también les gustó (20)

Anuncio

Similares a SharePoint on Azure (20)

Más de Usama Wahab Khan SharePoint/office365/azure Architect (13)

Anuncio

Más reciente (20)

SharePoint on Azure

  1. 1. SharePoint on Azure Usama Wahab Khan Sr. Solution Architect , Microsoft Most Valuable Professional, Microsoft Technical Community Leader, Microsoft Certified Trained Vice -President, Technology Middle east and Europe (DAVIGOLD LLC)
  2. 2. Cloud Models Applications
  3. 3. Windows Azure $
  4. 4. pay only for what you use 
  5. 5. no upfront costs
  6. 6. per minute billing
  7. 7. no charge for stopped VMs $
  8. 8. Global Footprint
  9. 9. Pay for what you use
  10. 10. Cloud Computing
  11. 11. SharePoint Cloud Continuum CONTROL COST-EFFICIENCY Value Prop Full h/w control – size/scale Roll-your-own HA/DR/scale SharePoint (On-premises) • SharePoint Value Prop 100% of API surface area Easy migration of existing apps Roll-your-own HA/DR/scale SharePoint (IaaS) • Hosted SharePoint Value Prop Auto HA, Fault-Tolerance Friction-free scale Self-provisioning, mgmt. @ scale Office 365 (SaaS)
  12. 12. What are Infrastructure Services? Cloud Based Virtual Machines Hyper-V Based Hosting Technology Run workloads in Azure that were traditionally run on-premises Networking Virtual Networks: Private IPV4 Network support, and hybrid connectivity to on-premises Access Control Lists, External and Internal Load Balancing, Reserved IPs • Run Traditional workloads in the cloud with little to no changes
  13. 13. SharePoint on Azure IaaS • Mario Brandan • Regional Architect • Microsoft
  14. 14. SharePoint farms in Microsoft Azure Scenarios Production Internet Development or Test Demo Environment Concepts Virtual Network Availability Sets Load Balancer Access Control Lists
  15. 15. Virtual Machines
  16. 16. Virtual Machines on Azure
  17. 17. SharePoint in a Microsoft Azure VM? Why Host in Microsoft Azure Virtual Machines? Control - hosting in Microsoft Azure gives you a similar level of control to hosting on premises minus managing the hardware. Agility – quickly spin up or copy development and test environments. Smaller Laptops – Consultants, you should appreciate this! SharePoint Server 2010 and 2013 supported Platform base image available for 2013 License Mobility through Software Assurance SharePoint 2010 create custom image: KB2728976 Fast Search Server 2010 is NOT supported in Microsoft Azure
  18. 18. VM with persistent drive
  19. 19. Microsoft Azure Storage SharePoint Virtual Machine Disk Storage Storage Accounts are Created per Region Upload Existing SharePoint VHDs to Storage with PowerShell C: OS Disk (127 GB) D: Local Temporary Storage F: Data Disk (500 GB) G: Data Disk (1 TB) spstorage - West US
  20. 20. Windows Azure Virtual Networks • Build virtual networks that scale • Traditional, familiar approach to build extension to datacenter • Scalable approach to building virtual networks • Control over network configuration • Define your own IP address ranges • Be compliant with corporate IT security policy • Enables rich hybrid scenarios • Hybrid apps can reach all or portion of the on-premise network • Works with both Windows and non-Windows systems
  21. 21. Microsoft Azure Virtual Networks Declare your own address space in the cloud Private and Persistent IP Addresses (unless you de-allocate the VM) Support for Static Internal IP addresses (even if you de-allocate a VM) Advanced Connectivity Support for Hosting Active Directory in Azure Virtual Machines Connect multiple cloud services privately on the same virtual network Connect Virtual Networks in the same or separate regions Support for Internal Load Balancing Optional - Hybrid Connectivity – Site to Site, Point to Site and ExpressRoute Virtual Networks are Required for a SharePoint Farm
  22. 22. Virtual Gateways 10.1.2.0/24 10.1.3.0/24 10.2.2.0/24 10.2.3.0/24
  23. 23. IP Allocation with Virtual Networks IPs are allocated based on order of provisioning. (1st 4 IPs are reserved) Subnet: 10.0.0.0/24 1. VM1 = 10.0.0.4 2. VM2 = 10.0.0.5 If VMs are re-allocated in a different order they get different IP addresses 1. VM2 = 10.0.0.4 2. VM1 = 10.0.0.5 Use Static IP addresses to retain IP regardless of order Set-AzureStaticVNetIP
  24. 24. Reserved IP Addresses New Feature for Virtual Machines
  25. 25. Load Balancing and High Availability
  26. 26. Availability Sets A label that tells Microsoft Azure your virtual machines perform the same workload router/switch power supply network cables physical machine
  27. 27. SharePoint Farms and Availability Sets For each tier create an Availability Set Availability Sets do not span cloud services
  28. 28. External Load Balancing Load Balancer External – public sites Uses health probes for additional availability Use Reserved IP for Public IP addresses or map external domains using a CNAME
  29. 29. Load Balancing with Always On Listener Load Balancer SQL Always On uses external load balancer for listener virtual name. Use Reserved IP for Public IP. SQL AO will stop working if external IP changes.
  30. 30. Access Control Lists Used to restrict access to endpoints Protect SQL Listener Load Balanced Endpoint Add Permit rule for SharePoint Cloud Service IP (Denies everyone else)
  31. 31. Internal Load Balancing (NEW) Virtual Network Address Space: 10.0.0.0/16 On Premises 192.168.0.0/16 Active Directory Replication Access on-premises resources Access intranet over hybrid connection https://spintranet Map to: 10.0.0.100 Set Internal Load Balancer IP New-AzureInternalLoadBalancerConfig http://spintranet Hybrid Connection
  32. 32. Setting the Internal Load Balancer http://spintranet
  33. 33. Virtual Machine Instance Sizes Size Name CPU Cores Memory Max. data disks Max. IOPS ExtraSmall Shared 768 MB 1 1x500 Small 1 1.75 GB 2 2x500 Medium 2 3.5 GB 4 4x500 Large 4 7 GB 8 8x500 ExtraLarge 8 14 GB 16 16x500 A5 2 SharePoint Virtual 14 GB Machines 4 4X500 A6 4 28 GB 8 8x500 A7 8 56 GB 16 16x500 A8 8 56 GB 16 16x500 A9 16 112 GB 16 16x500 Each data disk can hold up to 1 TB of storage.
  34. 34. Extranet and Public-Facing Internet Windows Azure On Premises Cloud Service Virtual Network Active Directory Site developers and authors VPN Tunnel Internet Zone Anonymous Extranet Zone Default Zone Windows Windows SAML FBA Visitors Partners and Customers
  35. 35. Dev / Test SP DR3 (Large) Cloud Service Virtual Network Windows Azure SQL DR1 (A6) SP DR1 (Large) AD1 (X-Small) SQL DR2 (A6) SP DR2 (Large) SP DR4 (Large) SP DR5 (Large) Visual Studio Online Test Agents
  36. 36. Azure Account 80
  37. 37. Single Virtual Machines Template LB WEB/APP SQL AD/DC/DNS 80 20000 Cloud Service Virtual Network Windows Azure Web/App Tier 1 x Large (4 Cores & 7 GB) Data Tier 1 x A6 (4 Cores & 28 GB) Identity Tier 1 Small (1 Core & 1.75 GB) K
  38. 38. Hybrid SharePoint Farm – Site to Site Scenarios Production SharePoint Farm (Intranet or Extranet) Extend Access to or from On-Premises • Active Directory • BCS Data Sources Concepts Site to Site Public Internet IP/SEC
  39. 39. Site to Site Devices Supported Cisco, Juniper, F5, Brocade, CheckPoint, Fortinet Individual Devices: http://msdn.microsoft.com/en-us/library/azure/jj156075.aspx Software VPN Support Microsoft Routing and Remote Access, OpenSwan
  40. 40. Hybrid SharePoint Deployment – Site to Site Virtual Network Address Space: 10.0.0.0/16 On Premises 192.168.0.0/16 Active Directory Replication Access on-premises resources Management Traffic Public Internet IP/SEC http://contoso.com
  41. 41. Microsoft Azure ExpressRoute Azure Edge Scenarios Private, Low Latency Connectivity to Cloud Production SharePoint Farm (Extranet or Intranet) Extend Enterprise Identity Access On-Premises or Co-Located Resources Disaster Recovery Concepts ExpressRoute Connectivity Provider Customer’s Infrastructure network Customer’s dedicated connection Traffic to public IP addresses in Microsoft Azure Traffic to Virtual Networks in Microsoft Azure 10 Mbps to 10 Gbps
  42. 42. Express Route (Internet Exchange Provider) High speed (up to 10 Gbps) and Low Latency Private (direct connect from data center to Azure) INTERNET Exchange Provider Equinix Level3 Supported Bandwidth 200,500 Mbps 1 Gpbs 10 Gpbs Microsoft Azure Virtual Network On Premises 192.168.0.0/16
  43. 43. Express Route (Network Service Provider) High speed (up to 1 Gbps) and Low Latency Private (direct connect one or more data centers to Azure via MPLS VPN) INTERNET MPLS VPN AT&T Level3 Bandwidth 10,50,100,500 Mbps 1 Gbps Microsoft Azure Virtual Network
  44. 44. ExpressRoute and SharePoint DR Active SharePoint Directory WEB Equinix – Silicon Valley Active Directory SharePoint App F5 BIG IP Load Balancer SharePoint App SQL Witness SQL Primary SharePoint WEB ExpressRoute Circuit (1Gps) Microsoft Azure - West US
  45. 45. SharePoint Deployment Tips Only SharePoint is on the C: drive Put each SharePoint logical tier into its own availability set (WFE, APP etc…) Put blob cache on a data disk to increase available IOPS. D: may be considered just remember that it may be deleted and refreshing blob cache can be painful. Use Static IP addresses to avoid issues if virtual machines started out of order.
  46. 46. SQL Server Best Practices Storage Recommendations Split content databases across multiple disks for increased IOPS Verify Disk Cache Settings on Data Disks (See whitepaper link below) Avoid using OS drive for databases Put database and transaction log files on separate drives Use SQL Server File Groups instead of Disk Striping SharePoint relies heavily on TempDB – Split and move TempDB to data disks Database Recommendations Consider using database page compression to reduce I/O High Availability Recommendations Consider latency between primary and replica when choosing sync mode Use Availability Sets SQL Server Performance Whitepaper: http://go.microsoft.com/fwlink/?LinkId=306266
  47. 47. More on Storage for SQL Server Performance Considerations Do not use the temporary disk (D:) (including for TempDB) Use SQL file groups across multiple disks instead of disk striping Put logs, data and backup on separate disks Disable geo-replication on storage account for consistency Remember storage account capacity planning. 20,000 IOPS per Storage Account – 500 IOPS per disk Consider compressing any data files when transferring in/out of Windows Azure. Scale Out Not Up Move content databases to separate SQL Servers Move search databases to separate SQL Servers Add more WFE for scaling SharePoint services Add dedicated Search Servers and SQL Server SQL Server Performance Whitepaper: http://go.microsoft.com/fwlink/?LinkId=306266
  48. 48. Storage Capacity and Planning Random I/O (8 KB Pages) Sequential I/O (64 KB Extents) Supports up to 40 data disks using maximum IOPS per disk Sequential I/O (256 KB Blocks) Reads Writes Reads Writes Reads Writes IOPS 500 500 500 300 300 300 Bandwidth 4 MB/s 4 MB/s 30 MB/s 20 MB/s 70 MB/s 70 MB/s
  49. 49. How to get Azure
  50. 50. MSDN Azure Benefits • Subscription Levels Subscription Level Visual Studio Professional with MSDN Visual Studio Test Professional with MSDN MSDN Platforms Visual Studio Premium with MSDN Visual Studio Ultimate with MSDN Azure Credits included per month $50 $50 $100 $100 $150 Spending Limit Requires a credit card on file Doesn’t let you exceed your monthly Azure Credits Can be turned on and off No Production Work
  51. 51. Other ways • Pay as you go – Pricing Calculator: – http://azure.microsoft.com/en-us/pricing/calculator/ • Free Trial – http://azure.microsoft.com/en-us/pricing/free-trial/
  52. 52. start now. http://WindowsAzure.com
  53. 53. Deep technical content and free product evaluations TechNet Virtual Labs Hands-on deep technical labs Free, online, technical courses Download Microsoft software trials today. Find Hand On Labs. Take a free online course. Technet.microsoft.com/evalcenter Technet.microsoft.com/virtuallabs microsoftvirtualacademy.com
  54. 54. MSDN Member Benefits
  55. 55. MSDN Credits with Windows Azure
  56. 56. Web + Mobile experiences Big data, machine learning, IoT Hybrid on-premises integration Flexible cloud development
  57. 57. Questions?
  58. 58. Resources • Windows Azure Training Kit • Kirk Evans Presentation from SPC14

Notas del editor

  • Speaking Points:
    Microsoft Azure itself is deployed around the world
    With Microsoft Azure, we have a concept of regions, which is where you choose to place your code and run.
    In each of the regions, we have a Microsoft datacenter.
    These datacenters are massive facilities that host 10s or in some cases hundreds of thousands of servers
    We have currently four regions in North America, two regions in Europe, and two in Aisa
    As you can see on this slide we also have a number of CDN edge points, which we can use to cache your content and deliver it even faster for customers. %
    What you’re going to see in the next couple months and years is that we will rapidly expand our datacenter footprint around the world, so you will have more options for running your applications.
    Once you build an application, you can choose where you want to run in the world and you can move your workloads from region to region.
    You can also run your application in multiple regions simultaneously and just direct traffic and customers to whichever version of the app is closest to them.
    That gives you a global footprint and a chance to reach a bigger customer base or audience in new markets

    Notes:
    Microsoft Azure services such as compute and storage are now available in 8 worldwide datacenters with an additional 24 Content Delivery Network endpoints.
    You can’t have a real cloud without a data center.
  • Speaking Points:
    The final thing I’ll mention about Microsoft Azure, before we dive into the tour of services is the approach we’re taking with paying for services.
    This maybe different for many of you who are familiar with hosting providers and on-premises systems.
    With Microsoft Azure you pay only for what you use.
    There are no upfront cost
    There is no need to buy any up front server licenses, that’s just included in the price
    Likewise if you use a SQL database, through our SQL Database feature in Microsoft Azure, you don’t have to buy a SQL Server license, that’s also included in the price.
    For compute services such as Virtual Machines and Web Sites you only pay by the hour.
    This gives you the flexibility to run your applications very cost effectively.
    You can scale up and scale down your solutions or even turn them on and off as necessary.
    This also opens up a ton of possibilities in terms of the new types of apps you can build
  • Slide Objectives:
    Explain the three established industry terms for cloud services

    Speaker Notes:
    There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service.
    Since PDC08 when we first announced the Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications.
    We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform.

    Notes:
    There is a lot of confusion in the industry when it comes to the cloud.
    It’s important that you understand both what is happening in the industry and how we think about the cloud.
    This is the most commonly used taxonomy for differentiating between types of cloud services.
    The industry has defined three categories of services:
    IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications.
    PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed.
    SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue.
    It is important to note that these 3 types of services may exist independently of one another or combined with one another.
  • Speaking Points:
    This is designed to give you very reliable performance and hopefully it ensures that it is always on


×