Category: Upgradation from SP 2010 to 2013


There are a few improvements in the database base attach upgrade process.

1. Deferred site collections upgrade.

2. Site collections health checks.

3. Upgrade evolution site collections.

4. System event notification.

5. Logging changes.

6. Site collection upgrade throttling.

7. New Upgrade Process.

1: Deferred site collections upgrade

Allows existing 2010 site collections to work with SharePoint 2013.

Replaces the Visual upgrade

  1. The site collection upgrade process is not reversible
  2. Visual upgrade preserved only the old master pages, CSS files, and HTML files
  3. Deferred site collection upgrade preserves much more, including SharePoint Feature functionality
  4. One key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of the site (SPWeb)

Deep backward compatibility.

2:Site collections health checks

  • In SharePoint 2013 we have a few rules which run against the site collections to verify whether it is working or not.
  • Before upgrading the site collection site owner need to run site collection health checks.

You can run this using Power shell script or OOB settings.

POWERSHELL:

  • Test-SPSite -Identity <SiteURL> [-Rule <RuleID>]
  • Repair-SPSite -Identity <SiteURL> [-Rule <RuleID>]

UI:

UI for site collection Admin:

Go to Site settings under site collection administration click on Site collections health check.

site collections health check

Once we click on start checks below details list will display. Please see the below screenshot.

site collections health check Results

The above screenshot Show’s the rules.

  1. Customized files.
  2. Missing gall5. 1.1.3 Upgrade evolution site collections series.
  3. Missing site templates.
  4. Un supported Language pack references.
  5. Unsupported MUI references.

If the above screen shows any errors we need to fix the errors before migrating the site collection.

After resolving we can click to try it again and check what the results are.

3.Upgrade evolution site collections

  1. It allows upgrade preview of existing sites in 15 modes.
  2. Makes side by side copy of the existing site collection.
  3. Send an email notification when copy and upgrade is completed.

From The site settings under site collection administration click on the site collection upgrade.

Where we will get an option for a trail a demo upgrade.

Create Upgrade Evaluation site collection

From the above screenshot if we click on “Create Upgrade Evaluation site collection “ It will below confirmation message.

Create Upgrade Evaluation site collection

After completion of demo upgrade user will receive an email confirmation with URL of evolution site collection.

4: System event notification

After attaching the content Db to the respective webapplication new SharePoint 2013 Farm, whenever we open the new site collection it will show message as “Experience all that SharePoint 15 has to offer. Start now or Remind me later”.

Experience all that SharePoint 15 has to offer. Start now or Remind me later

5: Logging Changes

Logging has been changed to ULS format.

  1. TSV format allows improved parsing.
  2. Can be imported to Excel.
  3. Includes correlation ID.

Per SPSite logs available for site collection administrator.

SPSite logs

6: Site Collection upgrade Throttling

This feature prevents self service site collection upgrade. It uses the Upgrade Timer Job.

This can be achieved at three levels:

  1. Application pool level.
  2. Content DB level.
  3. Content Level.

 

We cannot go directly and start the up-gradation process. SharePoint 2013 does not support in-place upgrade for an existing environment. You must use the database-attach upgrade method to upgrade your databases to a new environment that is based on SharePoint 2013. Also, to provide more flexibility to farm administrators and site administrators, the upgrade process has changed to separate upgrade of the software and databases from upgrade of the sites.

we shall complete the up-gradation process in simple steps.

1. Planning.

2. Pre-Requisites.

3. Migration Part.

4. Upgrade Process.

Planning:

1. We need to document the complete server farm.

2. We need to document the current system i.e.  Hardware and Software Requirements.

3. Need to Estimate the space that we should have for up-gradation.

4. Need to estimate how long the upgrade process will take place.

5. Need to test the upgrade in a non production environment with a copy of production data.

6. Have a proper roll back plan and test it during trail upgrade.

7. Validate a successful upgrade by testing all components detailed in your solution documentation.

Pre-requisites:

Server Requisites:

SharePoint server :

  1. Windows server 2008 R2 SP1.
  2. No Previous versions of SharePoint.

Database server

  • SQL server 2008 R2 SP1 (X64) , or
  • SQL server 2012 (X64).

Client side Requirements:

Office 2010 or office 2013 :

SharePoint designer:

  1. SPD 2010 for 2010 mode sites.
  2. SPD 2013 for 2010 and 2013 mode site.

Take SQL server DB backup from SharePoint 2010 farm:

In our POC we are assuming that the first stage has been completed i.e. Existing farm to read only and create a new farm by installing require components for WFE, Application and Database server for SharePoint 2013.

We will start taking the SQL server DB backup from SharePoint 2010 farm (existing farm).

  1. Login to the SQL server.
  2. Open the SQL server management studio and select the database which we want to perform the backup of the database.
  3. Right click on the database and navigate to the tasks option and select the BACKUP DATABASE.
DB backup from SharePoint 2010 farm

4) Select to the backup type as Full in the dropdown list which is the default selection.

5) Select back up to option to Disk as we need to take the backup to disk.

DB backup from SharePoint 2010 farm

6) If we want to provide the specific disk path, Click on Add button to provide the disk path where backup files will get created And we will get the below browse window to provide the same.

7) Provide the path where more space is available, so that backup file of database size can be created and click ok.

DB backup from SharePoint 2010 farm

8) Select OK in the main Backup form to start the backup process. You can see the progress of the backup on the left side form. Once it is completed we will be receiving the completion message.

9) Go to Backup path which was provided during the backup process to verify and validate the same.

Perform above steps for all the databases you want to restore it in new SharePoint 2013 Farm.

