wss moss planning and deployment best practices

8/8/2019 WSS MOSS Planning and Deployment Best Practices

1/42

Windows SharePointWindows SharePoint

Services And OfficeServices And OfficeSharePoint ServerSharePoint ServerPlanning and Deployment BestPlanning and Deployment BestPracticesPractices

Kuldip Obhan

ConsultantMicrosoft Canada


2/42

Where to Start?Where to Start?

Review and Correct Your EnvironmentGather and review requirements

Review product features and map torequirements

Determine constraintsPlan your new architecture

Establish Teams and determine trainingrequirements*

Establish a definition for your service(scope & approach)*Governance Plan*

Get buy-in from all resources*


3/42

Review and Correct YourReview and Correct YourEnvironmentEnvironment

Get counts and amountsReview language pack requirements

Consider replacing hardware if any risksfrom end of warranty or lifeSite lifecycle cleanupSplit databases that are very large

Move sites out of content databasesLevel set patches and service packs


4/42

Review Product FeaturesReview Product Features

and Map to Requirementsand Map to Requirements

Determine security requirements

Determine what features youll enable

Review storage planning considering recycle bin

Review data connectivity plans

Determine RSS consumption requirements

Block or enable SharePoint Designer

Self-service creation or IT provisioningMinimum quota limit

Incoming and outgoing e-mail

Discussion groups


5/42

Determine ConstraintsDetermine Constraints

What is your hardware design?How much storage is available, can you grow?

What authentication methods will you use?

What percentage of traffic is authoring vs. read?

What percentage of traffic is collaboration?How does content need to be constrained?

Is the mobile user a key scenario?

When and how long does backup run?


6/42

Plan Your New ArchitecturePlan Your New Architecture

Do you need to use the same hardware?How much do you need to index?How many properties do you have?What is your backup strategy?

Will you be allowing self-service creation orcharging for the service?What is the average user latency?How much data can we store?

How many users can our environmentsupport?How many sites can we run on our servers?


7/42Microsoft Confidential

Site Objects

Site Collections, Web sites, documents, documentlibraries, list items, document file size, etc.

People Objects

User profiles, security principals, etc.

Search Objects

Search indexes, Indexed documents

Logical Architecture ObjectsShared Services Providers, Site Collections,Content Databases, Zones, etc.

Physical Objects

Servers: Index, WFE, Database, Application, etc.



Software scalability

Recommendations for acceptable performancebased on software behavior and characteristics

Hardware scalability

Does not change/modify software behavior orcharacteristicsbut can increase overallthroughput of a server farm and might be

necessary to achieve acceptable performanceas the number of objects approachrecommended limits



Determine Usage ProfileUsage profile == User communitys behavior

Distribution of requests across content

Operation types and frequency

Estimating Throughput TargetsUser response time, concurrency

Throughput target rule of thumb: 1 RPS == 100concurrent users. * Note, this is consistent with SPS 2003, WSS 2.0



Object RecommendedMaximum

Scope ObjectCategory

ContentDatabases

100 per Web applicationWebapplication

Logicalarchitecture

Site

Collections

50,000 per Content

Database

Content

Database

Logical

architecture

Web Sites 250,000 per SiteCollection

Site collection Site object

Documents 5 million per library(2,000 per nestedfolder/view)

Library Site object

IndexedDocuments/Items

50 million per queryserver (across ALLindexes/SSPs)

Farm Search object

Web Serversto DatabaseServer Ratio

8 Web servers perdatabase server

Farm Physical object



Throughput vs. Number of Site Collectionsin One Content Database



Throughput differences between flat documentlibrary vs. document library with folders



Throughput vs. number of Webservers

Test findings showed plateau at 5:1 (your mileagemay vary)

Perform tests in your environment

Other RecommendationsCarefully plan your site hierarchy and design

Minimize # Web applications and applicationpools

Limit # of Shared Service Providers

Plan for database growth

Follow data and feature best practices andsuggested limits



Other configuration factors that caninfluence throughput targets

Indexing (schedule indexing window off-hours)

Caching enabled?Output Caching and Cache Profiles

Object Caching

Disk-based Caching for Binary Large Objects

Page customizationsCustom Web parts



Latency componentsServer processing

SQL processing, # SQL round trips, AJAX processing, security trimming

Client processing

Javascript, CSS, AJAX requests, HTML load, Client machine specs

Wire transfer

Bandwidth, size of download

RecommendationsPrimary cause of latency problems: custom web parts

Watch for: SQL round trips, unnecessary data, excessive client sidescript

Re-use existing client code versus adding more

Design code for performance (Use HTML and .Net best practices)

Profile your solutions


16/42

Designed to grow with organization needsTopology restrictions removed

Redundant WFE, Query and DB roles

Server resources: x32, x64, CPU, RAM, HDDRecommend 64-bit for back end services (SQL) whichcan leverage additional addressable memory

