Best Practices to SharePoint Physical and Information Architecture

Best Practices: SharePoint Physical and Information Architecture Fundamentals

Name: Joel OlesonTitle: Sr. ArchitectCompany: Quest Software

Who is SharePoint Joel?

8 year SharePoint Veteran…First SharePoint Admin!Sr. Technical Product Manager - SharePoint team Launch of SharePoint Server 2007Top IT SharePoint Blog

Blog: http://www.sharepointjoel.comTwitter: @joeloleson

http://www.sharepointjoel.com/

Audience PollSharePoint Admins?Less than 3 years in SharePoint?Belong to SharePoint &/or .NET user groups?

Microsoft Confidential

Agenda…SharePoint Best Practices: Architecture Fundamentals

Core Logical ArchitecturePhysical ArchitectureDesigning Information ArchitectureAvoid Common Mistakes


WSS 3.0 and SharePoint Server 2007

SharePoint Server 2007 Enterprise

SharePoint Server 2007

Standard

Windows SharePoint Services 3.0

Platform & Collaboration(blogs & wikis)

Doc Management, Web Content Management,

Search, & Portals

Web Forms, Excel Services,

BDC

MOSS FISFor Internet Sites

& Enterprise Intranet

Windows Internet

Connector

Intranet/ExtranetStandard

Fundamental Principle #1

IIS WSS 2.0 / SPS 2003 WSS 3.0 / SharePoint Server

Web Sites Virtual Servers Web Applications

IIS Web Sites = IIS Virtual Servers = Web Applications

Physical Server

Web Application(s)

Top Level Site(s)

Site Collections

Site(s)

Site Collection


Fundamental Principle #2Consistency in Hierarchy

WSS 3.0Web ApplicationsSite CollectionsSitesTemplates & Features

MOSS 2007Web ApplicationsSite CollectionsSitesTemplates & Features


Fundamental Principle #2Servers Have Services are Are Roles

Servers have RolesWeb Front End (WFE)QueryCalculation (Excel)Index(Non SharePoint) Database Server

Simplified Really Just 3 RolesWFE/Query – 99%Index (App Tier)SQL

Note: Never put Query and Index on same server if there is another Query server!


Deployment InstallKey concepts

32 bit or 64bit binaries**Note: SharePoint 2010 requires 2008 64bit & 64bit SQL 2005 or 2008

InstallBasic NOT RECOMMENDED except for POCAdvanced – Allows you to connect to SQL

WFE only vs. Full installLanguage Packs (Downloads on the Web)

WSSMOSS

Ifilter packs


Most Common Farms

WFE/Query

“All in One”

WFE/Query

Index

SQL SQL

All SP Roles

SQL

User requests

Load balances webfront end servers

Applicationservers

2 Clustered SQL server

Index Query Query Calc +

10 Server Farm (Large)

User requests

Web front ends + application(s)

Application(s)

Clustered SQL server

5 Server Farm (Medium)

3 Server Farm (Small)User requests

Each load-balanced server includes:

• Web front end• Applications

Dedicated SQL server

Single Server

• Web front end • Application • Database

One Server which contains:

User Requests

Picking Your Topology

Availability

Perf

orm

ance


Key Factors in TopologyUsage

# UsersSolution (The answer before the question)

Authentication Type (Anonymous vs. AD)Caching Offload devices

Business & Tech RequirementsClient & Server Performance RequirementsSLAs (Uptime/High Availability Req.)WAN Considerations (Multi farm)

DataGBs/TBs of data Total # Files and Items (rare)

SharePoint in common…LOLCATS.COM


Fundamental Principle #3You MUST learn the difference between site and site

collection despite the confusion.

Site = Web = Spweb aka subwebSTSADM = WebUI=site

Site Collection = SpSiteSTSADM = SiteCentral Admin = SiteUI= Site Collection

•Basic Install (BAD!)•All On C Drive•No Backup•Restore Complexity

Server•All One site collection•Not Configured: Quota, Expiration, Auditing, Versions, Workflows, Meta Data capture•All items view default (flat)

List and Site Collection

•One database•Db config (log and db location)•No maintenance plan

Database

Defaults have Faults


POP QUIZ!!!! What is the most scalable object in SharePoint?

Site Collection

Can I run WFE and Query on one box and WFE Query Index on another?

