five pillars of sharepoint governance supportability

©2011 Quest Software, Inc. All rights reserved..

Chris McNulty, Quest SoftwareSharePoint Strategic Product Manager

The Five Pillars of SharePoint Governance - Supportability

Jason Himmelstein, SentriSharePoint Practice Director

June 6, 2012

Toll-free: +1 (888) 632-5004 Toll: +1 (913) 643-0957 Participant code: 870156

2


IT Manager

Cut through the SharePoint chaos, control costs and simplify the enforcement of your governance strategy with Quest solutions for SharePoint

SharePoint Developer

Stand up for your right to customize SharePoint without code and easily deploy custom applications across your environment

SharePoint Administrator

Reclaim your workday and declare your right to focused, simple and fast SharePoint administrative solutions

www.Quest.com/ControltheChaos

3


Agenda

• What is Governance?

• The 5 Pillars of SharePoint Governance

• What is Supportability?

• How Does Supportability Fit in your Governance Plan?

• How Quest Addresses SharePoint Supportability

4


Five Pillars Of SharePoint Governance

Security the policies and procedures to protect SharePoint

Auditing the policies and procedures to track user, content and configuration compliance

Reliability the policies and procedures to prevent user productivity interruptions

Usability the policies and procedures to ensure user adoption and business productivity

Supportability the policies and procedures tofix what goes wrong

5


The Five Pillars of SharePointGovernance Webcast Series

View on Demand Recordings here:

www.Quest.com/FivePillarsWebcasts

Webcasts Date TimeFive Pillars of SharePoint Governance Overview

On Demand

1. Five Pillars of SharePoint Governance - Security

On Demand

2. Five Pillars of SharePoint Governance – Auditing

On Demand

3. Five Pillars of SharePoint Governance – Reliability

On Demand

4. Five Pillars of SharePoint Governance – Usability

On Demand

5. Five Pillars of SharePoint Governance - Supportability

Wed, June 611:30 a.m. ET / 8:30 a.m PT / 4:30 BST

6


Want to learn how to develop and implementSharePoint supportability in your governance plan?

Sign up for a complimentary one-on-one session with

today’s partner and Quest to:• Glean more best practices for SharePoint supportability

• Learn how to implement these best practices in your environment

• Discuss upcoming SharePoint supportability projects in your

organization

Sign up Today!

www.Quest.com/SharePointSupportabilityConsultationSpace is limited!

http://www.quest.com/SharePointSupportabilityConsultation


Jason Himmelstein, MCTS, MCITPSharePoint Practice Director@sharepointlhorn Sentri, Inc.SharePoint Practice Director

Sentri, Inc.@Sentri_Inc

The Five Pillars of SharePoint Governance - Supportability

8


About Me

• SharePoint Practice Director, Sentri Inc.

• Microsoft vTSP

