SharePoint 2010 – Installation and maintenance – best practices

SharePoint 2010 – Installation
and maintenance – best
practices

Toni Frankola
Acceleratio d.o.o.
http://sharepointusecases.com

History Lesson

2012
WINDAYS12 TECHNOLOGY OBRAZOVNI PARTNER

History Lesson

1912

14.4.1912 23:39


Mistakes

• Ignored warnings

• Sailing too fast

• Construction QA

• Iceberg 1:10


Contents

Installation Patching SQL

Capacity Monitoring Backup

Upgrade Language Packs Tools and Scripts


Before installation

• Choose your edition: Foundation / Sta / Ent

• Services I need…

• Hardware I need (read minimal reqs)

• Additional software (SQL, Windows…)

• Check licensing options

• OWA requires a license and key

• Control SharePointa deploys with GP


How to setup

• Minimum of 2 SharePoint farms

• Test / Production

• Only 1 farm = no Production farm

• Prepare & Learn it’s not Next > Next


Hardware

• 4 cores

• 8 GB of RAM

• 100 GB C: Drive
Windows, Program Files, Updates

• Second
Logs and stuff


SharePoint 2010 – Installation and maintenance – best practices

Repeat this procedure for

• Office Web Apps

• Other products (Project Server)

• …


Language packs

Formulas and
Per User columns Turn ON

Regional settings Automatic switch Error messages

Translate content


PowerShell Install

• http://tinyurl/SPFarmConfig ili http://autospinstaller.codeplex.com/


Patching
• RTM = Release to Manufacturing
• CU = Cumulative update
• SP = Service Pack


When should I install a patch?

• Install SP1

• Install CU if affected with error

• Check community blogs
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx
?ID=224

• Currently „stable” : SharePoint 2010 SP1 + December
2011 CU


Patching procedure

• Backup

• Unpack files

• Run configurtation wizard

• Repeat on each server


Patches

• Various flavors

• Foundation / Server

• Language Packs


Installing today?

• Try to use SQL 2012

• Windows Server 2008 R2 + all patches

• SharePoint 2010 + SP1 + Dec11 CU


Installing today? (2)

• Slipstreaming patches


Service Accounts
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=237

Account name Role
sp_install Used to install SharePoint binaries.

sp_farm Farm account. Used for Windows Timer Service,
Central Admin and User Profile service

sp_webapp App pool id for content web apps

sp_serviceapps Service app pool id
sp_search Search process id
sp_content Account used to crawl content

sp_userprofile Account used by the User Profile services to access
Active Directory
sp_superuser Cache account
sp_superreader Cache account

SQL Best Practices for SharePoint
http://technet.microsoft.com/en-us/library/hh292622.aspx

• Use a dedicated server for SQL Server 2008 (Configure specific SQL
Server 2008 settings)

• Pre-grow all databases and logs if you can. Be sure to monitor the
sizes so that you do not run out of disk space.

• Limit content databases to 200 GB.

• Defragment and rebuild indices daily, if you can absorb the
downtime required to rebuild.

• Be sure that you back up and truncate the log files

• Test Restore

• Continuously monitor SQL Server storage and performance

Challenges

• User Profile Service
http://technet.microsoft.com/en-
us/library/ee721049.aspx

• Configuring Search-a
Security
Schedule


Backup

• SLA?

• Must have: Content databases

• Other databases?

• PowerShell backup, CA backup, SQL backup, 3rd
party

• Test it!!!


Regular checks

• Event Log

• ULS Log (ULS Log Viewer)

• Usage, Health logs

• Performance Counters

• Disk (if no other monitoring tools)

• Search


Warmup

• Can be configured as Search job

• Web Site search (npr. http://intranet/default.aspx)

7:00
2:00
Working
Recycle
day starts

6:00
Search
warmup

Caching

• Blobcaching
us/library/cc770229.aspx

• SharePoint caching


Sites and templates

• Prepare site templates(Team Site)

• Prepare document templates


Features

• Different editions and

• Different templates have different features


PDF icon & iFilter

• Follow instructions

• or automate with PowerShell


Capacity Limits

• Laws of physics

• SharePoint Server 2010 capacity management:
Software boundaries and limits
us/library/cc262787.aspx

• Quotes


Capacity Limits - example
Limit Maximum value Limit type Notes
Application 10 per Web Supported The maximum number is determined by hardware
pools server capabilities.
This limit is dependent largely upon:
The amount of RAM allocated to the Web servers

The workload that the farm is serving, that is, the user
base and the usage characteristics (a single highly
active application pools can reach 10 GB or more)

Content database 200 GB per Supported We strongly recommended limiting the size of content
size (general content database databases to 200 GB, except when the circumstances in
usage scenarios) the following rows in this table apply.
If you are using Remote BLOB Storage (RBS), the total
volume of remote BLOB storage and metadata in the
content database must not exceed this limit.


2007 upgrade workflow

8. Test and back 9. Install 2010
1. 2007 SP2
to step 3. Prod

7. Mount- 10. Repeat steps
2. Install 2010
SPContentDB 4,5,7

3. Preupgrade 6. Back to Step
check 3.

4.
5. Test-
Backup/Restore
SPContentDB
WINDAYS12 TECHNOLOGY OBRAZOVNI PARTNER 2007DB

Document your farm

• SharePoint has hundreds of settings

• Different admins or partners

• Make documentation


Documentation Toolkit for SharePoint
http://spdockit.com


Questions
http://sharepointusecases.com
http://slideshare.net/tonifrankola

SharePoint 2010 – Installation and maintenance – best practices

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to SharePoint 2010 – Installation and maintenance – best practices (20)

More from Toni Frankola (13)

Recently uploaded (20)

SharePoint 2010 – Installation and maintenance – best practices