Contents
Overview of Upgrade plan
The
SharePoint 2013 upgrade process model followed in this document is a Microsoft
recommend method of upgrade from SharePoint 2007 to SharePoint 2013. First 2007
is migrated to interim SharePoint 2010 Farm with all the customization carried
forward from 2007 and from SharePoint 2010 to 2013. To minimize the impact of
upgrade to end users no changes in architecture are carried before or during the
upgrade and database upgrade option is adopted in the double hop upgrade plan.
The
upgrade plan consist of 1. Pre-upgrade stage. 2. Trail upgrade. 3. Rehearsal
upgrade & checklist. 4. Communication & downtime plan. 5. Production
upgrade.
Pre-upgrade:
The main object of this stage is to gather Information, Hardware, Software,
setup user accounts and to run the pre-upgrade check list and fix some of the housekeeping
tasks prior to the actual migration.
Trail-upgrade:
The main object of trail upgrade is identify 1. Upgrade errors & document
errors. 2. Find fixes, document fixes and apply fixes for SharePoint 2010 farm.
The outcome of trail upgrade will facilitate Rehearsal upgrade. Trial upgrade will be performed for stage 1
and stage 2.
Rehearsal-upgrade:
The main object of the rehearsal-upgrade is calculated exact time and go
through the order of the checklist and apply fixes. The rehearsal-upgrade will
facilitate the real production upgrade.
Communication
& Downtime plan: This stage is mainly for stakeholders and management to
communicate the outage of SharePoint, Changes to any sites/workflows etc.
Training end users and impact to end users. A clear plan and picture can be
implemented later once completely carrying out the Rehearsal upgrade for stages
1 and 2.
Production
upgrade plan: This is the actual production upgrade by now all the information
relating to upgrade is clear. And a smooth execution of the upgrade and
implementing the checklist and its fixes are carried out. Communication plan and
end user training and impact are carried out prior to this stage. A scheduled
downtime on Friday morning is communicated. Upgrade email plans are sent out
and SharePoint 2007 is in read only mood and Server is unavailable for end
users until complete upgrade is performed.
Stage – 0
Requirement
gathering Phase & Document check list stage.
1. a. User IDs and passwords of all Farm,
SQL Server, SPInstall
Accounts
used in SharePoint Central Admin.
b. AD, DNS and forest, IP range,
subnet mask and other details.
c. Hardware / Software
gathering
Windows 2008 R2 with SP2.
Windows
2012 Servers with latest service packs installed.
Software (SQL Server 2008, SharePoint 2010/2013).
SQL Studio Management.
2008.
InfoPath Designer/ SharePoint designer 2010/ 2013
VS2008 / VS 2010 / VS 2012
Nintex 2010/Nintex 2013
c. Fire-wall and any
network restrictions to be removed for your ID for future tools to download like,
SPManager, ULS log viewer, Patches, hotfixes etc.
2. Identifying and document any hidden
Solutions / features / web parts source code unaware and used in SharePoint
sites. (Currently 12 Solutions
identified) - direct upgrade or re-work?
3. Identify & understand and document
Custom Scripts, Event receivers, Workflows.
4. Rework/ Publish of InfoPath forms for
2010 upgrade.
5. Identify and document Email enabled
lists for later testing.
6. Document Central Admin setting in
migration check list, Master pages, Themes, CSS, Logo etc...
7. Document and Clean-up sites/lists/documents
library.
a. Identify Performance bottle necks if
any and document it.
b. Create check list for manual migration
of solutions/ InfoPath/ workflows etc.
8. Make sure MOSS 2007 is upto date with
SP2 Cumulative updates..
9. Run Pre-Upgrade check tool /Scripts and
check and resolve the possible problems
Stsadm –O preupgradecheck
Following are common
problems.
a. Orphaned users active in SharePoint
but inactive in AD.
b. Trim Audit logs in SQL Server using
Studio.
c. Empty Recycle bins.
d. Find and delete Orphan sites.
e. Scripts to clean up Document Versions
in all Document library in entire farm to free up disk space. (Optional time
consuming task).
f. Database repair to detect corruption
for the following types orphaned items. Stsadm -0 databaserepair (Optional very
time consuming operation precaution).
Prepare
and review pre-upgrade checklist from step 2 to Step 9.
Stage – 1
Build of interim SharePoint 2010 Single
Server Test/Staging environment with trail licence for SharePoint server.
Review
Farm Infrastructure & Prep Environment
|
1 day
|
Install SQL Server and Patches on Database Server
|
0.5 day
|
Install SharePoint Prerequisites
|
0.25 day
|
Install SharePoint and SharePoint Patches
|
0.5 day
|
Install Language packs
|
0.5 day
|
Configure SharePoint Server
|
0.5 day
|
Buffer if something goes wrong
|
0.5 -1 day
|
Since we are following a
database attach upgrade we need to configure the services manually before the
attaching the database. Service application, Managed Metadata, and user profile
services to be started and configured.
The following database are copied
along with content db.
1. Managed Metadata Service db
2. User Profile Service Profile db
3. User Profile Service Social db
4. User Profile Sync DB
5. WSS_Content_Mysites
6. WSS_Content_SSP.
Once all the database are copied to
interim sharepoint 2010 envirnoment. New Service applications need to be
created for the copied databases.
Following are the commands to create
profile service application
a.
New-SPProfileServiceApplicaton -Name SharedServices2007
-ApplicationPool
"SharePoint Web Services Default" -ProfileDBName wss_2007_COntent_Profile
Next create proxy for the created
service applicaton
New-SPProfileServiceApplicationProxy
-Name ShareServiceMoss2007Proxy -ServiceApplication GUID
Assign permissions for the Service
Application. And test for user in profile search.
Next Upgrade Managed Metadata Service
Move-SPProfileManagedMetataProperty
Update Mysites.
Test Mysites health is good, Before
bringing to 2010.
Test-SPContentDatabase -Name Mysites_Content_DB -WebApplication URL
-> Resolve all the issues reported.
Once all the issues are resolved
attach the db to the new webapplication.
Stsadm
-o addcontentdb -url MysiteURL -database 2007DBname databaseserver
2010DBServer.
Run Variationfixuptool for publishing
sites
Stsadm -o variationfixuptool –url
a. Database attach upgrade to 2010.
Backup-Restore 2007Db
b. Create web application and link to
2007 DB by
1. Remove content db : Stsadm –o
deletecontentdb –url http:// -databasename 2007db.
2. Test content db :
Test-SPContentDatabase –Name 2007db –Webapplication name
c. Manually migrate solutions/features / InfoPath/
workflow.
InfoPath
Deploy cmd Update-SPInfoPathAdminFileURL -find
<OldUURLtoReplace> -replace <NewURL>.
d. Delete corrupted objects
stsadm -o databaserepair
-url <URL of SharePoint site> -databasename <name of database>
-deletecorruption
e. Attach Content DB.
Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer
<ServerName> -WebApp
f. Export and Import BDC
Post upgrade to Identify upgrade
errors and issues.
a. Migrate Site templates to SharePoint
2010.
b. If any errors find fix for upgrades,
Add fix to 2010 Environment.
c. Remove unused web-parts or closed web-parts
in Pages.
d. Test site collections and sub sites /
Custom solutions/ Web parts after upgrade. (Scripts to Check-in and Check-out
to eliminate 404 Page not found error).
e. SharePoint alerts stop working due to
URL changes. (Scripts for webapp or Admin Tool kit ) or
stsadm –o updatealert
f. Unit testing of creating sites,
document library, lists, kick-off workflows deploy new web-parts, test look and
feel in the SharePoint 2010 environment.
g. Perform above activity (rehearsal
upgrade) again to get accurate time second time and checklist and note the time
for migration.
h. Perform Visual Upgrade on
SiteCollections.
i. Release SharePoint 2010 environment
for review & testing. Site Admins to be involved here.
Stage – 2
In this stage
we are building 2013 staging environment preparing 2010 environment for
migration. Importance to be given to sequence of steps follows below.
Preparing 2010 SharePoint environment
for Migration.
1. Change the Authentication to claims in
2010 environment. Perform quick unit testing after the Change.
2. Build of SharePoint 2013 staging environment
(Dev / Test Server).
Farm Infrastructure & Prep Environment
|
1 day
|
Install SQL Server and Patches on Database Server
|
0.5 day
|
Install SharePoint Prerequisites
|
0.25 day
|
Install SharePoint and SharePoint Patches on Servers
|
0.5 day
|
Install Language Packs
|
0.5 day
|
Configure Application Servers and Establish a SharePoint Farm
|
0.5 day
|
Buffer time
|
0.5 – 1
day.
|
a. Initial stages of Database migration
is similar to 2007 to 2010 upgrade till creating service applications.
Important notes Stsadm is deprecated in 2013.
b. Database attach upgrade to 2013.
Backup-Restore 2010 content database to Sharepoint 2013 SQL Server.
c. Test & Verify database is running
by command Test-SPContentdatabase from SharePoint 2013 Farm.
d. Attach the content db to
WebApplication using Mount-SPContentdatabase.
e. Perform Site Collection health check
Test-SPSite –identity <url>
f. Upgrade site collections.
g. If Error use command “Repair-SPSite
–identity <url>
h. Review Infopath forms due to Claim authentication
impacts. Known issues are reported.
i. Test creating sites/lists/library/
workflows. Etc.
j. Identify upgrade errors and issues.
k. Find fix for upgrades, Add fix to 2013
Environment.
l. Test site all site collections/
solutions/ Web parts after upgrade.
Perform above activity again to get
accurate time second time. Log time and Check list.
Release 2013 for review
& testing. Site Administrators to be involved in this stage.
Stage – 3
Build Production environment 3 Tire
Staging farm with high availability.
A high level steps involved in the
Production setup are
1. Install new Windows 2012 R2 Server.
Configure TCP/IP properties and join to domain restart the server and logon
with domain account.
2. Install MS SQL server on Database
server and configure inbound rule in windows Firewall to allow incoming traffic
to SQL Server services. Enable dbcreator and securityadmin role for spInstall
account
3. Repeat Step 1 for App1 Server and
logon with spInstall and Install SharePoint 2013 prerequisites and install
hotfixes KB 2554876, KB2708075, KB2472264.
4. Install SharePoint 2013 on App1 as Application
server. Configure App1 as main Application server & host Central admin port
and create the new farm.
5. Install SharePoint 2013 on App2 as
Application server. Configure App2 by joining to existing farm. In central
admin stop Managed Service Microsoft SharePoint Foundation Web Application as
they are started on WFE1.
6. Repeat Step 1 for WFE1. Install Web
Server (IIS) role on WFE1
7. Install prerequisites on WFE1, Install
SharePoint Server on WFE1. Configure it to join exiting SharePoint Farm. And in
Central Admin configure and stop all services not need for Front End and enable
Microsoft SharePoint Foundation Web Application.
8. Repeat step 6 for WFE2.
9. Configure NLB for WFE1 and WFE2.
