Chapter 2 – Upgrading to Sharepoint 2010 – Hybrid Approach

Wrox Real World Sharepoint 2010 (Page 35)

Visual Upgrade – allow user to switch look & feel back and forth between 2007 and 2010. Two options:
— preserve the user interface – use 2007 (use this!)
— upgrade to new user interface

Pre-Upgrade Checker – a STSADM extension for MOSS 2007 SP2. (better than prescan.exe of MOSS 2003) Can run on MOSS 2007 production and not changing any data.
Goal of the checker:
(1) whether your servers meet the core requirements for upgrading
(2) what currently exist insode the farm.

The STSADM command can be run from any machine in the farm. Can be run on each server to make sure configurations on all servers all are identical.

STSADM –o preupgradecheck

You can use the –localonly
switch to check only the local server.

During upgrade, twoupgrade files are created uner 12/LOGS:
Upgrade-TimeOfUpgrade……
Upgrade-TimeOfUpgrade-Error….

Database Test cmdlet —
Test-SPContentDatabase: tes a content database against a web application to verify that all customizations are also installed in the web application. Also identity missing orphans, assemblies, site definitions and features. Use this command along with pre-upgrade checker.

Database attach approach allowed upgrading multiple content databases
at the same time.

Upgrade status is also displayed on Central Administration page.

With MOSS 2007 SP2, setting MOSS 2007 read-only is now supported.

In Sharepoint Administration Toolkit, there is a Batch Site Manager
with which you can move one or more site collections between exising Content databases.

Upgrading with Custom Site Definitions —
Site definition is a blue print for newly created sites, it defines what is added to the site when it’s being created. All are defined in ONET.XML.

***** When upgrading 2007 to 2010, Micrsofot use Upgraded Definition Files (UDF) to map and transform sites from MOSS 2007 to Sharepoint 2010.

MOSS 2007 Site Definitions à UDF à Sharepoint 2010 Site Definitions

Choosing the right upgrade path —
(1) In-Place Upgrade Approach – simpler. Downtime. All in one step.
— Install Sharepoint 2010 on all your MOSS 2007 servers.
— Run Sharepoint Products Configuration Wizard on the server running Central Admin.
— Better for smaller farms (< 15 GB)

All default job are set back to the default times, so be sure to document these prior to kick off an in-place upgrade.

farm configuration wizard – (central Admin) – provide very little control over naming of services and service applications.

To upgrade texonomy data: Move-SPProfileManagedMetadataProperty
First get the ID of the new User Profile Service Application by using Get-SPServiceApplicationProxy
Update-SPProfilePhotoStore – copy user photos from 2007.

If your MOSS 2007 uses FBA, it must be converted to Claim-Based Authentication (CBA) befroe FBA will work.

(2) Database Attach Upgrade Approach — Upgrading the contents only. Good if you’re chaning the hardware too –because you’re installing Sharepoiont 2010 on a different server.
— Can upgrade miltiple content databases simultaneously. Faster.
— Sharepoint 2007 configuration settings are not upgraded, must be done manually.
— All customizations must be moved manually.
— Sharepoint 2010 environment must be built and configured prior to attaching 2007 content databases for upgrade.

if you use InfoPath forms (admin-approved form templates and data connection files), you must perform extra steps:
— Form templates (*.XSN)
— Data Connection Files (*.UDCX)

My Site è User Profile service + Managed Metadata service

Sharepoint 2010 Hybrid Upgrade
(1) – Database Read-Only; minimum downtime

— in MOSS 2007, only Content Database can be made Read-Only.
— Tmake content database in read only mode (1) make database read-only and (2) disable timer jobs.

Sharepoint 2010 Hybrid Upgrade (2) – InPlace + Database Attach
— First detach content database (so in-place upgrade doesn’t upgrade the content DB) to detach:
STSADM –o deletecontentDB –URL http://Web_Applucation_URL –databasename NameofDB

— Upgrade in-Place
— re-attach Content Database, using:
Mount-SPContentDatabase –Name DNName –DatabaseServer ServerName –WebApplication NameofWebApp
— Primary advantage – upgrade multiple databases at the same time.

You can use a temporary Sharepoint 2010 Farm to upgrade your MOSS 2007 Content Database.

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: