Upload
joel-oleson
View
4.945
Download
1
Embed Size (px)
DESCRIPTION
SharePoint 2010 Upgrade Best Practices Teched Brazil by Joel Oleson. Includes strategy for upgrade including details on the common upgrade methods including additional best practices, a decision tree, and solutions.
Citation preview
SETEMBRO, 2010 | SÃO PAULO
Joel OlesonSr. SharePoint ArchitectQuest Software
SharePoint 2010 Upgrade Best Practices
CÓDIGO DA SESSÃO: OSP302
3
10 Years of SharePointSharePoint Product Architect, Evangelist & Strategy @ Quest
Twitter: @joelolesonEmail: [email protected]
Who is SharePoint Joel?
4
SharePointJoel.com
5
Upgrade
Learn
Prepare
TestImplement
Validate
BeforeDuring & After
6
Pre Upgrade
7
SharePoint 2010 Requirements
SharePoint 2007 SP2 Update (Recent CU or at least October highly recommended)
64 bit operating system for application serversWindows Server 2008 or 2008 R2 + SP & Hotfixes included in PreReq Installer
64 bit SQL Server2008 R2+, 2008 SP1 CU5 or later, 2005 SP3 CU5 or later***
Virtualization is supported and very common
*** Upgrade or Installation will fail w/o proper CU
8
Running PreUpgradeCheck (in SP2007 Sp2)
PreUpgradeCheck Failed Report (snippets)Selections from PreUpgradeCheck
10
Test-SPContentDatabase
11
Upgrade
12
Insight on Upgrade
Binary UpgradeIn Place - New Timeout, Resume on failuresDatabase Attach - New Parallel, Progress Indicator
Visual UpgradeSeparate processDelegation by default
Binary Upgrade
Visual Upgrade
13
In-Place Upgrade
All-at-once upgradeMust upgrade the whole farm at one timeNo SP 2007 and SP2010 in same farmSchedule downtime
Simplest approach, but *most risky*!No going back
Resume Upgrade if problems occurRecommendations
Run Test-SPContentDatabase from SP 2010 farm against databasesDo a full farm backup before you start!
14
Pre Requisite Installer
15
In Place Upgrade - Install
16
In Place - Binary Approach to Upgrade
Pre-Upgrade
Check 2007 farm
Fix Issues
Upgrade Binaries with In place
(Setup)
Fix Issues Visual Upgrade Verify
Caution: Not recommended for most deployments…
17
Why I don’t recommend In-Place Alone
18
Database Attach Upgrade
Safer, Requires more planning (A good thing)Upgrade is done on a separate 2010 farm
Done database-by-database Can be used with 2nd step visual upgrade
Use Test-SPContentDatabase (PowerShell cmdlet) to test database firstTo attach
Mount-SPContentDatabase (PowerShell)STSADM –o Addcontentdb operation
Parallel database upgrades are possible
19
DEMO
Test-SpContentDatabaseMount-SpContentDatabaseUpgrade Status
20
Attaching Database to SP2010 Farm
21
Central Admin Upgrade Status
22
No Brainer - Read-Only Database Strategy
23
DB Attach - Binary Approach to Upgrade
PreUpgradeCheck
on SP2007
farm
Fix issues
Create Destination farmUpgrade Services(consider in-place)
Test-SPContentDataba
ses
Add solutions
/Fix issues
Set ReadonlyDatabase
Attach Content
Databases
Visual Upgrade
Recommended for most deployments…
24
Visual Upgrade
Stay in 2007 (default) or move to 2010 UI2010 ships 2007 Master pages and CSSUI Preview capability
Farm admin or site admin controlledWeb level setting
Some items not 2007 UI compatibleMy site hostPWA site collectionReport Server web parts
25
Demo
Read-OnlyVisual Upgrade
26
Post Binary Upgraded Site: Preview Visuals
27
Visual Upgrade Options
28
29
What about the Fabulous 40 Application Templates?
What do you want to do?I want to continue using them
Install Upgraded Templates - Fab 40 on Destination farmConvert Templates - .STP to .WSP
I want to remove themRemove the .stp (Remove the template)Export lists or use third party tools to move into OOB Site Defs
http://bit.ly/dhQUjd
30
Upgrade Strategies
31
PowerShell Upgrade Cmdlets
Test-SPContentDatabaseDiscover and Document issues 2007/2010
Mount-SPContentDatabaseInitiate Content database B2B/V2V upgrade
Upgrade-SPContentDatabaseResume Content database B2B/V2V upgrade
Upgrade-SPEnterpriseSearchServiceApplicationSearch Service Application Instance
Upgrade-SPSingleSignOnDatabaseO12 SSO data to Secure Store database
32
Hybrid Upgrade Considerations
Best of In PlaceConfiguration databaseSite Definitions may be upgradedEasier SSP -> Service App Upgrade
Best of Database AttachFast with multi database parallel upgrade
33
Consider a Hybrid Upgrade
Make a copy of
the farm
Set databases Read-Only on Source
Upgrade Binaries/ Services with In Place
upgrade on
Secondary
Test-SPContentDatabases
Database Attach
Content Databases in Parallel
Visual Upgrade
34
Decisions???
Customized?Uptime?New HardwareExtra?Hardware Ready?Virtual/Rollback?MSDE/SQL Express?
35
SSP to Service App
Each SSP upgrades into:A Search service appA User Profiles service appAn Excel service appAn App Registry back-compat service app
New Services can be activated/added
36
Visual Upgrade Strategies
Upgrade the UI at the same timepsconfig.exe –cmd upgrade –preserveolduserexperience falseUpdateuserexperience parameter of the Mount-SPContentDatabase or STSADM
Stager Upgrade (Hide UI)Post Upgrade: Site Settings | Site Collection Administration | Supported User Experiences
Delegate UI Upgrade (Default)psconfig.exe –cmd upgrade –preserveolduserexperience true
37
In Place Upgrade - Visual Upgrade Decisions…
38
Troubleshooting/Common IssuesMissing server-side files or customizations, such as features or Web PartsConfiguration issues in the server farm, Web application, or services, such as managed paths or services that are not startedAdditional issues in sites discovered on a site-by-site basis, starting with high-impact, high-profile sitesDisk Space or CPU/Memory ConstraintsDon’t forget Forms to ClaimsProfile Import & FIM (CU has fixes, security requirement)
39
Released to the Web
SharePoint 2010: Best Practices for Upgrading and Migrating
Get Prescriptive guidance on Upgrade MethodsDrill deep into assessment toolsCompare Migration toolsSave yourself time
40
Why Consider third party tools?
Getting out of customizations…Quest Migration Manager
2003 to 2010 with post Migration Sync2007 to 2010 in beta
Notes to SharePoint Migrations
www.quest.com
41
Obrigado!
Por favor preencha a avaliação
43
Learn More about SharePoint 2010
Information forIT Prosat TechNet
http://MSSharePointITPro.com
Information forDevelopers
at MSDNhttp://MSSharePointDeveloper.com
Information forEveryone
http://SharePoint.Microsoft.com
© 2008 Microsoft Corporation. Todos os direitos reservados. Microsoft, Windows, Windows Vista e outros nomes de produtos são ou podem ser marcas registradas e/ou marcas comerciais nos EUA e/ou outros países.Este documento é meramente informativo e representa a visão atual da Microsoft Corporation a partir da data desta apresentação. Como a Microsoft deve atender a condições de mercado em constante alteração, este
documento não deve ser interpretado como um compromisso por parte da Microsoft, e a Microsoft não pode garantir a precisão de qualquer informação fornecida após a data desta apresentação. A MICROSOFT NÃO DÁ QUALQUER GARANTIA, SEJA ELA EXPRESSA, IMPLÍCITA OU ESTATUTÁRIA, REFERENTE ÀS INFORMAÇÕES DESTA APRESENTAÇÃO.