32-bit can directly address only a 4GB Memory Address

Space64-bit supports up to 1,024 GB Memory (Physicaland/or Addressable)

64-bit Prioritization: SQL Index Excel SearchWFE*64-bit hardware can be mixed within a farm, but not within server role level (ie WFEs, etc)

Plan Hardware and StoragePlan Hardware and StorageHow SharePoint Scales and x32 vs. x64How SharePoint Scales and x32 vs. x64


17/42

Plan Hardware andPlan Hardware andStorageStorageMulti-Server Farm ExampleMulti-Server Farm Example

Optimizes performance of web servers

Increases redundancy and reduces points of failure

Redundancy at WFE and Database server roles

Determine configuration based on your business needs and goals

Determine config of other Application roles (Excel Services, Index, Forms,etc)

Web Servers ApplicationServer

ClusteredSQL

Server


18/42

Plan Hardware andPlan Hardware andStorageStorageStorage ConsiderationsStorage ConsiderationsPrimary Metric: Document Storage

Plan for 1.2 1.5 x file system size for SQLServer

note: metric is closely tied to RAID level used on SQL disks

Secondary Metric: Index Size

Index Server: 30% of total size of all contentindexed for a single server

Query Server: 1 x index size


19/42

Development EnvironmentDevelopment Environment

Features


20/42

Solution DeploymentSolution DeploymentExtension of Web PartPackages

Support more solutionfile types

Feature definitions

Site definitions

Template Pages &Resources

Resources

Global, Binassemblies


21/42

Testing EnvironmentTesting Environment

Virtual EnvironmentMulti farm

Separate domain



Identical Software and Hardwareconfiguration

Identify issues earlier than production

No virtual servers

Content authoring and staging

Subset of actual users testingfunctionality

Content Deployment to PROD


23/42

Microsoft Confidential

Identical to Production environmentAcceptable failover/downtime time from production to disasterrecovery environment and vice versa?

How should users be switched from production to disasterrecovery URL?

Does the Disaster Recovery site need to be editable or read-only?How many hours/days of loss/out of sync data is acceptablebetween production and disaster recovery environment?

What are the performance and availability requirements for thedisaster recovery environment?

What incident(s) will be declared as disaster?

How much time do we want to wait till we make a decision onwhen to switch from prod to DR?


24/42

ContdContd

Backup and Restore methods2-Stage Recycle Bin for documents and lists

Site-level backup/restore via STSADM

Integrated backup/restore UI for web application and farm

VSS writer for farm backup

SQL Server backup/restore

Mirror/failover farm

Replicate primary farm on secondary system

SQL log shipping transfers content DB data

Must manually replicate configuration changes

On disaster, router switches traffic in minutes


25/42


ToolsVisual Studio Team System Test Edition (VSTT)

Fiddler

When?Initial deployments

New hardware configurations

Impact of scaling across or up

Validating custom solutions

Debugging performance related issues


26/42


Data for testing (Sites, Search terms, lists,documents etc)

A test farm with enough servers to mirror atopology you are testing for

A VSTT controller machine (2-4 GB RAM);preferably with SQL Server 2005 to store the testresults

VSTT clients machines; preferably physical; withat least 2GB of RAM to support many concurrent

connectionsCreate VSTT Test Project (Web and Load)


27/42


Setup your RigCreate your content (Data Load Tool orManually)

Create your tests (web, load)

Configure the test parameters

Run. Measure. Repeat.


28/42


SharePoint sends down a relativelylarge payload when you visit the site;even though it is improved from SPS2003

This payload comes from jScript files,IE Behaviors, and images, in additionto the text content

h i i l i


29/42

Model

*SCCP System Center Capacity Planner

What we ship

SharePoint Capacity PlanningSharePoint Capacity PlanningToolTool Solution OverviewSolution Overview

Built-in best practices

Visual Model Editor

What if analysis

Efficient deploymentplanning

Sh i C i l i


30/42

SharePoint Capacity PlanningSharePoint Capacity PlanningToolTool Solution ConceptSolution Concept


31/42

Planning deployment of WSS v3.0 installations only

Planning deployment of MOSS 2007 installations only

Plan deployment of MOSS for Search

Plan deployment of MOSS for intranet

Plan deployment of MOSS for internet

Plan deployment of MOSS for Enterprise ContentManagement (ECM)

Planning storage requirements for MOSSPlanning scalability and expansion of existingMOSS/WSS installations

SharePoint Capacity PlanningSharePoint Capacity PlanningToolTool In ScopeIn Scope


32/42

This solution accelerator will not cover any upgradescenarios for WSS or MOSS

This solution accelerator will not perform self-discovery ofalready existing MOSS/WSS installations

This solution accelerator will not cover deployment migrationfrom competitor products to MOSS/WSS

Note: The solution will NOT prevent customers and third partydevelopers from building tools on top of itself to cover any orall of the above scenarios


