Sharepoint 2010 architecture, ha and dr (tig)
-
Upload
tihomir-ignatov -
Category
Technology
-
view
3.535 -
download
0
description
Transcript of Sharepoint 2010 architecture, ha and dr (tig)
SHAREPOINT 2010 ARCHITECTURE, HA & DRTihomir Ignatov
Sr. Consultant
Microsoft Corporation
Blog: http://tihomirignatov.blogspot.com
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
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 management systems
• 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.
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).
Architecture in Sharepoint Deployments
Software ArchitectureDeployment Architecture
Network ArchitectureDeployment Architecture
Enterprise architectureServer architecture
Information architectureData architecture
Business architecture
Permission architectureCloud architecture
Infrastructure architecture
• 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?
Architecture is Making ideas real
“Make everything as simple as possible, but not simpler.”
-Albert Einstein
Sharepoint Architecture
Application Architecture
http://itweb
• IIS web site• Separate web.config
• http://itweb/sites/pmo• Or http://pmo• Separate Content DB,
Security, Navigation• Separate “Limits and
Boundaries”• Separate Customizations
Scope
• Content DB size• Maintenance• Backup & Recovery
Web Tier
Data Tier
Web application
Site Collection
Services Architecture
http://itweb http://hrweb
Search
BCS
WASUser
ProfilesExcel Calc
3rd party Service
Components• IIS• Services• GAC• Hive 14
• 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
Supportability
• Use only SUPPORTED scenarios for customization and configuration
• Do not use Quick & Dirty approach for production• What is supported?• Ask for supportability!
• 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.
Some Important LimitsLimit Max value Limit type
Zone 5 per web application Boundary
Application pools 10 per web server Supported
Content database size 200 GB per Content DB Supported
Site Collections number 500,000 per Web Application Supported
Site Collection Size 100 GB per Site Collection Supported
Web site 250,000 per Site Collection Supported
List view threshold 5,000/20,000 Threshold
List row size 8,000 bytes per row Boundary
File size 2 GB Boundary
Documents / Items 30 M per library / list Supported
Bulk operations 100 items per bulk operation (UI) Boundary
AD Principles/Users in a SharePoint group
5,000 per SharePoint group Supported
Web parts 25 per page ThresholdSoftware boundaries and limits at TechNet
• 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…
• 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
• “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
• 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
• Scale up or scale out?• When to scale?• What to scale?
Scalability
• 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
Sharepoint Farm TopologiesLimited Deployments
Sharepoint Farm TopologiesSmall Farm Topologies
Sharepoint Farm TopologiesMedium Farm Topologies
Sharepoint Farm TopologiesLarge Farm Topologies
Search Physical & Logical ComponentsWeb Application /
Search Proxy
Query Processor
Query ComponentIndex Partition
Crawl Component
Search Admin Component
Property DB
Crawl DB
Search Admin DB
WFE
Application Server
SQL Server DB
Single Box
How the Search works?
Property DB
Crawl DB
Search Admin DB
Web Application /Search Proxy
Query Processor
Query ComponentIndex Partition
Crawl Component
Search Admin Component
Crawl defined by Administrator
User Query Query Results
Real World Example
Admin
Search Admin db
Property db
Crawl db
Crawler
Web serverQuery server
Web serverCrawl server
Index partition 1
Query serverCrawl server
All other SharePoint databases
Query component 1 Query component 1m
Crawler
Disaster Recovery
Config, Services database
s DB 1
Config, Services database
s DB 2
Content Log
Shipping
Primary
Search
D/RSearch
Disaster Recovery (2)
Q & A