SharePoint Sitehttp://www.sharepointconference.co.nz search

Browse PageSite Actions username

Parent > Parent > Current PagePage Title

This Site: site search

LibrariesSite PagesShared DocumentsDrop Off LibraryCustom library

Current PagePage One Page Two

Practical SharePoint 2010 Architecture PlanningChakkaradeep (Chaks) Chandran

Consultant, Microsoft Consulting Serviceschaksc@microsoft.comMicrosoft New Zealand

@chakkaradeep

www.chakkaradeep.com

Session Agenda

• What we will cover– Server Architecture– Server Topologies– Performance and Capacity Planning– Software Boundaries and Limits – QUIZ!– Search Topology

• No Demos

• What we will not cover– Information Architecture Planning– Backup and Recovery Plans– High Availability– Disaster Recovery– Search Planning

Audience Poll

• SharePoint Administrators ?• SharePoint Developers ?• SharePoint End Users ?• IT Administrators ?

Overall Design Goals

• Use minimum number of server farms

• Build a topology that suits our requirements

• Build a topology that caters for performance, maintainability, reliability etc.,

• Creating a framework that can scale out

Architecture Components

Web Front End Servers Application

Servers

Database Servers

Service Applications SharePoint

Services

Disaster Recovery

High Availability

29/03/2012 1:30 p.m. - 2:30 p.m. SharePoint 2010 – Planning High Availability for SharePoint 2010 Farms 29/03/2012 2:45 p.m. - 3:45 p.m.A Closer Look at SQL and SharePoint: Tips and tricks from the field

Where do we start?

• Gather Requirements• Requirements drive everything we do• What we are really doing“Build and deploy a solution that satisfies the business and IT requirements”

Service Applications

Application Tier design decisions will be based on Service Applications

• Access Services• Business Data Connectivity service• Excel Services Application• Managed Metadata service• PerformancePoint Service Application• Search Service Application• Secure Store Service• State service• Usage and Health Data Collection service• User Profile service• Visio Graphics Service• Web Analytics service• Word Automation Services• Microsoft SharePoint Foundation Subscription Settings Service

Real World Example

“I want my company Intranet powered by SharePoint. I see my teams are struggling to work together. I heard SharePoint can solve that problem too.”

Different Workloads

Intranet

Team Collaboration Sites

Project Team Sites

Document Management System

Workflows Search

Excel Services

Access Services

User ProfilesMy Sites

Service Applications

Application Tier design decisions will be based on Service Applications

• Access Services• Business Data Connectivity service• Excel Services Application• Managed Metadata service• PerformancePoint Service Application• Search Service Application• Secure Store Service• State service• Usage and Health Data Collection service• User Profile service• Visio Graphics Service• Web Analytics service• Word Automation Services• Microsoft SharePoint Foundation Subscription Settings Service

SharePoint Topology Options

Single Server with SQL Server• “All In One” Box• All Roles on one server

– SQL Server– Web Front End– Application Server

• Easy to deploy• Best suited for developer environments or pilot• What's wrong?

– Installs SQL Express– No High Availability– Heavy resource usage– Single point of failure (SPOF) “All In One” Box

SharePoint Topology Options

Multiple Servers – Option 1• Dedicated SQL Server• All SharePoint Roles on one Server

– Web Front End– Application Server

• Good option to start• What’s wrong:

– No High Availability– We still have SPOF– Heavy resource usage

• SharePoint 2010 Server– No redundancy Database Mirroring Failover Clustering

(AND/OR)

Log Shipping

SharePoint Topology Options

Multiple Servers – Option 2• Dedicated SQL Server• Dedicated Web Front End Server• Dedicated Application Server• What’s wrong:

– No redundancy

Database Mirroring Failover Clustering

(AND/OR)

Log Shipping

SharePoint Topology Options

Multiple Servers – Option 2 Extended

/ WFE

Database Mirroring Failover Clustering

(AND/OR)

Log Shipping

Bit more on service applications...

