Sunday, April 24, 2011

SharePoint 2010 - What is the best Upgrade Practice ?


Nothing makes a grown man scream like a little kid or as bad as realizing they don’t have any backups — or even worse, realizing the backups you have cannot be restored. So the foremost thing to keep in mind is have complete set up backups for all the required.

In-Place Upgrade
The most obvious path to upgrading SharePoint 2007 to SharePoint 2010 is an in-place upgrade.
This method is the simplest, and boils down to clicking Next ➪ Next ➪ Finished. Wooho...
Congratulations, you have SharePoint 2010. But fairly speaking it is not that easy though.

When you do an in-place upgrade, you’re installing SharePoint 2010 on the same hardware as
your existing SharePoint 2007 farm, and for the most part everything stays the same. For example, URLs are the same for your users, settings are retained, custom code is still installed, customizations are still there, and application pools run as the same accounts. If you were to envision your “dream” SharePoint upgrade, this would be it.

Considerations before you go for the above approach.
1. Your hardware should support SharePoint 2010 .i.e. all servers should be Server 2008/R2 64Bit
2.SQL should have a supported version (stsadm -o preupgradecheck command can discover this).
3.Considerable amount of downtime, since the content will not be available until all the upgrade completes (Drawback here)

Database Attach
In this method you already have a SharePoint 2010 farm installed and configured. To upgrade your content, you attach a SharePoint 2007 (service pack 2 or later) content database, which SharePoint 2010 will upgrade. Sounds easy, Giv a try...

The Database attach method requires that you have separate hardware for your SharePoint 2010 farm; you cannot use your SharePoint 2007 hardware unless you remove SharePoint 2007 from all of the machines and install SharePoint 2010 on them.

Considerations for DB Attach method
1. The database attach method also usually results in different URLs for your web applications, as the corresponding SharePoint 2007 farm istypically online at the same time.
2.You have more control over the data.
3.You can attach multiple databases at the same time by opening multiple command windows provided your sql has the capacity to handle.
4.In simple > use the below set of commands in the sequence for every database that you want to attach to the new SharePoint 2010 farm

Use Test-SPContentDatabase ( Can ignore those basic errors if needed which can be fixed later)
Then Mount-SPContentDatabase to upgrade and attach the database to SP2010 Farm. In case of failure at any stage you can re-run the command Upgrade-SPContentDatabase

No comments: