23
Is a Single Server Sufficient for a SharePoint Deployment? Brainstorm SharePoint Deployment Planning Mark Macrae

Suguk nottm sept 2010 share point 2010 farm design considerations

Embed Size (px)

DESCRIPTION

Presentation by Mark Macrae at SUGUK Nottingham September 2010. It begins by asking the question: Is a Single Server Sufficient for a SharePoint Deployment? The asnwer is 'It Depends!' but the presentation explains all the considerations.

Citation preview

Page 1: Suguk nottm sept 2010   share point 2010 farm design considerations

Is a Single Server Sufficient for a SharePoint Deployment?Brainstorm SharePoint Deployment Planning

Mark Macrae

Page 2: Suguk nottm sept 2010   share point 2010 farm design considerations

• Director Intelligent Decisioning Ltd• 7 Years SharePoint Exp• SUGUK Organiser for Midlands• SharePoint Saturday• (shh...support West Ham)

About Me

Page 3: Suguk nottm sept 2010   share point 2010 farm design considerations

It Depends!

Page 4: Suguk nottm sept 2010   share point 2010 farm design considerations

Considerations

• SLAs• Users• Authentication• Licensing• Location • Hardware• Software (client and server)• SQL Server• SharePoint Features• Information Architecture• Staff / Roles

Page 5: Suguk nottm sept 2010   share point 2010 farm design considerations

SLAs

• SLAs affect everything– Recovery plan– Topology– Server spec

• At least:– Approx Users– Max down time (RTO)– Max data loss (RPO)

Item Level Recovery

Disaster Recovery

High Availability

Page 6: Suguk nottm sept 2010   share point 2010 farm design considerations

SLAs

• Define RTO/RPO targets and design a solution to meet these– RTO (Recovery Time Objective)

• Maximum acceptable duration of time of system inoperability (Downtime)– RPO (Recovery Point Objective)

• Maximum amount of acceptable data loss

Commitment Annual downtime

99% 87 hours

99.9 9 hours

99.99 53 mins

99.999 5 mins

Page 7: Suguk nottm sept 2010   share point 2010 farm design considerations

Users• Who are your users?

– You know them individually (Intranet)– You know them as partners/customers (Extranet)– You don’t know them (Internet)

• Define who will be using the system• How will they use it?

– Which browsers?– Mobile?

• Where are your users base?– Local?, Global?, Both?

• How many users?• How will they be using it?

Page 8: Suguk nottm sept 2010   share point 2010 farm design considerations

Authentication• How will you authenticate your users?• Depends largely on previous slide

Classic Authentication• Active Directory authenticates a user, provides an NT Token. The token is used to authenticate

to SharePoint. SharePoint consumes that token and it's converted into an SPUser object for authorization

Claims Authentication• SharePoint redirects a client to the associated trusted identity provider. The identity provider

authenticates clients and provides a security token e.g.– NT, SAML, FBA

Kerberos – when and why would you need it? …….

Page 9: Suguk nottm sept 2010   share point 2010 farm design considerations

Licensing

• Foundation• Standard• Enterprise• CALs vs External Connector

Page 10: Suguk nottm sept 2010   share point 2010 farm design considerations

Location

• On Premise vs Hosted?• Capacity?– Staff / Administrators– Skills– Costs– Worry

• Next session may help

Page 11: Suguk nottm sept 2010   share point 2010 farm design considerations

Hardware• Physical vs Virtual?

– Skills– Recovery plan– Budget

• SharePoint 2010 & Foundation – X64 Quad core processor– 4GB for Dev/8GB for production– 80GB System Partition– SQL Server 2008 X64

• Prices

Page 12: Suguk nottm sept 2010   share point 2010 farm design considerations

Naming Conventions• Databases• Web Applications• User/Service Accounts• Servers

Page 13: Suguk nottm sept 2010   share point 2010 farm design considerations

SQL

• Which version?• Disk – lots!• RAID Configuration• Instances• Business Intelligence• SSRS

Page 14: Suguk nottm sept 2010   share point 2010 farm design considerations

Temp Logs Search DataTemp

Even Read/Write

RAID 1/1+0

Logs

Even Read/Write

RAID 1/1+0

SearchN:1

Read/Write

RAID1/1+0

DataN:1

Read/Write

RAID 5

SQL

Page 15: Suguk nottm sept 2010   share point 2010 farm design considerations

Recovery Plan

• Disaster Recovery– Not just about Backup/Restore!– List all possible scenarios and plan for each one with

SLAs in mind• Hardware, Software, User error, environmental etc

– Backup Tools• SharePoint vs SQL

– 3rd Party?

• Hosted – do you need to worry?

Page 16: Suguk nottm sept 2010   share point 2010 farm design considerations

Recovery Plan

• High Availability– Servers– Services– Topology– Load Balancing solution– Database Availability

• Backup/Restore is not HA– Not quick enough

Page 17: Suguk nottm sept 2010   share point 2010 farm design considerations

SharePoint Feature Set

• PerformancePoint Services• Excel Services• Access Services• Visio Services• SQL Reporting Services• ….• = More of everything!!!

Page 18: Suguk nottm sept 2010   share point 2010 farm design considerations

SharePoint Databases

SharePoint 2007 SharePoint 2010

There are a lot more databases in 2010!

Page 19: Suguk nottm sept 2010   share point 2010 farm design considerations

Domain Account Considerations

• Best Practise of Least Privileges• SharePoint 2010 requires even more accounts!• Basic Accounts

• Farm Account (Database Access Account)• Install/Setup Account• Web Application App Pool Accounts

• Service Application Accounts– App Pool Identities – Unattended Service Accounts

Page 20: Suguk nottm sept 2010   share point 2010 farm design considerations

Environments

• Which environments do you REALLY need?– Dev– Continuous Build– UAT– Production

• More environments = – More maintenance = More resources– Patching

• SDLC!!

Page 21: Suguk nottm sept 2010   share point 2010 farm design considerations

Resources / Roles

• Most organisations have the familiar role of ‘The SharePoint Guy’

Page 22: Suguk nottm sept 2010   share point 2010 farm design considerations

Resources / Roles

• Network Administrator• SQL DBA• SharePoint Farm Administrator• Site Collection Administrators• Business ‘Champions’• Designer• Developers

Page 23: Suguk nottm sept 2010   share point 2010 farm design considerations

Scared?

• Governance• Security / Authorisation• Patching/Service Packs• Developed Solutions• ….