NO!

Is a default basic install good enough to get started?

No!

Is Virtualization and SharePoint ok?

Yes!


WooHoo! You Pass SharePoint

Fundamentals– The New World

Containment Hierarchy

Joel's Cheat Sheet for HostingDedicated

Farm(s)•Ideal for applications such as Project Server, Performance Point, BDC applications, CRM, Sales SAP/Siebel and Finance Solutions built on SharePoint•Great for staged deployments i.e. dev, test, authoring to production

Web App •Ideal for point solutions, Records Management, for Legal Holds, department solutions, and groups of site collections•Memory isolation and separate SSP such as Search Solutions

Site Collection •Support 100s-100K+ sites•Ideal for Collaborative environments including intranets, Projects, extranets•Document Management where scale is into +TBs

Sites •Information and aggregation Portals such as Intranets•WCM Internet sites with page libraries

SharePoint Server Logical Model

Permanent Central PortalWeb Application

Division Portals

Groups & Teams

Projects & Workspaces

My Sites

PermanentStructured SharePoint Server Sites

SharePoint ServerSites

Ad HocWSS SiteTemplates

Permanent Division PortalsWeb Applications or Site Collections

Semi StructuredConsolidation on 1 to 3Web Applications

1 Web App perRegion

CentralPortal

ServiceOffering

Planning for *REAL* Capacity BoundariesUnit TechNet Max Joel’s Guideline Joel’s MAX

Web Apps per Farm 8 5 Content Webapps with 8GB RAM

16 app pools100 web apps w/ 32GB RAM, 64 bit

Databases per WebApp

- 100 per SQL server 300 with 32GB RAM, 64 bit

Site Collection per Web App

50,000 100,0000 -

Size per content database

- 100GB 1 TB with serious list and site optimization (advanced only)

Size per Site Collection - 15GB in multi-tenant DB100GB in dedicated DB

25GB in multi1TB in dedicated Db

Sites in Site 2000 100 500

Items per List 2000 items per view

Use Custom Views and search UI for large lists

It’s pain tolerance


Plan for Software BoundariesPlan your lists and libraries

Throughput differences between flat document library vs. document library with folders

#8 SharePoint Common Mistakes

Operations and IT Failures

•Poor configuration (Not planned - defaults)•Insufficient RAM and Disk allocationServer•Poor choice of Site vs. Site Collection Structure•Flat Lists•One Content Database

Information Architecture

•Poor Network between WFEs and SQL•No plan for WAN (User complaints without answers)Network•No Backup•Emergency: No Restore plan or steps•Disaster Recovery – More like Disaster

OperationalBackup/Restore


Call to Action!Be sure to PLAN your logical infrastructure & Physical… Don’t forget a Governance Plan!

Where do you get your information? TechNet, MSDN, SharePoint Team Blog, SharePoint User Groups http://www.sharepointpros.org, and blogs!! Twitter?

http://www.sharepointjoel.com@joeloleson

http://www.sharepointpros.org/

http://www.sharepointjoel.com/

33

Quest IT Solutions for SharePoint Site Administrator for SharePoint Discover, understand and manage your SharePoint environment

Migration Manager for SharePoint SharePoint 2003 to 2007 migration

File Migrator for SharePoint File shares to SharePoint migration

Recovery Manager for SharePointGranular SharePoint recovery for enterprise-level needs

Quest Web Parts Enable rapid development of SharePoint applications

Public Folder Migrator for SharePointExchange Public Folders to SharePoint migrationNotes Migrator for SharePointNotes application content to SharePoint migration

Quest SQL Server Solutions Maximize SQL Server performance while simplifying tasks and providing visibility and control

For IT Pros:70-631 - Windows SharePoint Services 3.0 - Configuring70-630 - Office SharePoint Server 2007 - Configuring

For Developers:70-541 - Microsoft Windows SharePoint Services 3.0 - Application Development70-542 - Microsoft Office SharePoint Server 2007 - Application Development

MCM and MCA!

SharePoint Exams!Get Certified on the New Exams!!!

http://www.microsoft.com/learning/exams/70-631.mspx




Q&AQuestions?

Best Practices to SharePoint Physical and Information Architecture

Technology

Transcript of Best Practices to SharePoint Physical and Information Architecture