0
SETEMBRO, 2010 | SÃO PAULO<br />
CÓDIGO DA SESSÃO:OSP301<br />Arquitetura e topologias do SharePoint 2010<br />Michael Noel<br />Partner<br />Convergent Co...
Michael Noel<br /><ul><li>Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “Shar...
Partner at Convergent Computing (www.cco.com / +1(510)444-5700) –  San Francisco, USA Bay Area based Infrastructure/Securi...
SharePoint 2010 Architecture Planning Changes<br />
SharePoint 2010 Architecture PlanningUser Workloads<br /><ul><li>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!!! </li></li></ul><li>SharePoint 2010 Architecture PlanningC...
Determine peak demand benchmark
Plan for unplanned peak ‘spikes’
Use reference architectures as a starting point
Stay within Microsoft recommended boundaries</li></ul>(http://technet.microsoft.com/en-us/library/cc262787.aspx)<br />
SharePoint 2010 Infrastructure Improvements<br />
SharePoint 2010 Infrastructure ImprovementsVersion and Edition Changes<br />
SharePoint 2010 Infrastructure ImprovementsService Applications<br /><ul><li>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</li></li></ul><li>SharePoint 2010 Infrastructure Improve...
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part II)<br />
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part III)<br /><ul><li>New database size recommendat...
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.</li></li></ul><li>SharePoint 2010 Infrastructure ImprovementsMulti-tenancy – A Quick...
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</li></li></ul><li>SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Datab...
SharePoint 2007 vs. SharePoint 2010 Server Architecture Models<br />
SharePoint 2007 vs. 2010 RolesDedicated SQL Database Server (Also Similar)<br />2007<br />2010<br />
SharePoint 2007 vs. 2010 RolesSmallest Highly Available Farm<br />2007<br />2010<br />
SharePoint 2010 ArchitectureMedium Sized Farm<br />
SharePoint 2010 ArchitectureLarge Farm<br />
Restructuring SharePoint Content<br />
Content Database and Site CollectionsRearchitecting for Scalability<br /><ul><li>Change new SP2010 Farm to model of distri...
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</li></li></ul><li>Sample SP Logical Architecture<br />
RestructuringUpgrade / Migration<br /><ul><li>In-Place upgrade (not recommended)
Upcoming SlideShare
Loading in...5
×

SharePoint 2010 Architecture - TechEd Brasil 2010