Good!! Half job is done, you have taken the backup successfully from existing farm I. e. SharePoint 2010.

Now you have restored all the databases which you have taken into SharePoint 2013 .

Restore Databases in new SharePoint 2013 Farm environment:

10) Open the SQL server management studio and select the databases and select restore database.

DB backup from SharePoint 2010 farm

11) Enter the newly database name in “To database” section below and Select “From Device “option for providing the path as mentioned in the above screenshot and click on the file browser button to provide the backup the file path and we will receive the window like below.

DB backup from SharePoint 2010 farm

12) Click on add and provide the Backup file to be restored and click on OK to complete the file selection process. Select the checkbox which will be available Restore column after selecting the backup file, please check the below screenshot.

DB backup from SharePoint 2010 farm

13) Click on “Options “button available on the left side of the Restore form .Once after selecting the options page we will receive the below window.

14) Select the below option

a) Select the “overwrite the existing database” checkbox.

b) Select the first radio button available under the Recovery state and the database should be in Read and write mode as mentioned in the above screenshot.

15) Click on OK to start the restore process.

Nice, you have completed the restore.

Third Stage

Create a web application in SharePoint 2013 Farm based on existing web applications in SharePoint 2010 farm environment.

And Install all the customizations in a SharePoint 2010 farm to a SharePoint 2013 farm.

Upgrade Content Database:

Now you have to upgrade the content databases. To perform this operation you have to use powershell.

Tip: Use Start-Transcript for capturing all the details which are shown in the powershell command window.

Start-Transcript

Which will greatly help us see all the details in notepad. please check the below screenshot format, so we can analyze the details of powershell commands which we execute during migration.

Start-Transcript

We will continue the POC which we started to do upgrading content DB from SharePoint 2010 farm to a SharePoint 2013 farm. For that we will use below powershell commands.

Use “Test-SPContentDatabase” and “Mount-SPContentDatabase” to perform the upgrade activity.

Test-SPContentDatabase:

Running “Test-SPContentDatabase” is very safe, Read only and can be run very often so that we can get more information on errors and warning in that database. See the below screen where we have run the power shell command.

As a best practice try to run this command as many times as possible and try to resolve all the errors and warnings. This is the best place to resolve all the issue before attaching the content DB to web application.

Note: Never ignore any warnings.

“Test-SPContentDatabase -name “databasename” -webapplication “webapplicationname”.

Get help for “Test-SPContentDatabase” by

Get-help Test-SPContentDatabase -examples >c:\Test-SPContentDatabase.txt

Once you execute the above command you can see the syntax Test-SPContentDatabase.txt file in C drive.

After we resolve all the errors and warnings raised by “Test-SPContenDatabase” perform below step.

Mount-SPContentDatabase:

Please check below “Mount-SPContentDatabase” powershell command and its status.

Mount-SPContentDatabase

Once we complete the above powershell command content database to the respective web application.

Content Database

If there are any errors while mounting the database it will show the below message in the screenshot.

errors while mounting the database

%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\15\LOGS.

You will get two types of files with Upgrade-‘date’ and Upgrade-‘date’-error formats. You can check both of these files and see if we can if there are any issues with upgrade of content Dbs.

Upgrade log and Upgrade error log

After up gradation completed then try to open the site, you might the error in most of the cases.

How to troubleshoot issues related to migration of Content DB:

Browse the site collections which are in new SharePoint 2013 farm, most of the times we will see the error on home page of site collection because various reasons.

SharePoint 2010 error message

The above error represents the way of displaying it in SharePoint 2010 mode.

Whereas SharePoint 2013 error message will be different way display, please check the above Screenshot.

SharePoint 2013 error message

To find the errors use “Get-SPLogevent” command to find what that error is.

Get-SPLogevent -starttime (get-date).addminutes (-20) | where-object {$_.correlation -eq “28331078-c03b-48e8-b27a-1b86ef7e5ce1”} | fl message > c:\errors.txt.

The above powershell command will filter the logs for the correlation Id logs that have been generated in ULS and store it in errors.txt file in C drive.

You can use Get-help command with examples.

You can use Merge-SPLogfile command to merge the log files across the farm into a single file.

To check whether the site collection is exists or go site settings page “URL”+/_layouts/settings.aspx we will see the below similar to below screenshot.

Experience all that SharePoint 15 has to offer. Start now or Remind me later

Great now we have the migrated site from SharePoint 2010 to SharePoint 2013 farm showing in SharePoint 2010 mode.

It shows message as “Experience all that SharePoint 15 has to offer. Start now or Remind me later”.

Under the site collection administration we can see two new features “Site collection health checks” and “Site collection upgrade”.

Site collection health checks” and “Site collection upgrade

Site collection health checks:

Click on Site collection health checks to see if there are any issues with upgraded site collection.

From there click on “start checks” button.

Site collection health checks

Here in our case we don’t see any issues. So it is showing status in green color and it says “Clean bill of health”.

So, we are ready for an upgrade.

Site Collection Upgrade:

Click on site collection upgrade from the “Site collection upgrade “the below screen appears.

Site Collection Upgrade

Click on “Upgrade this Site collection”. We can try the demo upgrade as well it will create a clone of the current site collection.

Site Collection Upgrade

Click on I’m Ready from the above screenshot. It will start the site collection upgrade process.

Site Collection Upgrade

We can observe status as upgrade in Progress.

Congratulations we have upgraded the site collection successfully.

Site Collection Upgrade Status

Congratulations you have completed the up-gradation from SharePoint 2010 to SharePoint 2013.

You can status of migration from Central Administration.

status of migration from Central Administration