• SharePoint Foundation Logger (http://spflogger.codeplex.com)

• Web: www.sentri.com

• Blog: www.sharepointlonghorn.com

• Twitter: @sharepointlhorn

• LinkedIn: www.linkedin.com/in/jasonhimmelstein

http://spflogger.codeplex.com/

http://www.sentri.com/

http://www.sharepointlonghorn.com/

https://twitter.com/

http://www.linkedin.com/in/jasonhimmelstein

9


Agenda

• Day to Day Supportability• Correlation IDs

• The Developer Dashboard

• Configurable ULS \ Flood Protection

• Architecting for Supportability• Infrastructure design

• SQL Performance

• Patching your Environment• Why patch?

• Microsoft patching methodology

• Patching Process

10


Day to Day Supportability

11


Correlation IDs

• What is this weird 32 character message & why do I

care?

• How are they used in SharePoint 2010?

• How are they useful?

12


The Developer Dashboard

• What is the Developer Dashboard?

• How can the Developer Dashboard help my

supportability?

13


The Developer Dashboard (cont’d)

14



Angry SharePoint!

15


Happy SharePoint!


16


Configurable ULS Logs

• Size limitation

• Easy Granular tuning, with visibility into what’s tuned

• Ability to specify number of days to log

17


Flood Protection

• I’m smart, why don’t I want to see everything?

• How does Flood Protection work?

• How do I turn it off and on?

With this option enabled, if the same event fires 5

times within 2 minutes, SharePoint will suppress the

event from logging and throw a summary event at

the 2 minute mark.

The default behavior and can be customized using

PowerShell and the Set-SPDiagnosticConfig

cmdlet.

18


Architecting for Supportability

19


Infrastructure Design

Virtualization

Benefits

• Snapshot capability

• Rapid system deployment

• HA\DR ability

• Centralized Management

Drawbacks

• Loss of minimum 8% compute for

overhead

• Limitations on addressing full hardware

• Disks are often stored as single/multi-file

• Centralized Networking

Physical

Benefits

• No virtualization overhead

• Ability to target DBs to separate

physical spindles

• Only OS limits on Hardware

• Simple Networking

Drawbacks

• Backup & recovery time

• Limited snapshot ability

• Costly & lacking Centralized

Management

• Failover limitations

20


SQL Server Performance

• Pre-grow databases• Requires more space initially

• Dramatic increase in performance

• Databases like contiguous space

• Auto-growth • Immediately change from 1m increments

• Do not use “Grow by %” setting

• 50-100m maximum growth per required

• Schedule maintenance task to check size & grow in off peak hours as

required

21



• I\O requirements DB Files RAID Level Optimization

1 TempDB data 10 Write

2 TempDB logs 10 Write

3 ContentDB data 10 Read\Write

4 ContentDB logs 10 Write

5 Crawl DB logs 10 Write

6 Crawl DB data 10 Read\Write

7 Property DB logs 10 Write

8 Property DB data 10 Write

9 Services DB logs 10 Write

10 Services DB data 5/10 Read\Write

11 Archive Content DB 5 Read

12 Publishing Site Content DB 5 Read

22



• Sizing recommendations• Recommended limit for ContentDBs: 200G

• Maximum supported: 4TB

• Includes Remote BLOBs

• Backup/Restore timing

• Simple vs. Full recovery mode

23



• Database Instance Isolation• Secure Store Database

• SharePoint core databases

• Content Databases

• Search

• Highly Transactional non-SharePoint DBs

• Drawback• Lose the central management in a single SQL Server Management

Studio window

24


Patching your Environment

25


Why Upgrade?

• Why do we upgrade?

• If it ain’t broke, don’t fix it

• Consistency

• Security

• Microsoft Support Services

26


Microsoft patching methodology

• Upgrades vs Patches

• Microsoft Patch Terminology• Hotfix

R Point solutions – limited testing

• Cumulative Update

R Roll-up package of Fixes – standard testing

• Service Pack

R Enhancements \ Fixes \ Hotfixes – through testing

• Are SharePoint Patches removeable?

27


Patching Process

• Snapshot environments before patching

• Review fixes in patch• Allow 2-4 weeks of life in the wild to validate success of patch

• Apply to development environment to test custom code• Allow 1-2 weeks for developers to test & validate

• Apply to QA environment & regression test• Allow 1-2 weeks for testing & validation against test plans

• Apply to Production• Validate

• Record patch level before & after patching• Looks like: Build 14.0.6120.5000


Chris McNulty, MCTS, MCSEQuest SoftwareSharePoint Strategic Product Manager

Implementing Supportability in Your Environment

29


@cmcnulty2000

Chris McNulty• SharePoint BU, Quest Software

• 10+ years with SharePoint

• 20 years consulting (led KMA SharePoint practice) and financial services technology (Santander, John Hancock/Manulife, GMO, State Street)

• MBA in Inv Mgmt from Boston College

• Write and speak often on Microsoft IW technologies (blogs & books)

• MCSE MCTS MSA MVTSP MCC

• Hiking, cooking, playing guitar, colonial history, photography

• My family: Hayley, three kids (17, 8, 5) and my dog Stan

30


Previously, on “The Five Pillars of SharePoint Governance”…

• Incident: an event with a material impact on an IT service, resulting in degraded performance or unavailability

• Reliability – preventing incidents

• Problem resolution – long term removal of incident root cause

31


Four key activities

• addressing common user requests

• resolving incidents

• rapidly collecting troubleshooting information

• recovering from major system problems

32


User requests

• Supportable customization

• Site templates

• Fab 40 – SP2007

• SP2010 – www.techsolutions.net

• Project governance• Internal resourcing

• External resourcing

• Catalog of service vs. custom

http://www.techsolutions.net/

33


Incident resolution

• Incident capture

• Incident tracking

• Knowledge management

34


Quest Solutions

35


Quest Web Parts – User Requests

• Provides a template Help Desk

site ready to use!

• Design without code!

• Offload support to Quest

• ezEdit: Embedded configuration tool

• ezLearn: Provides in context

guidance and links to training

• Recompose legacy applications

• An “approved” way to customize

SharePoint without full app dev

36


Reduce the “Project Threshold”

37


Info & Policy - Site Administrator for SharePoint

• Enterprise Overview Report

• SharePoint capacity needs

• Storage usage

• Other reports encompass:

• Size and load among Content Databases

and Web Applications.

• Content usage by database and by SQL

• Content footprint by file types, versions,

recycle bins, etc.

• Unused sites

• Web-based Information Portal Dashboard

www.quest.com/site-administrator-for-sharepoint

http://www.quest.com/site-administrator-for-sharepoint

38


Info - Deployment Manager for SharePoint

• What’s Changed?

• Compare, deploy and control code

and data across multiple

environments

• LiveCompare – Compare sites side

by side, identify the missing parts and

create deployment tasks

• Solutions Manager – Adds rich

deployment and management

capabilities for SharePoint Solution

Packages (WSP)www.quest.com/deployment-manager-for-sharepoint

http://www.quest.com/deployment-manager-for-sharepoint

39


Recovery Manager for SharePoint• Reduces the RTO for farm restore

from SharePoint farm backup

• Simplifies scheduling native backups

• Significantly improves RTO for

granular content restore without

creating duplicate backups

• Integrates with native SQL and

SharePoint backups, as well as

leading 3rd party backup solutions

such as Symantec Backup Exec,

NetBackup, IBM Tivoli

• Also works with Quest data protection

products such as Lite Speed for SQL,

vRanger Pro and NetVault.

• Maintains role separation for efficient

operations

www.quest.com/recovery-manager-for-sharepoint

http://www.quest.com/recovery-manager-for-sharepoint/

40


demoQuest Solutions

41


Conclusion • Supportability…so you can count on

SharePoint…you can count on Quest.


www.Quest.com/SharePoint

Questions and Answers

43






• Discuss upcoming SharePoint supportability projects in your organization

Sign up Today!



44






• Discuss upcoming SharePoint supportability projects in your

organization

Sign up Today!



45


More information

• SharePoint architecture design patterns in Chris’ e-

book entitled SharePoint 2010 Consultant’s Handbook

– A Practical Field Guide • Get your free copy here http://www.quest.com/get-chris-book

http://www.quest.com/get-chris-book

http://www.quest.com/get-chris-book

46


The Five Pillars of SharePointGovernance Webcast Series

View on Demand Recordings here:

www.Quest.com/FivePillarsWebcasts

Webcasts Date TimeFive Pillars of SharePoint Governance Overview

On Demand

1. Five Pillars of SharePoint Governance - Security

On Demand

2. Five Pillars of SharePoint Governance – Auditing

On Demand

3. Five Pillars of SharePoint Governance – Reliability

On Demand

4. Five Pillars of SharePoint Governance – Usability

On Demand

5. Five Pillars of SharePoint Governance - Supportability

Wed, June 611:30 a.m. ET / 8:30 a.m PT / 4:30 BST

five pillars of sharepoint governance supportability

Technology

quest solutions

sharepoint chaos

pillars of sharepointwed

supportability fit

governance plan

governance strategy

day supportability correlation

procedures totrack user