© 2009 Quest Software, Inc. ALL RIGHTS RESERVED

Getting SharePoint 2010 Deployment Right

Mike Watson

Sr. Product Manager

Quest Software – SharePoint

www.sharepointmadscientist.com

www.sharepointforall.com

www.twitter.com/mikewat

2

Agenda• Understanding the Unknown• Preparing for the Unknown• Summary• Q&A

3

About Mike• Product Manager at Quest

– Web Parts– Deployment Advisor– Focus on availability, scalability, and manageability of

SharePoint

• Previously at Microsoft – BPOS (Dedicated and helped design Standard)– Worked on SharePoint guidance as

• SharePoint CAT virtual team member• Center of Excellence

– Helped teach the MCM

• U.S. Army– Computers, Finance, Accounting, and Armor (M1A2)

4

Problems in SharePoint 2007

Managing & Monitoring Change GovernanceManaging Systems

Storage Usage & Growth

Tracking & improving performance

Lack of insight

Lack of knowledgePatching

Managing CapacitySecurity

Cross-farm management

Customization Maintenance

Guaranteeing Availability

5

Problems in SharePoint 2010

Managing & Monitoring Change GovernanceManaging Systems

Storage Usage & Growth

Tracking & improving performance

Lack of insight

Lack of knowledgePatching

Managing CapacitySecurity

Cross-farm management

Customization Maintenance

Guaranteeing Availability

6

Complexity

Concurrency

Expectations

AccountabilityOMG!

7

What’s Going On?• Complexity

– New capabilities and terminology– Changes to familiar services– Brand new services

• Additional databases (was 7: now 19)

• Concurrency– Clients more connected– Ajax polling– Offline

• Expectation– Users are more sophisticated

• Accountability– More ways than ever to catch you

8

The SharePoint 2010 Administration Paradigm

Inexperienced system

managers

Implement new

technology

For new users

Leading to unfamiliar problems

Handled by

9

It’s Getting Harder!

10

Prepare Yourself

11

Prepare Yourself and Your Team• Setup an evaluation environment

– Install and play with SP2010• http://sharepoint2010.microsoft.com/try-it/Pages/Trial.aspx

– Install and play with Office 2010• http://technet.microsoft.com/en-us/evalcenter/ee390818.aspx

• Learn Learn Learn!– http://

blogs.msdn.com/arpans/archive/2009/12/02/sharepoint-2010-training.aspx

• Practice your upgrade

12

Prepare Your Environment

13

Hardware Requirements (2007)Web App SQL

Processor

Minimum 2.5Ghz 2.5Ghz 1.4Ghz

Recommended >3Ghz Dual >2.5Ghz Dual >2.0Ghz

Best Practice 3.0 Ghz Quad 3.0Ghz Quad Dual 2.0 Quad

Memory

Minimum 2GB 2GB 512MB

Recommended >2GB 4GB >2GB

Best Practice 8GB 16GB 32GB

14

Hardware Requirements (2010)Web App SQL

Processor

Minimum Quad 2.5ghz Quad 2.5ghz Quad 2.5ghz

Recommended ? ? ?

Best Practice ? ? ?

Memory

Minimum 4GB 4GB 4GB

Recommended 8GB 8GB 8GB

Best Practice ? ? ?

Source: http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx

15

Four to Six Servers Min for HA, Sanity, & Performance

• Why?• Optimizes performance of web servers• Increases redundancy and reduces points of failure

• Redundancy across serserver roles

• Allows most flexibility & role isolation

Web Server +Query Server

Application Server

Clustered SQLServer

16

KISS Principle

Mo Servers = Mo ProblemsMo Problems = Mo Money

17

SharePoint & Virtualization• Virtual is never as good as physical (sharing)• Some virtualization features don’t work well

– E.g. Resource pool allocation aka overcommit

• Virtualization introduces some artificial limitations to scaling up– Processor limitations per machine– Ability to leverage memory– Sharing across bottlenecks (hw bus, NIC)

• Some roles work better with virtualization than others…

18

Virtualization is Great But be Careful

OK

• Web – Processor, Memory

• Query – Disk constraints

Maybe

• Excel – Processor, Memory

Maybe Not

• Index – Processor, Disk constraints, memory

• SQL – Processor, Disk constraints, memory

19

VM’s Need Hardware Too!Web App SQL

Processor

Minimum Quad 2.5ghz Quad 2.5ghz Quad 2.5ghz

Recommended ? ? ?

Best Practice ? ? ?

Memory

Minimum 4GB 4GB 4GB

Recommended 8GB 8GB 8GB

Best Practice ? ? ?

Source: http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx

20

Balance Front-end & Back-end Capacity

21

SQL Health = SharePoint Health!

Sub-optimal SQL performance will radiate to other components in the farm

Slow SQL

Slow App

Database Performance is Paramount!

22

Configure SQL to conform w/ best practices• Configure Memory

– Min & Max values = Total memory – 2GB for OS overhead• Configure Temp DB

– Allocate ¼, ½, or 1 data file per processor core• Pregrow databases & never autogrow• Align partitions

– 64KB or 256KB• Use 64KB or larger multiple for RAID stripe size• Dedicate storage for SQL• Separate storage for different workloads• Use RAID 10

23