33/42


HTTP Compression is enabled andturned on by default for Static fileslike .js, .css etc

Aspx pages need to be added

Compression improves latency anddecreases payload size

Compression affects up to 15%

throughput


34/42

Implemented in MOSS as Site Collection

Output Cache

Control it at the site collection level

Exceptions allowed for layout pages and

subsites

Caching profiles determine cachecharacteristics

You can use different profiles for anonymousand authenticated users

Out of box includes four profiles that fit mostscenarios

MOSS Output CacheMOSS Output Cache


35/42

OutputOutput Cache ConsiderationsCache ConsiderationsWhat if I dont want the whole page to be

exactly the same every timePost-Cache Substitution controls, like login

Default caching behavior for

authenticated users is to cache forReader only

Check Allow writers to view cached contentin profile to change

Use the cache debug statements

Verify it is working first!


36/42

MOSS BLOB CachingMOSS BLOB CachingBlob Cache puts SharePoint items on disk

Also stamps a cacheability value on items inthe blob cache

Turned off by default; must edit web.configto change

Parameters:location: the directory where items are storedpath: a regex expression of the types of filesthat should be blob cachedmaxSize: the size in GB that the cache isallowed to usemax-age: the amount of time in seconds thatitems should be cached on the client

enabled: set to true to enable the blob cache


37/42

MOSS Object CacheMOSS Object Cache

Enabled by default

Used to store frequently accessed items

Site navigation structure

Field content of a library or list item

Content by Query web part data

Configured to use 100MB by default

Use Object Cache UI to flush ObjectCache as well as disk-based cache (whichreally means the blob cache)


38/42

Microsoft AdministrationMicrosoft AdministrationStandard tool supportStandard tool support

MOM packs for MOM 2005

Volume Shadowcopy Service (VSS)

Best Practices Analyzer (BPA)Microsoft update support


39/42

ResourcesResourcesWhite Paper: Working with Large Lists in Office SharePointServer 2007

http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409

White Paper: Performance Recommendations for StoragePlanning and Monitoringhttp://go.microsoft.com/fwlink/?LinkID=105623&clcid=0x409

Plan for Performance and Capacityhttp://technet2.microsoft.com/Office/en-us/library/8dd52916-f7

Determine Hardware and Software Requirements

http://technet2.microsoft.com/Office/en-us/library/4d88c402-24
http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409http://go.microsoft.com/fwlink/?LinkID=105623&clcid=0x409http://technet2.microsoft.com/Office/en-us/library/8dd52916-f77d-4444-b593-1f7d6f330e5f1033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/4d88c402-24f2-449b-86a6-6e7afcfec0cd1033.mspxhttp://technet2.microsoft.com/Office/en-us/library/4d88c402-24f2-449b-86a6-6e7afcfec0cd1033.mspxhttp://technet2.microsoft.com/Office/en-us/library/8dd52916-f77d-4444-b593-1f7d6f330e5f1033.mspx?mfr=truehttp://go.microsoft.com/fwlink/?LinkID=105623&clcid=0x409http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409


40/42

Resources (cont'd)Resources (cont'd)SharePoint Capacity Planning Toolhttp://technet.microsoft.com/en-us/library/bb961988.asp

Tools for Performance and Capacity Planninghttp://technet2.microsoft.com/Office/en-us/library/301ed

Visual Studio 2005 Team Test Edition: Testing Demoshttp://www.microsoft.com/downloads/details.aspx?Famil

( d)
http://technet.microsoft.com/en-us/library/bb961988.aspxhttp://technet2.microsoft.com/Office/en-us/library/301ed832-95da-4251-b266-7be6288f7ea01033.mspxhttp://www.microsoft.com/downloads/details.aspx?FamilyId=88F7CB8B-473B-4ED5-BA47-ABBC06D0048E&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=88F7CB8B-473B-4ED5-BA47-ABBC06D0048E&displaylang=enhttp://technet2.microsoft.com/Office/en-us/library/301ed832-95da-4251-b266-7be6288f7ea01033.mspxhttp://technet.microsoft.com/en-us/library/bb961988.aspx


41/42

Resources (cont'd)Resources (cont'd)

Custom Caching Overview

http://msdn2.microsoft.com/en-us/library/aa5897

How to Optimize a SharePoint Server 2007Web Content Management Site forPerformance

http://msdn2.microsoft.com/en-us/library/bb727371.aspx

Ottawa SharePoint User Group

http://sharepoint.microsoft.com/sharepoint/worldwide/ca/ottawa
http://msdn2.microsoft.com/en-us/library/aa589700.aspxhttp://sharepoint.microsoft.com/sharepoint/worldwide/ca/ottawa/http://sharepoint.microsoft.com/sharepoint/worldwide/ca/ottawa/http://msdn2.microsoft.com/en-us/library/aa589700.aspx