Sharepoint 2010 architecture, ha and dr (tig)


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Sharepoint 2010 architecture, ha and dr (tig)

  1. 1. Sharepoint 2010 Architecture, HA & DR<br />Tihomir Ignatov<br />Sr. Consultant<br />Microsoft Corporation<br />Blog:<br />
  2. 2. Agenda<br />What is Sharepoint?<br />Application Architecture<br />Services Architecture<br />Web Server Components<br />Best Practices vs Real World<br />Limits & Boundaries<br />Scalability & High Availability<br />Deployment Topologies<br />Search Architecture<br />Disaster Recovery<br />
  3. 3. What is Sharepoint?<br /><br />Web application platform developed by Microsoft. It is designed as a centralized replacement for multiple web applications and supports various combinations of enterprise website requirements. It is typically associated with web content management and document managementsystems<br />SharePoint's multi-purpose platform allows for managing and provisioning of intranet portals, extranets and websites, document management and file management, collaboration spaces, social networking tools, enterprise search, business intelligence tooling, process/information integration, and third-party developed solutions. SharePoint can also be used as a web application development platform.<br />
  4. 4. What is Sharepoint? (2)<br />SharePoint is designed to be highly scalable. It is capable of supporting multiple organizations on a single 'server farm'. Microsoft provides SharePoint as a free product, sells premium editions with additional integration and functionality, and also provides SharePoint as a cloud computing solution as part of BPOS and Office 365. The product is also sold as a cloud solution by local third-party vendors.<br />SharePoint provides various methods for customization and configuration of web areas, all of which have granular governance configurations. Beyond basic page-editing, file-storing and custom design ('branding') capabilities, one of the more prevalent forms of configuration is the ability to install third-party customizations called 'web parts' (i.e. widgets/gadgets).<br />
  5. 5. Architecture in Sharepoint Deployments<br />Deployment Architecture<br />Network Architecture<br />Enterprise architecture<br />Server architecture<br />Permission architecture<br />Cloud architecture<br />Infrastructure architecture<br />Deployment Architecture<br />Software Architecture<br />Data architecture<br />Information architecture<br />Business architecture<br />
  6. 6. To build application that satisfies the business and IT requirements<br />Choosing appropriate technical solution based on the requirement and the maturity of the team involved<br />Sharepoint Architecture – What is it for?<br />
  7. 7. Architecture is Making ideas real<br />“Make everything as simple as possible, but not simpler.”<br />-Albert Einstein<br />
  8. 8. Sharepoint Architecture<br />
  9. 9. Application Architecture<br /><ul><li>IIS web site
  10. 10. Separate web.config</li></ul>Web Tier<br />http://itweb<br />Web application<br /><ul><li>http://itweb/sites/pmo
  11. 11. Or http://pmo
  12. 12. Separate Content DB, Security, Navigation
  13. 13. Separate “Limits and Boundaries”
  14. 14. Separate Customizations Scope</li></ul>Site Collection<br />Data Tier<br /><ul><li>Content DB size
  15. 15. Maintenance
  16. 16. Backup & Recovery</li></li></ul><li>Services Architecture<br />3rd party Service<br />BCS<br />Search<br />WAS<br />User Profiles<br />Excel Calc<br />http://itweb<br />http://hrweb<br />
  17. 17. Components<br />IIS<br />Services<br />GAC<br />Hive 14<br />
  18. 18. Always use best practices (BP) when is possible<br />Adapt your design to the business requirements<br />Do not hesitate to jump over the BP if is reasonable, but leave a track why (document it)<br />Always weigh out the business requirements against feature TCO (complexity, time, resources, price, etc.)<br />Say “NO” to your client, when the feature is expensive and low business impact<br />Best Practices vs. Real World<br />
  19. 19. Supportability<br />Use only SUPPORTED scenarios for customization and configuration<br />Do not use Quick & Dirty approach for production<br />What is supported?<br />Ask for supportability!<br />
  20. 20. Boundaries are absolute limits that cannot be exceeded by design.<br />Thresholds are those that have a default value that cannot be exceeded unless the value is modified. <br />Supported limits define the tested value for a given parameter. <br />Limits<br />Thresholds and supported limits guidelines are determined by performance. <br />
  21. 21. Some Important Limits<br />Software boundaries and limits at TechNet<br />
  22. 22. Capacity is directly affected by scalability<br />If your solution plans exceed the recommended guidelines <br />Evaluate the solution to ensure that compensations are made in other areas.<br />Flag these areas for testing and monitoring as you build your deployment.<br />Redesign or partition the solution to ensure that you do not exceed capacity guidelines.<br />Take Into Account…<br />
  23. 23. How to design the solution (Sub Sites vs. Site Collections vs. Web Applications)<br />Which SA to provision<br />Do not use the Farm Configuration Wizard<br />Important Decisions<br />
  24. 24. “Some” resources in Technet…<br />Consider the limits!<br />Storage and SQL capacity planning<br />For content databases<br />For Service Applications<br />Always test storage performance with SQLIO tool<br />Schedule meetings with storage administrators <br />Capacity Planning<br />My capacity planning tool:<br />
  25. 25. Browser and version<br />MS Office version<br />Client PCs – HW & SW configuration, load, other applications<br />Monitor and test page rendering performance on regular PC (not development) <br />Client Compatibilities<br />
  26. 26. Scale up or scale out?<br />When to scale?<br />What to scale?<br />Scalability<br />
  27. 27. Is the Sharepoint a business critical application?<br />Try to define SLA and down time – cost, operations, reliability <br />From scalability and capacity to availability<br />Database availability strategies – clustering or mirroring?<br />Service Applications redundancy strategies<br />SA that store data outside a database <br />SA that store data in databases<br />Search Service Application redundancy<br />High Availability<br />
  28. 28. Sharepoint Farm Topologies<br />Limited Deployments<br />
  29. 29. Sharepoint Farm Topologies<br />Small Farm Topologies<br />
  30. 30. Sharepoint Farm Topologies<br />Medium Farm Topologies<br />
  31. 31. Sharepoint Farm Topologies<br />Large Farm Topologies<br />
  32. 32. Search Physical & Logical Components<br />Web Application /<br />Search Proxy<br />Query Processor<br />WFE<br />Query Component<br />Index Partition<br />Crawl Component<br />Application Server<br />Search Admin Component<br />Single Box<br />Property DB<br />Crawl DB<br />Search Admin DB<br />SQL Server DB<br />
  33. 33. How the Search works?<br />Web Application /<br />Search Proxy<br />User Query<br />Query Results<br />Query Processor<br />Property DB<br />Query Component<br />Index Partition<br />Crawl DB<br />Crawl Component<br />Search Admin DB<br />Search Admin Component<br />Crawl defined by <br />Administrator<br />
  34. 34. Real World Example<br />
  35. 35. Disaster Recovery<br />D/R<br />Search<br />Primary Search<br />Config, Services databases DB 1<br />Config, Services databases DB 2<br />Content Log Shipping<br />
  36. 36. Disaster Recovery (2)<br />
  37. 37. Q & A<br />