• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SharePoint 2010 Architecture - TechEd Brasil 2010
 

SharePoint 2010 Architecture - TechEd Brasil 2010

on

  • 2,887 views

 

Statistics

Views

Total Views
2,887
Views on SlideShare
2,887
Embed Views
0

Actions

Likes
0
Downloads
185
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Step 1: Model – Modelling is the process by which you decide the key solutions you want your environment to support, and establish all important metrics and parameters. Step 2: Design – Once you have gathered the data from Step 1, you can design your farm. Outputs are detailed data architecture and physical and logical topologies.Step 3: Pilot, Test and Optimize – If you have designed a new deployment, you need to deploy a pilot environment for testing against your workload and expected usage characteristicsStep 4: Deploy – This step describes implementing the farm, or deploying changes to an existing farm. Step 5: Monitor and maintain – This step describes how to set up monitoring, and how to predict and identify bottlenecks, as well as perform regular maintenance and bottleneck mitigation activities.
  • As an example using this rough guideline, SQL Server would be expected to devote 75 IOPS to a 100GB content database, or 375 IOPS for five content databases.  Analyzing one’s SQL Server, it may be necessary to split some content databases onto their own spindles in order to achieve this rate. 

SharePoint 2010 Architecture - TechEd Brasil 2010 SharePoint 2010 Architecture - TechEd Brasil 2010 Presentation Transcript

  • SETEMBRO, 2010 | SÃO PAULO
  • CÓDIGO DA SESSÃO:OSP301
    Arquitetura e topologias do SharePoint 2010
    Michael Noel
    Partner
    Convergent Computing
  • Michael Noel
    • Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles .
    • Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco, USA Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
  • AgendaWhat we will cover
    Physical SharePoint Server Architecture
    Architecture Planning Changes
    SharePoint Databases
    Service Applications
    Virtual SharePoint Server Architecture
    Virtual Host Guidelines
    Virtual Guest Guidelines
    Sample Virtual Environments for SharePoint 2010
  • SharePoint 2010 Architecture Planning Changes
  • SharePoint 2010 Architecture PlanningUser Workloads
    • Capacity planning is similar to MOSS2007
    • Usage now broken down by workload
    • A workload is defined by the usage characteristics and the user base.
    • We still need the following:
    • Total Users (estimated)
    • Active Users
    • % Active Users
    • Peak concurrent users
    • % Peak concurrent users
    • Don’t use the SharePoint System center capacity planning tool!!!
  • SharePoint 2010 Architecture PlanningCAPACITY MODEL
    • Try not to over/undersize deployment
    • Determine peak demand benchmark
    • Plan for unplanned peak ‘spikes’
    • Use reference architectures as a starting point
    • Stay within Microsoft recommended boundaries
    (http://technet.microsoft.com/en-us/library/cc262787.aspx)
  • SharePoint 2010 Infrastructure Improvements
  • SharePoint 2010 Infrastructure ImprovementsVersion and Edition Changes
  • SharePoint 2010 Infrastructure ImprovementsService Applications
    • SSP concept replaced with Service Applications
    • Each service runs independently, providing application isolation
    • All SSP functionality moved to databases, so they can be consumed from multiple servers more easily
    • New products use this framework
    • Get-SPServiceApplicationcmdlet shows list of Service Applications
  • SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)
  • SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part II)
  • SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part III)
    • New database size recommendations
    • Collaboration or write-heavy workloads:  200 GB
    • Document management or read-heavy workloads: 1 TB
    • Rule of thumb for sizing content databases is 0.75 IOPS per GB. (separate spindles to achieve IOPS!!)
    • Consider using Remote BLOB storage (RBS):
    • Sites that contain large files that are infrequently accessed, such as knowledge repositories.
    • Sites with terabytes of data.
    • Sites that host video or media files.
  • SharePoint 2010 Infrastructure ImprovementsMulti-tenancy – A Quick Overview
    • Isolation of data, operational services, and management
    • Partitioning of Data
    • Usage Isolation
    • Administrative Isolation
    • Customisations
    • Operations
    • New functionality targeted at hosting SharePoint sites
    • More centralised control over hardware and data storage
    • Simplified management and scriptability
    • Block setup of ‘rogue’ SharePoint deployments
    • “Site subscriptions” group site collections based on tenants
    • Features and services mapped to tenants
  • SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)
    • The ability to uniquely separate each customer on a shared environment
    1
    2
    SA
    WA
    Tenant 1
    Tenant 2
    SC
    SC
    SC
    SC
    SC
    SC
    SC
    SC
    SC
    SC
  • SharePoint 2007 vs. SharePoint 2010 Server Architecture Models
  • SharePoint 2007 vs. 2010 RolesDedicated SQL Database Server (Also Similar)
    2007
    2010
  • SharePoint 2007 vs. 2010 RolesSmallest Highly Available Farm
    2007
    2010
  • SharePoint 2010 ArchitectureMedium Sized Farm
  • SharePoint 2010 ArchitectureLarge Farm
  • Restructuring SharePoint Content
  • Content Database and Site CollectionsRearchitecting for Scalability
    • Change new SP2010 Farm to model of distributed content databases, within reason (more than 50 per SQL instance is not recommended)
    • Distribute content across Site Collections from the beginning as well
    • Allow your environment to scale and your users to ‘grow into’ their SharePoint site collections
    • Consider MultiTenancy for hosting
  • Sample SP Logical Architecture
  • RestructuringUpgrade / Migration
    • In-Place upgrade (not recommended)
    • Visual upgrade
    • Database Attach Upgrade
    • STSADM –Export of sub-webs
    • Third-Party Migration Tools
    • Metalogix
    • Quest
    • AvePoint
    • Etc…
  • SharePoint 2010 Virtual Farm Architecture
  • Can you Virtualize SharePoint 2010 Production Servers?
    Answer is yes, you can (it is supported), but with caveats
    Must architect the environment properly!
    Not taking into account Disk/Proc/Mem, and other host and guest environments can make a virtualized environment run slowly
  • Virtual Host Guidelines
  • SP2010 Role Virtualization
  • SharePoint Guest Guidelines
  • SharePoint Role VM Guidelines
  • SQL Server VM Guidelines
  • Sample SharePoint 2010 Virtualized Farm Architecture
  • Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA
    • Allows Organizations that wouldn’t normally be able to have a test environment to run one
    • Allows for separation of the database role onto a dedicated server
    • Can be more easily scaled out in the future
  • Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA
  • Virtualized Farm ArchitectureHighly Available Farm with only Two Servers
    • High-Availability across Hosts
    • All components Virtualized
    • Uses only two Windows Ent Edition Licenses
  • Virtualized Farm ArchitectureHighly Available Farm with only Two Servers
  • Virtualized Farm ArchitectureBest Practice Virtual/Physical with HA/Perf
    • Highest transaction servers are physical
    • Multiple farm support, with DBs for all farms on the SQL cluster
  • Virtualized Farm ArchitectureLarge Virtual Farms
  • NUMA Memory Guidelines
  • NUMA Example: 2x Quad Core, 64GB RAM
    Proc 1
    Proc 2
  • NUMA Example: 2x Quad Core, 8GB RAM
    Proc 1
    Proc 2
  • Virtualization Performance Monitoring
  • Virtualization Performance MonitoringPerformance Counters and Thresholds on Hosts
    Network Bandwidth – Bytes Total/sec
    <40% Utilization = Good
    41%-64% = Caution
    >65% = Trouble
    Network Latency - Output Queue Length
    0 = Good
    1-2= OK
    >2 = Trouble
    Processor
    <60% Utilization = Good
    60%-90% = Caution
    >90% = Trouble
    Available Memory
    50% and above = Good
    10%-50% = OK
    <10% = Trouble
    Disk – Avg. Disk sec/Read or Avg. Disk sec/Write
    Up to 15ms = fine
    15ms-25ms = Caution
    >25ms = Trouble
  • Virtualization Performance MonitoringPerformance Counters and Thresholds on Guests
    Network Bandwidth – Virtual NIC Bytes Total/sec
    <40% Utilization = Good
    41%-64% = Caution
    >65% = Trouble
    Network Latency - Output Queue Length
    0 = Good
    1-2= OK
    >2 = Trouble
    Processor (N/A)
    Available Memory
    50% and above = Good
    10%-50% = OK
    <10% = Trouble
    Disk – Avg. Disk sec/Read or Avg. Disk sec/Write
    Up to 15ms = fine
    15ms-25ms = Caution
    >25ms = Trouble
  • SharePoint Virtualization Support
  • Microsoft Support of SharePoint Virtualization
    Microsoft’s official SharePoint support stance is that any SharePoint role or service is supported for hardware Virtualization, including SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2. There are only three requirements for Virtualization that must be satisfied, these are as follows:
    Hardware-assisted Virtualization, which is available in processors that include a Virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology.
    Hardware-enforced Data Execution Prevention (DEP) is available and enabled.
    Either deployed on Microsoft Hyper-V (RTM or R2 version) or a validated third-party hypervisor that is part of the Server Virtualization Validation Program (SVVP) – KB 897615
  • Windows Server 2008 R2 Hyper-V
  • Hyper-V R2 for SP2010Overview
  • System Center Virtual Machine Manager 2008 R2
  • Virtualization Host and Guest Management Platform
    Part of the System Center Management Suite, which includes the following:
    System Center Operations Manager 2007
    System Center Data Protection Manager 2007
    System Center Configuration Manager 2007 R2
    System Center Mobile Device Manager 2007
    System Center Essentials 2007
    System Center Capacity Planner 2007
    System Center Service Manager 2010
    System Center Virtual Machine Manager (VMM)
  • New version out (VMM 2008 R2)
    VMM 2008 R2 has P2V (Physical to virtual migration) and V2V (VMware Guest migration to Hyper-V) tools
    For SharePoint, allows for creation of SharePoint template servers that can be quickly provisioned for test farms or for new farm members in production
    Can manage both Hyper-V and VMware guests (though must ‘go through’ a Virtual Center server to manage VMware guests.)
    Self-Service Portal allows end users and remote admins to be able to provision their own virtual machines based on templates
    PowerShell support allows for scripted provisioning of SharePoint 2010 or other servers into a farm
    System Center Virtual Machine Manager (VMM) 2008 R2
  • Quick SP2010 Farm Provisioning with VMM 2008 R2
    Create new Virtual Guest (Windows Server 2008 R2)
    Install SP2010 Binaries. Stop before running Config Wizard
    Turn Virtual Guest into Template, modify template to allow it to be added into domain
    Add PowerShell script to run on first login, allowing SP to be added into farm or to create new farm
    Voila! 15 minute entire farm provisioning…
  • Quick Farm Provisioning with VMM 2008 R2
  • Farm Provisioning Script(Thanks to Muhanad Omar, MVP)
    $configType = read-host "Do you wish to join an existing Farm? (Y/N)"
    if ($ConfigType -eq "Y") {
    $DatabaseServer = read-host "Sounds good. Please specify the name of your SQL Server";
    $ConfigDB = read-host "Next, specify the name of your Farm Configuration Database";
    $Passphrase = read-host "Finally, please enter your Farm passphrase" -assecurestring
    } else {
    $DatabaseServer = read-host "In that case, let's create a new Farm. Please specify the name of your SQL Server";
    $FarmName = read-host "Please specify a name for your Farm (ex. SP2010Dev)";
    $ConfigDB = $FarmName+"_ConfigDB";
    $AdminContentDB = $FarmName+"_Admin_ContentDB";
    Write-Host "Please enter the credentials for your Farm Account (ex. CONTOSOSP_Farm)";
    $FarmAcct = Get-Credential;
    $Passphrase = read-host "Enter a secure Farm passphrase" -assecurestring;
    $Port = read-host "Enter a port number for the Central Administration Web App";
    $Authentication = read-host "Finally, specify your authentication provider (NTLM/Kerberos)";
    }
    if ($ConfigType -eq "Y") {
    Add-PSSnapinMicrosoft.SharePoint.PowerShell;
    Connect-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -Passphrase $Passphrase
    } else {
    Add-PSSnapinMicrosoft.SharePoint.PowerShell;
    Write-Host "Your SharePoint Farm is being configured..."
    New-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -AdministrationContentDatabaseName $AdminContentDB -Passphrase $Passphrase -FarmCredentials $FarmAcct
    }
    Initialize-SPResourceSecurity
    Install-SPService
    Install-SPFeature -AllExistingFeatures
    New-SPCentralAdministration -Port $Port -WindowsAuthProvider $Authentication
    Install-SPHelpCollection -All
    Install-SPApplicationContent
    Write-Host "Your SharePoint 2010 Farm has been created!"
    if ($ConfigType -eq "N") {
    $WebAppCreation = read-host "Would you like to provision a Web Application using the default Team Site Template? (Y/N)";
    if ($WebAppCreation -eq "Y") {
    $HostHeaderQ = read-host "Would you like to specify a host header? (Y/N)";
    if ($HostHeaderQ -eq "Y") {
    $HostHeader = read-host "Please specify a host header for your Web Application (ex. intranet.contoso.com)";
    $URL = "http://"+$HostHeader;
    Write-Host "Creating your Web Application...";
    New-SPWebApplication -Name "SharePoint 2010 Team Site" -Port 80 -HostHeader $FQDN -Url $URL -ApplicationPool "Content_AppPool" -ApplicationPoolAccount (Get-SPManagedAccount $FarmAcct.UserName) -DatabaseServer $DatabaseServer -DatabaseName $FarmName+"_TeamSite_ContentDB_01";
    New-SPSite $URL -OwnerAlias $FarmAcct.UserName -Language 1033 -Template "STS#0" -Name "Team Site";
    Write-Host "Configuration completed.";
    }
    else {
    Write-Host "Creating a Web Application using the default Team Site Template..."
    }
    }
    else {
    Write-Host "Configuration completed.";
    }
    }
    Write-Host "Press any key to continue..."
    $x = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
  • Summary
    Understand how to use the Service Application architecture of SharePoint 2010
    Plan for a distributed data model, especially for document management enviroments
    If considering virtualization of SharePoint, make sure to architect host/guest environment properly
  • Dúvidas?
    Michael Noel
    Twitter: @MichaelTNoel
    www.cco.com
    Por favor preencha a avaliação
  • © 2008 Microsoft Corporation.Todos os direitos reservados.Microsoft, Windows, Windows Vista e outros nomes de produtos são ou podem ser marcas registradas e/ou marcas comerciais nos EUA e/ou outros países.
    Este documento é meramente informativo e representa a visão atual da Microsoft Corporation a partir da data desta apresentação.Como a Microsoft deve atender a condições de mercado em constante alteração, este documento não deve ser interpretado como um compromisso por parte da Microsoft, e a Microsoft não pode garantir a precisão de qualquer informação fornecida após a data desta apresentação.A MICROSOFT NÃO DÁ QUALQUER GARANTIA, SEJA ELA EXPRESSA, IMPLÍCITA OU ESTATUTÁRIA, REFERENTE ÀS INFORMAÇÕES DESTA APRESENTAÇÃO.