Hey Crash... Kindly following steps
Database Attach Upgrade
- Migration Steps
First let us take a look at the Pre-Requisites for Up-gradation Pre-RequisitesMOSS 2007 should have SP2 Installed. You should have SP2 installed on your MOSS 2007 machine. The pre-upgrade check command was added only in SP2. So if you do not have SP2 installed you will not
have the pre-upgrade check command in stsadm.SharePoint 2010 should be set up on a different server machine.
Below are the steps and their explanation
Step 1: We have to run the Pre-Upgrade check command on the MOSS
2007 server to find out if there are any issues in the SharePoint 2007 farm (like missing site definitions, features etc.).
Running the command will generate an html report for you. This report will not only notify you of any issues regarding your SharePoint farm such as missing Site Definition Information or missing Feature Information, but it also provides you with a blueprint
of your SharePoint Farm setup
Some of the details that are provided by this report are—
Search content sources and start addresses
Office Server Search topology
Servers in the current farm
SharePoint version and list of components
running in the farm
Supported upgrade types (In-place Upgrade and Content Database Attach)
Site Definition and Feature Information
Language pack information
Alternate Access Mappings (AAM) that will need to be recreated
Customized List views (these will not be upgraded)
Customized field types (these will not be upgraded)
WSS Search topology
List of Content Databases and SQL server location
Syntax: stsadm –o preupgradecheck
After you have reviewed the report and fixed any issues which might be there in your farm you can move to the next step.
At this point your database is checked for up gradation and transferred to the SharePoint 2010 farm.
Now in the next steps we will start the Upgrade process on the SharePoint 2010 farm.
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.
Now Click on O.K. to confirm
new Authenticated users
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.
PS C:\Users\MossAdmin> Test-spcontentdatabase -name Restored -webapplication htt
Output On Screen
UpgradeBlocking : False
: File [Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.d
wp] is referenced  times in the database [Restored], but i
s not installed on the current farm. Please install any featu
re/solution which contains this file.
: One or more setup files are referenced in the database [Resto
red], but are not installed on the current farm. Please insta
ll any feature or solution which contains these files.
Step 5: Run the stsadm addcontentdb command
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
PS C:\Users\MossAdmin> stsadm -o addcontentdb -url
http://moss:7000 -databasename Restored
Operation completed successfully.
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
Have to manually upgrade the customizations. 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)
–Custom Web Parts
–Custom Images (/_layouts/Images)
Add the solution to the farm solution store by using stsadm and then deployed it to web application then copy the Web Part assemblies to the GAC and added the Safe Control entries in
the web.config file of the Web Application then copy 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.