2,562

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,562
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
187
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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. 
  • Transcript of "SharePoint 2010 Architecture - TechEd Brasil 2010"

    1. 1. SETEMBRO, 2010 | SÃO PAULO<br />
    2. 2. CÓDIGO DA SESSÃO:OSP301<br />Arquitetura e topologias do SharePoint 2010<br />Michael Noel<br />Partner<br />Convergent Computing<br />
    3. 3. Michael Noel<br /><ul><li>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 .
    4. 4. 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</li></li></ul><li>AgendaWhat we will cover<br />Physical SharePoint Server Architecture<br />Architecture Planning Changes<br />SharePoint Databases<br />Service Applications<br />Virtual SharePoint Server Architecture<br />Virtual Host Guidelines<br />Virtual Guest Guidelines<br />Sample Virtual Environments for SharePoint 2010<br />
    5. 5. SharePoint 2010 Architecture Planning Changes<br />
    6. 6. SharePoint 2010 Architecture PlanningUser Workloads<br /><ul><li>Capacity planning is similar to MOSS2007
    7. 7. Usage now broken down by workload
    8. 8. A workload is defined by the usage characteristics and the user base.
    9. 9. We still need the following:
    10. 10. Total Users (estimated)
    11. 11. Active Users
    12. 12. % Active Users
    13. 13. Peak concurrent users
    14. 14. % Peak concurrent users
    15. 15. Don’t use the SharePoint System center capacity planning tool!!! </li></li></ul><li>SharePoint 2010 Architecture PlanningCAPACITY MODEL<br /><ul><li>Try not to over/undersize deployment
    16. 16. Determine peak demand benchmark
    17. 17. Plan for unplanned peak ‘spikes’
    18. 18. Use reference architectures as a starting point
    19. 19. Stay within Microsoft recommended boundaries</li></ul>(http://technet.microsoft.com/en-us/library/cc262787.aspx)<br />
    20. 20. SharePoint 2010 Infrastructure Improvements<br />
    21. 21. SharePoint 2010 Infrastructure ImprovementsVersion and Edition Changes<br />
    22. 22. SharePoint 2010 Infrastructure ImprovementsService Applications<br /><ul><li>SSP concept replaced with Service Applications
    23. 23. Each service runs independently, providing application isolation
    24. 24. All SSP functionality moved to databases, so they can be consumed from multiple servers more easily
    25. 25. New products use this framework
    26. 26. Get-SPServiceApplicationcmdlet shows list of Service Applications</li></li></ul><li>SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)<br />
    27. 27. SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part II)<br />
    28. 28. SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part III)<br /><ul><li>New database size recommendations
    29. 29. Collaboration or write-heavy workloads:  200 GB
    30. 30. Document management or read-heavy workloads: 1 TB
    31. 31. Rule of thumb for sizing content databases is 0.75 IOPS per GB. (separate spindles to achieve IOPS!!)
    32. 32. Consider using Remote BLOB storage (RBS):
    33. 33. Sites that contain large files that are infrequently accessed, such as knowledge repositories.
    34. 34. Sites with terabytes of data.
    35. 35. Sites that host video or media files.</li></li></ul><li>SharePoint 2010 Infrastructure ImprovementsMulti-tenancy – A Quick Overview<br /><ul><li>Isolation of data, operational services, and management
    36. 36. Partitioning of Data
    37. 37. Usage Isolation
    38. 38. Administrative Isolation
    39. 39. Customisations
    40. 40. Operations
    41. 41. New functionality targeted at hosting SharePoint sites
    42. 42. More centralised control over hardware and data storage
    43. 43. Simplified management and scriptability
    44. 44. Block setup of ‘rogue’ SharePoint deployments
    45. 45. “Site subscriptions” group site collections based on tenants
    46. 46. Features and services mapped to tenants</li></li></ul><li>SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)<br /><ul><li>The ability to uniquely separate each customer on a shared environment</li></ul>1<br />2<br />SA<br />WA<br />Tenant 1<br />Tenant 2<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />
    47. 47. SharePoint 2007 vs. SharePoint 2010 Server Architecture Models<br />
    48. 48. SharePoint 2007 vs. 2010 RolesDedicated SQL Database Server (Also Similar)<br />2007<br />2010<br />
    49. 49. SharePoint 2007 vs. 2010 RolesSmallest Highly Available Farm<br />2007<br />2010<br />
    50. 50. SharePoint 2010 ArchitectureMedium Sized Farm<br />
    51. 51. SharePoint 2010 ArchitectureLarge Farm<br />
    52. 52. Restructuring SharePoint Content<br />
    53. 53. Content Database and Site CollectionsRearchitecting for Scalability<br /><ul><li>Change new SP2010 Farm to model of distributed content databases, within reason (more than 50 per SQL instance is not recommended)
    54. 54. Distribute content across Site Collections from the beginning as well
    55. 55. Allow your environment to scale and your users to ‘grow into’ their SharePoint site collections
    56. 56. Consider MultiTenancy for hosting</li></li></ul><li>Sample SP Logical Architecture<br />
    57. 57. RestructuringUpgrade / Migration<br /><ul><li>In-Place upgrade (not recommended)
    58. 58. Visual upgrade
    59. 59. Database Attach Upgrade
    60. 60. STSADM –Export of sub-webs
    61. 61. Third-Party Migration Tools
    62. 62. Metalogix
    63. 63. Quest
    64. 64. AvePoint
    65. 65. Etc…</li></li></ul><li>SharePoint 2010 Virtual Farm Architecture<br />
    66. 66. Can you Virtualize SharePoint 2010 Production Servers?<br />Answer is yes, you can (it is supported), but with caveats<br />Must architect the environment properly!<br />Not taking into account Disk/Proc/Mem, and other host and guest environments can make a virtualized environment run slowly<br />
    67. 67. Virtual Host Guidelines<br />
    68. 68. SP2010 Role Virtualization<br />
    69. 69. SharePoint Guest Guidelines<br />
    70. 70. SharePoint Role VM Guidelines<br />
    71. 71. SQL Server VM Guidelines<br />
    72. 72. Sample SharePoint 2010 Virtualized Farm Architecture<br />
    73. 73. Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA<br /><ul><li>Allows Organizations that wouldn’t normally be able to have a test environment to run one
    74. 74. Allows for separation of the database role onto a dedicated server
    75. 75. Can be more easily scaled out in the future</li></li></ul><li>Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA<br />
    76. 76. Virtualized Farm ArchitectureHighly Available Farm with only Two Servers<br /><ul><li>High-Availability across Hosts
    77. 77. All components Virtualized
    78. 78. Uses only two Windows Ent Edition Licenses</li></li></ul><li>Virtualized Farm ArchitectureHighly Available Farm with only Two Servers<br />
    79. 79. Virtualized Farm ArchitectureBest Practice Virtual/Physical with HA/Perf<br /><ul><li>Highest transaction servers are physical
    80. 80. Multiple farm support, with DBs for all farms on the SQL cluster</li></li></ul><li>Virtualized Farm ArchitectureLarge Virtual Farms<br />
    81. 81. NUMA Memory Guidelines<br />
    82. 82. NUMA Example: 2x Quad Core, 64GB RAM<br />Proc 1<br />Proc 2<br />
    83. 83. NUMA Example: 2x Quad Core, 8GB RAM<br />Proc 1<br />Proc 2<br />
    84. 84. Virtualization Performance Monitoring<br />
    85. 85. Virtualization Performance MonitoringPerformance Counters and Thresholds on Hosts<br />Network Bandwidth – Bytes Total/sec<br /><40% Utilization = Good<br />41%-64% = Caution<br />>65% = Trouble<br />Network Latency - Output Queue Length<br />0 = Good<br />1-2= OK<br />>2 = Trouble<br />Processor<br /><60% Utilization = Good<br />60%-90% = Caution<br />>90% = Trouble<br />Available Memory <br />50% and above = Good<br />10%-50% = OK<br /><10% = Trouble<br />Disk – Avg. Disk sec/Read or Avg. Disk sec/Write<br />Up to 15ms = fine<br />15ms-25ms = Caution<br />>25ms = Trouble<br />
    86. 86. Virtualization Performance MonitoringPerformance Counters and Thresholds on Guests<br />Network Bandwidth – Virtual NIC Bytes Total/sec<br /><40% Utilization = Good<br />41%-64% = Caution<br />>65% = Trouble<br />Network Latency - Output Queue Length<br />0 = Good<br />1-2= OK<br />>2 = Trouble<br />Processor (N/A)<br />Available Memory <br />50% and above = Good<br />10%-50% = OK<br /><10% = Trouble<br />Disk – Avg. Disk sec/Read or Avg. Disk sec/Write<br />Up to 15ms = fine<br />15ms-25ms = Caution<br />>25ms = Trouble<br />
    87. 87. SharePoint Virtualization Support<br />
    88. 88. Microsoft Support of SharePoint Virtualization<br />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:<br />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. <br />Hardware-enforced Data Execution Prevention (DEP) is available and enabled.<br />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<br />
    89. 89. Windows Server 2008 R2 Hyper-V<br />
    90. 90. Hyper-V R2 for SP2010Overview<br />
    91. 91. System Center Virtual Machine Manager 2008 R2<br />
    92. 92. Virtualization Host and Guest Management Platform<br />Part of the System Center Management Suite, which includes the following:<br />System Center Operations Manager 2007<br />System Center Data Protection Manager 2007<br />System Center Configuration Manager 2007 R2<br />System Center Mobile Device Manager 2007<br />System Center Essentials 2007<br />System Center Capacity Planner 2007<br />System Center Service Manager 2010<br />System Center Virtual Machine Manager (VMM)<br />
    93. 93. New version out (VMM 2008 R2)<br />VMM 2008 R2 has P2V (Physical to virtual migration) and V2V (VMware Guest migration to Hyper-V) tools<br />For SharePoint, allows for creation of SharePoint template servers that can be quickly provisioned for test farms or for new farm members in production<br />Can manage both Hyper-V and VMware guests (though must ‘go through’ a Virtual Center server to manage VMware guests.)<br />Self-Service Portal allows end users and remote admins to be able to provision their own virtual machines based on templates<br />PowerShell support allows for scripted provisioning of SharePoint 2010 or other servers into a farm<br />System Center Virtual Machine Manager (VMM) 2008 R2<br />
    94. 94. Quick SP2010 Farm Provisioning with VMM 2008 R2<br />Create new Virtual Guest (Windows Server 2008 R2)<br />Install SP2010 Binaries. Stop before running Config Wizard<br />Turn Virtual Guest into Template, modify template to allow it to be added into domain<br />Add PowerShell script to run on first login, allowing SP to be added into farm or to create new farm<br />Voila! 15 minute entire farm provisioning…<br />
    95. 95. Quick Farm Provisioning with VMM 2008 R2<br />
    96. 96. Farm Provisioning Script(Thanks to Muhanad Omar, MVP)<br />$configType = read-host "Do you wish to join an existing Farm? (Y/N)"<br />if ($ConfigType -eq "Y") { <br /> $DatabaseServer = read-host "Sounds good. Please specify the name of your SQL Server";<br /> $ConfigDB = read-host "Next, specify the name of your Farm Configuration Database";<br /> $Passphrase = read-host "Finally, please enter your Farm passphrase" -assecurestring<br />} else { <br /> $DatabaseServer = read-host "In that case, let's create a new Farm. Please specify the name of your SQL Server";<br /> $FarmName = read-host "Please specify a name for your Farm (ex. SP2010Dev)";<br /> $ConfigDB = $FarmName+"_ConfigDB";<br /> $AdminContentDB = $FarmName+"_Admin_ContentDB";<br /> Write-Host "Please enter the credentials for your Farm Account (ex. CONTOSOSP_Farm)";<br /> $FarmAcct = Get-Credential;<br /> $Passphrase = read-host "Enter a secure Farm passphrase" -assecurestring;<br /> $Port = read-host "Enter a port number for the Central Administration Web App";<br /> $Authentication = read-host "Finally, specify your authentication provider (NTLM/Kerberos)"; <br />}<br />if ($ConfigType -eq "Y") {<br /> Add-PSSnapinMicrosoft.SharePoint.PowerShell;<br /> Connect-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -Passphrase $Passphrase<br />} else {<br /> Add-PSSnapinMicrosoft.SharePoint.PowerShell;<br /> Write-Host "Your SharePoint Farm is being configured..."<br /> New-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -AdministrationContentDatabaseName $AdminContentDB -Passphrase $Passphrase -FarmCredentials $FarmAcct<br />}<br />Initialize-SPResourceSecurity<br />Install-SPService<br />Install-SPFeature -AllExistingFeatures<br />New-SPCentralAdministration -Port $Port -WindowsAuthProvider $Authentication<br />Install-SPHelpCollection -All<br />Install-SPApplicationContent<br />Write-Host "Your SharePoint 2010 Farm has been created!"<br />if ($ConfigType -eq "N") {<br /> $WebAppCreation = read-host "Would you like to provision a Web Application using the default Team Site Template? (Y/N)";<br /> if ($WebAppCreation -eq "Y") {<br /> $HostHeaderQ = read-host "Would you like to specify a host header? (Y/N)";<br /> if ($HostHeaderQ -eq "Y") {<br /> $HostHeader = read-host "Please specify a host header for your Web Application (ex. intranet.contoso.com)";<br /> $URL = "http://"+$HostHeader;<br /> Write-Host "Creating your Web Application...";<br /> 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";<br /> New-SPSite $URL -OwnerAlias $FarmAcct.UserName -Language 1033 -Template "STS#0" -Name "Team Site";<br /> Write-Host "Configuration completed.";<br /> }<br /> else {<br /> Write-Host "Creating a Web Application using the default Team Site Template..."<br /> }<br /> }<br /> else {<br /> Write-Host "Configuration completed.";<br /> } <br />}<br />Write-Host "Press any key to continue..."<br />$x = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")<br />
    97. 97. Summary<br />Understand how to use the Service Application architecture of SharePoint 2010<br />Plan for a distributed data model, especially for document management enviroments<br />If considering virtualization of SharePoint, make sure to architect host/guest environment properly<br />
    98. 98. Dúvidas?<br />Michael Noel<br />Twitter: @MichaelTNoel<br />www.cco.com<br />Por favor preencha a avaliação<br />
    99. 99. © 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.<br />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.<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×