Service Application Limiting Factor

Access Services • CPU on the App Server

Business Data Connectivity • CPU and memory on the WFE • CPU on the App Server that require

calls to Secure StoreExcel Services • CPU on the Excel Services tier (app

server)• CPU on the WFE

Workflow Performance- Key thing to note is Workflow Timer Service runs on WFEs

• Depends on Queue Settings:• Workflow Postpone Threshold • Workflow Event Delivery Batch

Size • Workflow Timer Job Frequency

• You can increase workflow throughput by scaling out to up to four WFEs.

More Info - http://technet.microsoft.com/en-us/library/ff608068.aspx

SharePoint Topology Options

Multiple Servers – Option 3

Database Mirroring Failover Clustering

(AND/OR)

NLB

Log Shipping

Software Boundaries and Limits

Limit Maximum Value

Content Database (x) per Web Application [500 – 300 – 100]

Site collection (x) per Web application [50,000 – 150,000 – 250,000]

Site collections per content database (x) recommended5000 Maximum[3000 – 1500 – 2000]

Application Pools (x) per Web Server[5 – 10 – 3]

Content Database (general scenarios) (x in GB/TB) per content database[100GB – 200GB – 1TB]

Content Database (document archive scenario) (x in GB/TB) per content database[500GB – 4TB – 3TB]

QUIZ TIME!

More Info - http://technet.microsoft.com/en-us/library/cc262787.aspx

What about Disaster Recovery?

Key Metrics• Recovery Time Objective (RTO)

– The maximum time a data recovery process will take• Recovery Point Objective (RPO)

– The maximum amount of time between the last available backup and any potential failure point.

• Service Level Agreements (SLA)

Business Continuity Planning - http://technet.microsoft.com/en-us/library/cc287972.aspx

An Update From The Business Team

• We have 10 departments• Documents around 10GB per department• This will grow 2% to 3% every year• Search is very critical• We have HR department who want immediate search results

Search Architecture Example

INDEX PARTITION

Query Component 1 Query Component 1m

Search Admin Crawler

Crawl Db

Crawler

Crawl Db

RAM RAM

RAM Use dedicated server instead

Enterprise Search Planning - http://technet.microsoft.com/en-us/library/cc263400.aspx

Disk Space Disk Space

Scaling out Search Architecture

• Add Query Components– To increase query throughput– To add failover query components to support redundancy

• Add Index Partitions– To support larger number of items

• Add Property Databases– To eliminate bottlenecks– To support more metadata to index

• Add Crawl Components– To increase crawl throughput– To add failover crawl components

Software Boundaries and Limits

Limit Maximum Value

SharePoint search service applications (x) per farm[20 – 30 – 10]

Crawl databases (x) crawl databases per search service application[30 – 10 – 15]

Crawl components (x) per search service application[14 – 15 – 16]

Query components (x) per search application64 total crawl components per server[65 – 128 – 120]

Index partitions (x) per search service application128 in total[22 – 20 – 64]

Property databases (x) per search service application128 in total[12 – 10 – 14]

QUIZ TIME!

More Info - http://technet.microsoft.com/en-us/library/cc262787.aspx

Real World Example

“I want my company Intranet powered by SharePoint. I see my teams are struggling to work together. I heard SharePoint can solve that problem too.”

TEAM SITES

Keep teams in sync and manage important

projects

INTRANET SITES

Keep everyone up to date with company

news and information

MY SITES

Share and manage personal documents

and information

Thank You | www.chakkaradeep.com

SharePoint 2010 Architecture Example

INDEX PARTITION

Query Component 1 Query Component 1m

Search Admin Crawler

Crawl Db

Crawler

Crawl Db

RAM RAM

RAM Use dedicated server instead

Enterprise Search Planning - http://technet.microsoft.com/en-us/library/cc263400.aspx

Disk Space Disk Space

Bronze Sponsors Media SponsorsTechnology

Sponsor

Gold Sponsors

Silver Sponsors