Continuing on the SharePoint 2013 upgrade process from previous post, we will see some considerations and commands while planning upgrading content databases to SP 2013.
When you have upgraded to SharePoint 2013 from SharePoint 2010 the sites are still in 2010 format. The sites themselves have to be updated as well.
Farm Administrators can run the command “Request-SPUgradeEvaluationSiteCollections” This creates an evaluation site collections and renders all the content in a different site collection.
The below command shows how many days the evaluation site will be stick around for evaluation.
We can push the reminder to upgrade the site collection : $weba.UpgradeReminderDelay = 5
In case if you does not want to upgrade a site collection you can disable the option to upgrade for site collections users from SP management shell.
Lets see some throttle settings at Site Collection level, which shows the ConcurrentUpgradeSessionLimit which on requirement we can either decrease or increase. If we have a small content upgrade it better to spike the limit up otherwise it will not be much help.
Throttle settings on content database upgrade
Lets see some more action while we initiate a site collection upgrade from SP management shell.
Coming to some options while running either the site collection upgrade or content database upgrade, we have options to “-Throttled” or “-Unthrottled” what unthrottling means it just upgrade everything immediately as a priority and will not put in throttling queue.
We can get the upgrade session info status by running this command “get-spsiteupgradesessioninfo -contentdatabase wss_content -showinprogress” we have other options like “-showcompleted” and “-showfailed”
we can remove a site from upgrade if its already queued to upgrade with “remove-spsiteupgradesessioninfo -identity http://intranet/sites/it”
Upgrade-SPContentDatabase WSS_Content -NoB2BSiteUpgrade -UseSnapshot
This example upgrades the existing WSS_Content content database schema only while using a snapshot of the database to retain read-only access to the content during the upgrade. No build-to-build upgrade actions are performed on any site collections. This operation does not change the CompatibilityLevel for existing site collections in this database.
We have seen some of the PowerShell help necessary for upgrading. But we need to plan and test the whole process from a staging farm before and look at the upgrade performance and plan the schedule. Once again this is purely from and SharePoint Admin perspective, later in another post we will look at other dev aspects which are key for smooth upgrade.