Content database upgrade from SharePoint 2013 to SharePoint 2016
Pre-upgrade checks
- Make sure that if you have any site collection which has already been migrated to SharePoint 2013 but if they are in “SharePoint 2010” mode do upgrade them to the SharePoint 2013 UI and PowerShell ( You can follow this article for any quick help) .
- On source web application on SharePoint 2013 take not of all the managed path site collections if any and create them in the new SharePoint 2016 environment.
- Backup all content databases of the SharePoint 2013 databases using the SQL Server management studio.
- Make the source sites (Web Application/site collection) in read-only mode as part of your downtime window.
- Using SharePoint Central Administration, we can Set the lock for a particular site collection, which is pretty straight forward. Since, It’s possible to set the site collection to read-only mode using PowerShell, We can loop through the each and every site collection in the web application and set the site collection's status to read-only. Once done with the migration/maintenance, you can unlock the sites again.
- SharePoint Web Application to Read only using PowerShell
# Get the Web Application
$WebApp=Get-SPWebApplication "http://SharePoint.neelam.com"
#Loop through all site collections and Set read only status
foreach ($SPsite in $webApp.Sites)
{
$SPsite.ReadOnly = $true
#Or you can use: Set-SPSiteAdministration -LockState "Unlock" -Identity $SPsite.url
}
- Alternatively, you can make a note of all the content databases and set them as read only from the SQL Server managements studio.
Upgrade Procedure
- Restore the databases which you had backup earlier at point 3 in the new SharePoint 2016 SQL instance/cluster.
- Now you need to provide the db_owner rights to all the databases to the account which is running the SharePoint PowerShell commands in the new environment. (example neelam\sp_farm2016).
- Before we start the upgrade make sure the new SP2016 Web Application has all features/solutions etc have been installed.
- Run the below command. This command tests to make sure the new web application http://portal.neelams.com has all the solutions/features/templates as per its assets from the source web application.
- Test-SPContentDatabase -Name WSS_Content_WADB_2013 -WebApplication http://portal.neelams.com
- If the above commands returns no results and you back to the command prompt congrats you are good with the next step, else you might need to fix the missing components and install them in the new SP2016 environment.
- Run the below command. This command proceeds with the upgrade process for the specific database WSS_Content_WADB_2013.
- Mount-SPContentDatabase -Name WSS_Content_WADB_2013 -WebApplication http://portal.neelams.com
- Wait for the process to complete to 100% and then try to access the new site collection.
- If you get “Site is not being shared” error please go the Application management > Change Site collection administrators and add the new primary and secondary site collections administrator to the newly migrated site collection.
Post upgrade checks
- You can now go Central Admin > Upgrade and Migration > click on “Check upgrade status” under Upgrade and Patch Management. This section shows all the upgrade activities status, their timing, warnings and it will also give you the location of the upgrade log file path which is actually at the 16 Hive.
- You now view the file for the verbose logging information here with the below filename.
C:\Program files\Common Files\Microsoft Shared\Web server extensions\16\Logs\Upgrade-YYYYMMDD….guid.log and and also a file ending with -error if any.
Thank you viewing my blog.
