Wednesday, May 29, 2019

My journey for upgrading web applications from SharePoint 2013 to SharePoint 2016: Step by step

Leave a Comment
I know its probably a bit late for upgrading from SharePoint 2013 to SharePoint 2016 as it should be upgraded to 2019. However, 2019 SharePoint applications upgrade I will write later on. Recently did a client project upgrade from SharePoint 2013 to SharePoint 2016, so here is my journey & steps which I followed:

Step 1: As normal procedure create a new web application from SharePoint Central Admin
Step 2: From managed content databases, remove content database for web application for Step 1

Step 3: Restore SharePoint 2013 content database on Database server
Step 4: From same managed content database choose web application created in Step 1
Step 5: After mounting content DB, we need to run few powershell commands to verify warning, possible errors which may happened during upgrade process and these are following. However, I used to add wsp solutions in order to verify possible issues may happened for code compatibility:

Step 6: As discussed we need to run series of Powershell command, first of it is: 
Test-SPContentDatabase -Name <Content_DB_Name> -WebApplication <WebAppName>
Above command will test content db against web application for all customization done as per content db are also installed in farm (WSP which we did in Step 5)
For me it just generated few warning which would not stop this upgrade as shown below


Step 7: Next powershell command in this series is to mount content db against this web application: 
Mount-SPContentDatabase -Name “<Content_DB_Name>” -DatabaseServer “<DBAlias>” -WebApplication <WebAppName>
According to microsoft documentation this command this will attach content db to web applicatoin
For me it don't show any error as show below


Step 8: Then we need to test the mounted site as Test-SPSite site url. This command run some series of health check against mounted spsite, site collection & its contents
Again it dont give any error for me

Step 9: Repair-SPSite -identity siteurl  and this command will fix any issues that it finds. For my case didn't find much


Step 10: And lastly Upgrade-SPSite siteUrl -VersionUpgrade
This command will actually upgrade site collections associated with this web application to SharePoint 2016 mode










If You Enjoyed This, Take 5 Seconds To Share It

0 comments: