1. Sharepoint 2010 Architecture, HA & DR Tihomir Ignatov Sr. Consultant Microsoft Corporation Blog: http://tihomirignatov.blogspot.com

2. Agenda What is Sharepoint? Application Architecture Services Architecture Web Server Components Best Practices vs Real World Limits & Boundaries Scalability & High Availability Deployment Topologies Search Architecture Disaster Recovery

3. What is Sharepoint? http://en.wikipedia.org/wiki/Microsoft_SharePoint 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 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.

4. What is Sharepoint? (2) 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. 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).

5. Architecture in Sharepoint Deployments Deployment Architecture Network Architecture Enterprise architecture Server architecture Permission architecture Cloud architecture Infrastructure architecture Deployment Architecture Software Architecture Data architecture Information architecture Business architecture

6. To build application that satisfies the business and IT requirements Choosing appropriate technical solution based on the requirement and the maturity of the team involved Sharepoint Architecture – What is it for?

7. Architecture is Making ideas real “Make everything as simple as possible, but not simpler.” -Albert Einstein

8. Sharepoint Architecture

11. Or http://pmo

12. Separate Content DB, Security, Navigation

13. Separate “Limits and Boundaries”

15. Maintenance

17. Components IIS Services GAC Hive 14

18. Always use best practices (BP) when is possible Adapt your design to the business requirements Do not hesitate to jump over the BP if is reasonable, but leave a track why (document it) Always weigh out the business requirements against feature TCO (complexity, time, resources, price, etc.) Say “NO” to your client, when the feature is expensive and low business impact Best Practices vs. Real World

19. Supportability Use only SUPPORTED scenarios for customization and configuration Do not use Quick & Dirty approach for production What is supported? Ask for supportability!

20. Boundaries are absolute limits that cannot be exceeded by design. Thresholds are those that have a default value that cannot be exceeded unless the value is modified. Supported limits define the tested value for a given parameter. Limits Thresholds and supported limits guidelines are determined by performance.

21. Some Important Limits Software boundaries and limits at TechNet

22. Capacity is directly affected by scalability If your solution plans exceed the recommended guidelines Evaluate the solution to ensure that compensations are made in other areas. Flag these areas for testing and monitoring as you build your deployment. Redesign or partition the solution to ensure that you do not exceed capacity guidelines. Take Into Account…

23. How to design the solution (Sub Sites vs. Site Collections vs. Web Applications) Which SA to provision Do not use the Farm Configuration Wizard Important Decisions

24. “Some” resources in Technet… Consider the limits! Storage and SQL capacity planning For content databases For Service Applications Always test storage performance with SQLIO tool Schedule meetings with storage administrators  Capacity Planning My capacity planning tool: http://tihomirignatov.blogspot.com/2010/12/sharepoint-2010-capacity-planning-and.html

25. Browser and version MS Office version Client PCs – HW & SW configuration, load, other applications Monitor and test page rendering performance on regular PC (not development) Client Compatibilities

26. Scale up or scale out? When to scale? What to scale? Scalability

27. Is the Sharepoint a business critical application? Try to define SLA and down time – cost, operations, reliability From scalability and capacity to availability Database availability strategies – clustering or mirroring? Service Applications redundancy strategies SA that store data outside a database SA that store data in databases Search Service Application redundancy High Availability

28. Sharepoint Farm Topologies Limited Deployments

29. Sharepoint Farm Topologies Small Farm Topologies

30. Sharepoint Farm Topologies Medium Farm Topologies

31. Sharepoint Farm Topologies Large Farm Topologies

32. Search Physical & Logical Components Web Application / Search Proxy Query Processor WFE Query Component Index Partition Crawl Component Application Server Search Admin Component Single Box Property DB Crawl DB Search Admin DB SQL Server DB

33. How the Search works? Web Application / Search Proxy User Query Query Results Query Processor Property DB Query Component Index Partition Crawl DB Crawl Component Search Admin DB Search Admin Component Crawl defined by Administrator

34. Real World Example

35. Disaster Recovery D/R Search Primary Search Config, Services databases DB 1 Config, Services databases DB 2 Content Log Shipping

36. Disaster Recovery (2)

37. Q & A