Building the Perfect SharePoint 2010 Farm - TechEd Australia 2011


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Building the Perfect SharePoint 2010 Farm - TechEd Australia 2011

  1. 1.
  2. 2. Building the ‘Perfect’ SharePoint 2010 FarmBest Practices from the Field<br />Michael Noel<br />Partner<br />Convergent Computing<br />SESSION CODE: #<br />(c) 2011 Microsoft. All rights reserved.<br />
  3. 3. Michael Noel<br />Sydney<br />Brisbane<br />Canberra<br />Tasmania<br />Katoomba<br />Skippy<br />Hungry<br />Quokkas<br />Bondi<br />Melbourne<br />12 (11)<br />Apostles<br />Adelaide<br />Perth<br />Great to be back in Beautiful Australia! <br />
  4. 4. What we will cover<br />Examine various SharePoint 2010 farm architecture best Practices that have developed over the past year<br />Examine SharePoint Best Practice Farm Architecture<br />Understand SharePoint VirtualisationOptions<br />Explore SharePoint DR and HA strategies using Database Mirroring<br />Explore other common best Practices (RBS, SSL, NLB)<br />Examine best practice security for SharePoint<br />A large amount of best Practices covered (i.e. Drinking through a fire hose,) goal is for you to be able to take away at least 2-3 useful pieces of information that can be used in your environment<br />
  5. 5. Architecting the Farm<br />
  6. 6. Architecting the FarmUnderstanding the Three Tiers of SharePoint Infrastructure<br />
  7. 7. Architecting the FarmSmall Farm Examples<br />‘All-in-One’ (Avoid)<br />DB and SP Roles Separate<br />
  8. 8. Architecting the FarmSmallest Highly Available Farm<br />2 SharePoint Servers running Web and Service Apps<br />2 Database Servers (Clustered or Mirrored)<br />1 or 2 Index Partitions with equivalent query components<br />Smallest farm size that is fully highly available<br />
  9. 9. Architecting the FarmBest Practice ‘Six Server Farm’<br />2 Dedicated Web Servers (NLB)<br />2 Service Application Servers<br />2 Database Servers (Clustered or Mirrored)<br />1 or 2 Index Partitions with equivalent query components<br />
  10. 10. Architecting the FarmScaling to Large Farms<br />Multiple Dedicated Web Servers<br />Multiple Dedicated Service App Servers<br />Multiple Dedicated Query Servers<br />Multiple Dedicated Crawl Servers, with multiple Crawl DBs to increase parallelisation of the crawl process<br />Multiple distributed Index partitions (max of 10 million items per index partition)<br />Two query components for each Index partition, spread among servers<br />
  11. 11. Previously a third party product ($$$$)<br />More reasonable pricing now<br />Highly tuned and specialised search engine for SharePoint and also as an enterprise search platform<br />Replaces SharePoint 2010 Native Search if used<br />‘Net new’ features built-in.<br />Architecting the FarmFAST Search<br />
  12. 12. Architecting the FarmFAST Search – Comparison Matrix – Slide 1 of 2<br />
  13. 13. Architecting the FarmFAST Search – Comparison Matrix – Slide 2 of 2<br />
  14. 14. Virtualisation of SharePoint Servers<br />
  15. 15. Virtualisation of SharePoint ServersCaveats – Be Sure to Understand Virtualisation Concepts<br />
  16. 16. Virtualisation of SharePoint ServersVirtual Guest Processor and Memory Guidelines<br />
  17. 17. Virtualisation of SharePoint ServersSample 1: Small Single Server Environment / No HA<br /><ul><li>Allows organisations that wouldn’t normally be able to have a test environment to run one
  18. 18. Allows for separation of the database role onto a dedicated server
  19. 19. Can be more easily scaled out in the future</li></li></ul><li>Virtualisation of SharePoint ServersSample 2: Two Server Highly Available Farm<br /><ul><li>High-Availability across Hosts
  20. 20. All components Virtualised
  21. 21. Uses only two Windows Ent Edition Licenses</li></li></ul><li>Virtualisation of SharePoint ServersSample 3: Mix of Physical and Virtual Servers – Best Perf<br /><ul><li>Highest transaction servers are physical
  22. 22. Multiple farm support, with DBs for all farms on the SQL cluster</li></li></ul><li>Virtualisation of SharePoint ServersSample 4: Scaling to Large Virtual Environments<br />
  23. 23. Virtualisation of SharePoint ServersVirtualisation Performance Monitoring<br />Network Bandwidth – Bytes Total/sec<br /><40% Utilisation = 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 (Host Only)<br /><60% Utilisation= 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 />
  24. 24. Virtualisation of SharePoint ServersQuick Farm Provisioning using VMM/Virtual Center<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 />End Result - 15 minute entire farm provisioning…quickly add servers into existing farms or create new farms (Test, Dev, Prod) on demand<br />
  25. 25. Demo<br />Quick Farm Provisioning with VMM 2008 R2<br />
  26. 26. Data Management<br />
  27. 27. Start with a distributed architecture of content databases from the beginning, within reason (more than 50 per SQL instance is not recommended)<br />Distribute content across Site Collections from the beginning as well, it is very difficult to extract content after the face<br />Allow your environment to scale and your users to ‘grow into’ their SharePoint site collections<br />Data ManagementDistribute Data Across Content DBs and Site Collections<br />
  28. 28.
  29. 29. BLOBs are unstructured content stored in SQL<br />Includes all documents, pictures, and files stored in SharePoint<br />Excludes Metadata and Context, information about the document, version #, etc.<br />Until recently, could not be removed from SharePoint Content Databases<br />Classic problem of structured vs. unstructured data – unstructured data doesn’t really belong in a SQL Server environment<br />Data ManagementBinary Large OBject (BLOB) Storage<br />
  30. 30. Data ManagementGetting your BLOBs out of the Content DBs<br />Can reduce dramatically the size of Content DBs, as upwards of 80%-90% of space in content DBs is composed of BLOBs<br />Can move BLOB storage to more efficient/cheaper storage<br />Improve performance and scalability of your SharePoint deployment – But highly recommended to use third party<br />
  31. 31. SQL Database Optimisation<br />
  32. 32. SQL Database OptimisationContent Databases Distributed Between Multiple Volumes<br />Volume #1<br />Volume #2<br />Volume #3<br />Volume #4<br />DB-A<br />File 1<br />DB-B<br />File 1<br />DB-A<br />File 2<br />DB-B<br />File 2<br />DB-A<br />File 3<br />DB-B<br />File 3<br />DB-A<br />File 4<br />DB-B<br />File 4<br />Tempdb File 1<br />Tempdb File 2<br />Tempdb File 3<br />Tempdb File 4<br />
  33. 33. SQL Database OptimisationContent Databases Distributed Between Multiple Volumes<br />Break Content Databases and TempDB into multiple files (MDF, NDF), total should equal number of physical processors (not cores) on SQL server.<br />Pre-size Content DBs and TempDB to avoid fragmentation<br />Separate files onto different drive spindles for best IO perf.<br />Example: 100GB total Content DB on Four-way SQL Server would have four database files distributed across four sets of drive spindles = 25GB pre-sized for each file.<br />
  34. 34. SQL Database OptimisationTempDB Best Practices<br />TempDB is critical for performance<br />Pre-size to 20% of the size of the largest content database.<br />Break into multiple files across spindles as noted<br />Note there is a separate TempDB for each physical instance<br />Note that if using SQL Transparent Data Encryption (TDE) for any databases in an instance, the tempDB is encrypted.<br />
  35. 35. High Availability and Disaster Recovery<br />
  36. 36. Clustering is Shared Storage, can’t survive storage failure, makes Mirroring more attractive<br />Clustering fails over more quickly<br />Mirroring is not supported for all databases, but Clustering is<br />Both Clustering and Mirroring can be used at the same time (Instance to Instance)<br />High Availability and Disaster RecoveryData Tier – Clustering vs. Mirroring<br />
  37. 37. High Availability and Disaster RecoveryData Tier – SQL Database Mirroring<br />Introduced in SQL 2005 SP1<br />Greatly improved in SQL 2008 and now SQL 2008 R2<br />Available in Enterprise and Standard (Synchronous only) editions<br />Works by keeping a mirror copy of a database or databases on two servers<br />Can be used locally, or the mirror can be remote<br />Can be set to use a two-phase commit process to ensure integrity of data across both servers<br />Can be combined with traditional shared storage clustering to further improve redundancy<br />SharePoint 2010 is now Mirroring aware!<br />
  38. 38. High Availability and Disaster RecoveryData Tier – Database Mirroring Model #1 – Single Site<br />Single Site<br />Synchronous Replication<br />Uses a SQL Witness Server to Failover Automatically<br />Mirror all SharePoint DBs in the Farm<br />Use a SQL Alias to switch to Mirror Instance<br />
  39. 39. High Availability and Disaster RecoveryData Tier – Database Mirroring Model #2 – Cross-Site with HA<br />Two Sites<br />1-10 ms Latency max<br />1Gb Bandwidth minimum<br />Farm Servers in each location<br />Auto Failover<br />
  40. 40. High Availability and Disaster RecoveryData Tier – Database Mirroring Model #2 – Remote Farm<br />Two Sites<br />Two Farms<br />Mirror only Content DBs<br />Failover is Manual<br />Read-only Mode possible<br />Must Re-Attach and Re-Index<br />
  41. 41. High Availability and Disaster RecoveryData Tier – Database Support for Mirroring – Slide 1 of 2<br />
  42. 42. High Availability and Disaster RecoveryData Tier – Database Support for Mirroring – Slide 2 of 2<br />
  43. 43. High Availability and Disaster RecoveryTwo Node/Two Instance Cluster – Take Advantage of both servers<br />
  44. 44. High Availability and Disaster RecoveryNetwork Load Balancing<br />Hardware Based Load Balancing (F5, Cisco, Citrix NetScaler – Best performance and scalability<br />Software Windows Network Load Balancing fully supported by MS, but requires Layer 2 VLAN (all packets must reach all hosts.) Layer 3 Switches must be configured to allow Layer 2 to the specific VLAN.<br />If using Unicast, use two NICs on the server, one for communications between nodes.<br />If using Multicast, be sure to configure routers appropriately<br />Set Affinity to Single (Sticky Sessions)<br />If using VMware, note fix to NLB RARP issue (<br />
  45. 45. High Availability and Disaster RecoveryWindows Software Network Load Balancing Recommendations<br />Best Practice – Create Multiple Web Apps with Load-balanced VIPs (Sample below)<br />Web Role Servers<br /> ( – Web Role Server #1<br /> ( – Web Role Server #2<br />Clustered VIPs shared between SP1 and SP2 (Create A records in DNS)<br /> ( - Cluster<br /> ( – SP Central Admin<br /> ( – Inbound Email VIP<br /> ( – Main SP Web App (can be multiple)<br /> ( – Main MySites Web App<br />
  46. 46. SharePoint Installation<br />
  47. 47. SharePoint InstallationScripted Installations<br />Good to understand how to install SharePoint from the command-line, especially if setting up multiple servers.<br />Allows for options not available in the GUI, such as the option to rename databases to something easier to understand.<br />Use PowerShell with SharePoint 2010<br />Sample scripts available for download…<br />
  48. 48. Function Configure-SPSearch {<br /> PARAM($AppPool, $FarmName, $SearchServiceAccount)<br /> $searchServiceInstance = Get-SPEnterpriseSearchServiceInstance -local<br /> Start-SPEnterpriseSearchServiceInstance -Identity $searchServiceInstance<br /> $dbName = $FarmName + "_SearchServiceApplication"<br /> $searchApplication = New-SPEnterpriseSearchServiceApplication -Name "$FarmName Search Service Application" -ApplicationPool $AppPool -DatabaseName $dbName<br /> $searchApplicationProxy = New-SPEnterpriseSearchServiceApplicationProxy -name "$FarmName Search Service Application Proxy" -SearchApplication $searchApplication<br /> Set-SPEnterpriseSearchAdministrationComponent -SearchApplication $searchApplication -SearchServiceInstance $searchServiceInstance<br /> $crawlTopology = New-SPEnterpriseSearchCrawlTopology -SearchApplication $searchApplication<br /> $crawlDatabase = Get-SPEnterpriseSearchCrawlDatabase -SearchApplication $searchApplication<br /> New-SPEnterpriseSearchCrawlComponent -CrawlTopology $crawlTopology -CrawlDatabase $crawlDatabase -SearchServiceInstance $searchServiceInstance<br /> while($crawlTopology.State -ne "Active")<br /> {<br /> $crawlTopology | Set-SPEnterpriseSearchCrawlTopology -Active -ErrorActionSilentlyContinue<br /> if ($crawlTopology.State -ne "Active")<br /> {<br /> Start-Sleep -Seconds 10<br /> }<br /> }<br /> $queryTopology = New-SPenterpriseSEarchQueryTopology -SearchApplication $searchApplication -partitions 1<br /> $searchIndexPartition = Get-SPEnterpriseSearchIndexPartition -QueryTopology $queryTopology<br /> New-SPEnterpriseSearchQueryComponent -indexpartition $searchIndexPartition -QueryTopology $queryTopology -SearchServiceInstance $searchServiceInstance<br /> $propertyDB = Get-SPEnterpriseSearchPropertyDatabase -SearchApplication $searchApplication<br /> Set-SPEnterpriseSearchIndexPartition $searchIndexPartition -PropertyDatabase $propertyDB<br /> while ($queryTopology.State -ne "Active")<br /> {<br /> $queryTopology | Set-SPEnterpriseSearchQueryTopology -Active -ErrorActionSilentlyContinue<br /> if ($queryTopology.State -ne "Active")<br /> {<br /> Start-Sleep -Seconds 10<br /> }<br /> }<br />}<br />SharePoint InstallationSamples Scripts –<br />
  49. 49. SharePoint InstallationSome Manual Service Apps Still Required<br />Due to complexity and/or bugs, certain Service Apps will need to be manually configured in most cases.<br />This includes the following:<br />PerformancePoint Service Application<br />User Profile Service Application<br />Web Analytics Service Application<br />
  50. 50. Security<br />
  51. 51. SharePoint SecurityLayers of Security in a SharePoint Environment<br />Infrastructure Security and Best Practices<br />Physical Security<br />Best Practice Service Account Setup<br />Kerberos Authentication<br />Data Security<br />Role Based Access Control (RBAC)<br />Transparent Data Encryption (TDE) of SQL Databases<br />Antivirus<br />Transport Security<br />Secure Sockets Layer (SSL) from Server to Client<br />IPSec from Server to Server<br />Edge Security<br />Inbound Internet Security (Forefront UAG/TMG)<br />Rights Management<br />
  52. 52. SharePoint SecurityInfrastructure – Sample List of Service Accounts<br />
  53. 53. SharePoint SecurityInfrastructure – Enable Kerberos when using Classic-Auth<br />When creating any Web Applications in Classic-mode, USE KERBEROS. It is much more secure and also faster with heavy loads as the SP server doesn’t have to keep asking for auth requests from AD.<br />Kerberos auth does require extra steps, which makes people shy away from it, but once configured, it improves security considerably and can improve performance on high-load sites.<br />Should also be configured on SPCA Site! (Best Practice = Configure SPCA for NLB, SSL, and Kerberos (i.e. <br />
  54. 54. SharePoint SecurityData – Role Based Access Control (RBAC)<br />Role Groups defined within Active Directory (Universal Groups) – i.e. ‘Marketing,’ ‘Sales,’ ‘IT,’ etc.<br />Role Groups added directly into SharePoint ‘Access Groups’ such as ‘Contributors,’ ‘Authors,’ etc.<br />Simply by adding a user account into the associated Role Group, they gain access to whatever rights their role requires.<br />SharePoint Group<br />
  55. 55. SharePoint SecurityData - Transparent Data Encryption (TDE)<br />New in SQL Server 2008<br />Only Available with the Enterprise Edition<br />Seamless Encryption of Individual Databases<br />Transparent to Applications, including SharePoint<br />
  56. 56. SharePoint SecurityData - Use SharePoint-Aware Antivirus (3rd Party or FPS)<br />
  57. 57. SharePoint SecurityTransport - Secure Sockets Layer (SSL) Encryption<br />External or Internal Certs highly recommended<br />Protects Transport of content<br />20% overhead on Web Servers<br />Can be offloaded via SSL offloaders if needed<br />Don’t forget for SPCA as well!<br />
  58. 58. SharePoint SecurityTransport – IPSec from Server to Server<br />By default, traffic between SharePoint Servers (i.e. Web and SQL) is unencrypted<br />IPSec encrypts all packets sent between servers in a farm<br />For very high security scenarios when all possible data breaches must be addressed<br />
  59. 59. SharePoint SecurityEdge – Forefront Unified Access Gateway<br />
  60. 60. SharePoint SecurityRights Management - Active Directory Rights Management Services<br />AD RMS is a form of Digital Rights Management (DRM) technology, used in various forms to protect content<br />Used to restrict activities on files AFTER they have been accessed:<br />Cut/Paste<br />Print<br />Save As…<br />Directly integrates with SharePoint DocLibs<br />
  61. 61. For More Information<br />SharePoint 2010 Unleashed from SAMS Publishing (<br />Windows Server 2008 R2 Unleashed and/or Hyper-V Unleashed (<br />Microsoft ‘Virtualizing SharePoint Infrastructure’ Whitepaper ( <br />Microsoft SQL Mirroring Case Study ( )<br />Failover Mirror PowerShell Script ( )<br />SharePoint Kerberos Guidance (<br />SharePoint Installation Scripts (<br />Contact us at<br />
  62. 62. Complete an Evaluation online and enter to WIN these prizes!<br /><Prizes & Process TBC><br />(c) 2011 Microsoft. All rights reserved.<br />
  63. 63. Thanks for attending!Questions?<br />Michael Noel<br />Twitter: @MichaelTNoel<br /><br />Slides:<br />
  64. 64. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.<br />The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.<br />(c) 2011 Microsoft. All rights reserved.<br />
  65. 65.<br />Sessions On-Demand & Community<br /><br />Microsoft Certification & Training Resources<br />http://<br />Resources for IT Professionals<br /><br />Resources for Developers<br />Resources<br />(c) 2011 Microsoft. All rights reserved.<br />