Step 2: Backup the content database of the Web
Application from SQL Server. Copy it to the machine where SharePoint 2010 is
installed and restore the backup of database in SQL Server using SQL Server
Management Studio. To restore the backup you will first have to create an empty
database in SQL Server and the restore your database one top of this new
Database. While restoring make sure that the Overwrite the Existing Database
option is checked (In the Options section....See image below)
At this point your database is checked for upgradation and transfered to the SharePoint 2010 farm. Now in the next steps we will start the Upgrade process on the SharePoint 2010 farm.
How
To Upgrade to SharePoint 2010 using Database Attach method: Part 2
This is a Continuation of my previous post How To Upgrade to
SharePoint 2010 using Database Attach method: Part 1 of my 2 Post series on How to Upgrade MOSS 2007 farm to
SharePoint 2010 farm using Database attach method
In my previous post we covered all the steps which were to be performed on MOSS 2007 server. In this post we will cover the steps which are to be performed on SharePoint 2010 site.
The two steps which we covered in my previous post were
Step 1: Running Pre-Upgrade check command on the MOSS 2007 server, reviewing the report generated by it and fixing any issues which might be there in the farm
Step 2: Copying the Content database from MOSS 2007 server to SharePoint 2010 server.
Now we move to the 3rd Step..
Step 3: Create a new Web Application in SharePoint 2010. Once you will create a web application a content database will be attached to it, remove the database attached to the web application via Central Administration -> Application Management -> Manage Content Databases.
Make sure that no database is attached to the Web Application which you have just created.
In my previous post we covered all the steps which were to be performed on MOSS 2007 server. In this post we will cover the steps which are to be performed on SharePoint 2010 site.
The two steps which we covered in my previous post were
Step 1: Running Pre-Upgrade check command on the MOSS 2007 server, reviewing the report generated by it and fixing any issues which might be there in the farm
Step 2: Copying the Content database from MOSS 2007 server to SharePoint 2010 server.
Now we move to the 3rd Step..
Step 3: Create a new Web Application in SharePoint 2010. Once you will create a web application a content database will be attached to it, remove the database attached to the web application via Central Administration -> Application Management -> Manage Content Databases.
Make sure that no database is attached to the Web Application which you have just created.
Step 4: Run the Test-SPContentDatabase cmdlet (PowerShell).
Running this command will check if the database is ready for upgrade or not. This will tell you about the things which are missing in this farm (E.g. Any setup files, web parts etc.). You can either attend to these missing features pre or post-upgrade but this depends on whether there are any items that will block the upgrade from proceeding.
Syntax: Test-SPContentDatabase -Name -WebApplication
Step 5: Run the stsadm addcontentdb command to add the content Database to the web application which you created. This will initiate the upgrade process as shown in the screen below
Syntax: stsadm -o addcontentdb -url -databasename
Step 6: Review the Upgrade Log file and fix the errors.
The upgrade process generates two log files. (Under 14/LOGS)
The upgrade log file which contains all the information about the upgrade
The error log file which gives you the error which occurred during the upgrade
You can review the log files and fix the errors by manually upgrading the Customizations which were there in your site
Step 7: Upgrade Customizations
You have to manually upgrade the customizations. I decided to copy the customization after doing the upgrade as none of it was blocking the upgrade. If any of your customization is blocking the upgrade you will have to upgrade the customization first and then do the upgrade.
The customizations in this upgrade included the following things
–A custom Solution (wsp)
–2 custom Web Parts
–Custom Images (/_layouts/Images)
I added the solution to the farm solution store by using stsadm and then deployed it to my web application then I copied the Web Part assemblies to the GAC and added the Safe Control entries in the web.config file of my Web Application then I copied all the images used in my Web Application to appropriate places (like /14/TEMPLATE/IMAGES)
Once you have upgraded all the customizations your upgrade is complete.
There is one more Feature about which i would like to tell you is the Visual Upgradefeature. This feature gives you an option to switch between MOSS 2007 view of your Site and SharePoint 2010 view of your site after it has been upgraded.
Since your custom themes will not be upgraded Visual upgrade gives you an option to keep the MOSS 2007 view after you have upgraded the site to buy you some time to create new themes for your SharePoint 2010 site and once you are done creating the new theme you can switch to the new SharePoint 2010 view.
Following images show how the site looked after upgrade in MOSs 2007 view and SharePoint 2010 view.
No comments:
Post a Comment