Migration from MOSS 2007 to SharePoint 2010

Migration steps from MOSS 2007 to SharePoint 2010
System Requirements
  • For migration from MOSS 2007 to SharePoint 2010 the minimum requirement is WSS SP2 and Office Server SP2 must be installed in the MOSS 2007 server. So before upgrade the content database make sure both the things are installed in the source server

Preupgrade check
  • Preupgradecheck command will let us know about the things that may restrict us to upgrade the database in SharePoint 2010 server. Before upgradation we need to fixed up all the steps which are failed in the preupgradecheck.


Backup Content Database of MOSS 2007 site
  • Before start taking backup of the database first go to the Manage Content Databases section in the Central Administration site and check the name of the database attach to your site.

Central AdministrationApplication Management->Manage Content databases


  • Open SQL Server right click on the databaseTasksBack Up
  • Click on Add button and browse to the path where you want to copy the backup file



Move the database to destination server
  • Move the backed up database to your destination database server and restore it SQL server

Restoring Content Database
  • Open SQL Server right click on Database Restore database


  • Specify a database name for restoring the database. If the specified database name is exist in the list of databases then your backed up database will overwrite it else it will create a new database and restore over it.
  • Go to the Options page and check the Overwrite the existing database checkbox



Create a blank site in destination server
  • For creating blank site in SharePoint 2010, open the Central Administration site and click on Manage web application link in the Application Management group.

Central AdministrationApplication ManagementManage web applications
  • Click on New link from the top left corner of the page


  • Enter the details of the site


  • Make the site Configurable and give the Service Account for it


  • After the Web Application is created click on Create Site Collection link for creating a blank site collection for the Web Application



  • Give service account for Primary Site Collection Administrator




Detaching Content Database
  • After the site get created go to Manage Content Database section and detach the database attached with the blank site
  • Central AdministrationApplication ManagementManage content databases

Click on the database

  • Check the Remove content database check box and click OK for the warning message


  • Click OK button and remove it


Upgrading and Attaching Content Database
  • After detaching the database attached with the blank site, our next step is to upgrade the MOSS 2007 site content Database restored in SQL Server and attach it to our blank site using PowerShell command prompt
  • Run PowerShell with Administrator privilege
  • Test –SPContentDatabase –Name [Database Name] –WebApplication [Web Application Name]
  • The above command will check the database for any references are missing in the destination server [i.e Custom Feature, Custom Webpart, Custom Site Definition etc].If any of the components are missing then deploy those to the destination server .Basically the custom components do not restrict the upgradation of the database, you can deploy this after upgradation too but it’s a good practice to deploy it before upgradation of the database.


  • Mount –SPContentDatabase –Name [Database Name] –WebApplication [Web Application name]
  • The above command will upgrade the database and attach with the site collection of the specified web application

Comments

Post a Comment

Popular posts from this blog

Auto-Generating Filenames for InfoPath Forms

Image
Auto-Generating Filenames for InfoPath Forms – I see this topic come up a LOT on forums all over the place, so instead of continuing to answer the question time and time again, I am going to post a quick blog entry showing the steps.  I think this stuff is fairly simple, but it just doesn’t pop into your head initially.  Once you see it and understand it, you’ll think it’s simple, too.  Keep in mind that I focus entirely on SharePoint-based InfoPath forms and for the most part BROWSER-ENABLED forms.  So, it’s possible and likely that all concepts explained here will work for non-browser forms and non-SharePoint forms, but just remember that my perspective is mostly browser-enabled.  The basis for this topic is that the standard method for submitting InfoPath browser-enabled forms is for the user to click Save at which point the user is prompted to give a filename along with choosing to allow overwrite.  I really dislike this feature, because users have no ...
Read more

Creating Three-state workflow in SharePoint 2010

Image
The Three-state workflow tracks the 3 states in a list to manage the business processes. Example Three states for Issue List could be Open, Resolved and Closed. Three state workflow supports to track the list item or issue through states. The workflow assigns a task to a person and sends an email to that person. When workflow is completed it updates the status of the item or issue. By default Three-state workflow works with the Issue Tracking list template. To use the Three-state workflow, you must define a list to use the workflow and it must contain some items. Two options to use the 3 state workflow Create a Issue-Tracking list which is having 3 state workflow Create a custom list to use the workflow Creating an Issue-Tracking list with 3 state workflow 1. In Team site, All site content page , click create 2. In the create dialogue, click Issue-Tracking and type a name for the list 3. Enter the description for the list as shown below Create a custom list and add a...
Read more