Pregrow Databases and Never Autogrow

Calculate total size

in 6months

Create 5 to 10

databases

Pregrow those DB’s.

Distribute across disks

24

Think Disk IO! Not Disk Capacity!

Spindle Count

X Spindle IOPS

= Total IOPS capability

25

Calculating Disk IO – An Example

10 spindles

X 200 IOPS per spindle

= 2000 IOPS

26

Temp

8KB Random

writes

1:1 read/write

Logs

8KB sequential

writes

1:1 read/write

Search

64KB Random

reads/writes

5:1 read/write

Data

64KB random reads

5:1 read/write

Temp Logs Search Data

Allocate as many disks as needed to SQL

27

Best Practices – SQL Disk IO

Allocate separate and dedicated disks with the following specifications:

* Raid 1 or variants (0+1, 1+0)

** Depends on type and amount of content being indexed

*** 2000 IOPS minimum. Plan on 1500 IOPS per simultaneous crawl. (e.g. 3 crawls = 4500 IOPS)

**** Use Raid 5 when redundancy needs are met with replication

Workload Size Raid Type IOPS

TempDB 300GB or 10% Raid 1* 800 or 2 IOPS/GB

Logs 25% of data storage

Raid 1* 2 IOPS/GB

Search ** Raid 1* 2000 IOPS ***

Data 110% of stored blobs

Raid 1* or 5**** .75 to 1 IOPS/GB

28

Use RAID 10Good• Better redundancy• Faster less impacting

rebuilds• 2X write performance• Optimized for IO

Bad• Expensive• Lower’s your capacity

29

Problems in SharePoint

Managing & Monitoring Change GovernanceManaging Systems

Storage Usage & Growth

Tracking & improving performance

Lack of insight

Lack of knowledgePatching

Managing CapacitySecurity

Cross-farm management

Customization Maintenance

Guaranteeing Availability

30

Deployment Advisor for SharePoint

31

What is Deployment Advisor?

A tool created specifically to instill confidence in SharePoint, its

administrators, their managers, and ultimately end users.

32

What is Deployment Advisor Currently?

Identify & resolve• Performance

bottlenecks• Security

vulnerabilities• Service outages• Support issues

Recommend and compare • SharePoint & SQL

configurations• Hardware• Windows, IIS,

ASP .NET settings

Track & manage• Change• Utilization• Storage growth• Customization• Site proliferation

Report on• Topology• Storage allocation• Health• Upgrade

readiness• Inconsistencies

33

Usage Scenarios• Discover layouts folder customizations• Compare web.config files across web applications

and servers• Compare service settings across farms• Determine upgrade readiness across farms• Assess health of services, servers, databases, and

farms• Discover best practice and capacity boundary

violations• Export and print anything you see – overviews,

summaries, risks.

34

Where is Deployment Advisor Going?

Identify & resolve• Performance

bottlenecks• Security

vulnerabilities• Service outages• Support issues

Recommend and compare • SharePoint & SQL

configurations• Hardware• Windows, IIS,

ASP .NET settings

Track & manage• Change• Utilization• Storage growth• Customization• Site proliferation

Report on• Usage • Changes• Uptime

35

Benefits of Deployment Advisor

Administrators

• Increase uptime

• Reduce failures

• Improve Visibility

Managers

• Report health & availability trends

• Track & manage change

Consultants

• Engage customers

• Market knowledge

• Find work

36

Features

Community driven, ever-growing set of built-in rules & best practices

An easy to deploy, easy to use console built specifically for SharePoint

Manage any number of servers and farms including non-SharePoint servers

Supports WSS 3.0 & 4.0, MOSS 2007, SharePoint Server 2010

No server needed. Runs on XP

Supports Windows 2000 & SQL 2000 and above

37

Extensible, Open, Community-Driven

Benefit• Ships with hundreds

of community approved rules and best practices

• Ignore & Modify rules

Extend• Import best practices

from Subject Matter Experts and the community

• Create your own rules using Powershell & C#

Contribute• Rate and rank

community contributions

• Create/upload rules and solicit feedback

38

How Deployment Advisor Works

• Install components on any XP or above workstation

Install

• Select any SharePoint server

• Agent pushes small webservice to server

Connect • Web service collects info about farm and stores in remote DB

• Data is loaded into console and analyzed real-time against configured rules and best practices

View

39

Summary• 2010 is infinitely better than 2007• Higher level problems still exist just as they did in 2007• Our jobs as Administrators are getting harder due to:

– Complexity– Concurrence– Expectations– Accountability

• Prepare for the unknown by:– Learning as much as you can– Practicing– Excess hardware capacity (physical and virtual)– Deploy SQL right– Allocate proper storage

40

Technology Responsibilities

40

Toughest Challenges

1. User Provisioning/de-provisioning

2. Delegation of Admin Rights

3. Compliance Reporting

4. Disaster Recovery

Active Directory44%

DNS26%

MIIS/ILM16%

Ex-chang

e15%

Multiple Technology Respon-sibilities

Technology Used / Deployed

• 99% MS Server OS• 90% Management Frameworks

• 55% - MOM • 27% - HP OpenView• 21% - IBM Tivoli

• 87% Exchange • 74% SharePoint

Source: DEC 2008 Attendee Survey Whitepaper

41

Q&A