sharepoint server 2010 self-study upgrade/migration...

SharePoint Server 2010 Self-study

Upgrade/Migration Guide

SharePoint Server 2010 Self-study Upgrade/Migration Guide

2

Copyright

Information described in this document (including Internet Web site references such as URL) is subject to

change without notice. Unless otherwise noted, the names of companies, organizations, products, domains,

e-mail addresses, logos, people, places, and events described in this software and related documents are

fictitious. No association with any real name is intended or should be inferred. Complying with all applicable

copyright laws is the responsibility of the user. Microsoft may have patents, patent applications, trademarks,

copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly

provided in any written license agreement from Microsoft, the furnishing of this document does not give any

license or rights to these patents, trademarks, copyrights, or other intellectual property.

© 2010 Microsoft Corporation. All rights reserved.

SharePoint, Excel, and Internet Explorer are registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries. Company and product names described herein may be the trademarks of

respective companies.


3

Introduction

Microsoft SharePoint Server 2010 was officially released in May 2010. Many organizations are likely to

consider upgrading to the new SharePoint Server 2010.

When performing the upgrade, careful planning is required. Moreover, before performing the upgrade,

it is important to have a clear picture in mind of the process during the upgrade and the results

afterward.

This self-study guide is designed to help those considering the upgrade to understand the upgrade

options available and the processes during the upgrade so that they can perform the upgrade smoothly.

Any upgrade technique has trade-off aspects. The hope is that this self-study guide helps you to

select the most appropriate upgrade technique for the SharePoint Server environment in your

organization.

However, there are several different upgrade techniques. Depending on the existing farm

configuration, you may need to employ techniques that are not fully covered in this self-study guide.

In any case, however, the procedures involved include operating databases, restoring databases, using

Windows PowerShell scripts, and running Stsadm operations. Because the commands to be used and

the database operations are the same in all cases, we recommend that you first read this self-study

guide thoroughly to understand general upgrade cases.


4

Revision History

Version Released In Details of Changes

Version 1.0 June 2010 Initial Release


5

About Prerequisite Environment

Note: This white paper is based on the environment described below. That environment is not available

to you, but this paper still offers a detailed, graphics-rich companion to the installation and upgrade

content available on TechNet.

The prerequisite environment is one where the Active Directory environment to be evaluated and the

e-mail server have already been made available.

The prerequisite environment used to write this self-study guide is as follows:

Active Directory

Server OS: Windows Server 2008 R2 (x64)

Server name: DC2008

Server roles: AD DS, DNS

Domain name: Contoso.com

Domain function level: Windows Server 2003 Native

E-mail server


Server name: MAIL2010

Application: Microsoft Exchange Server 2010

Installation: Exchange Server standard installation (Hub, CAS, Mail Box, Exchange administrative tools)

SharePoint Server 2007 (source)


Server name: MOSS2007

SQL Server: SQL Server 2005 (x64)

SharePoint Server 2010 (destination)


Server name: SP2010

SQL Server: SQL Server 2008 R2


6


7

Contents

Introduction ................................................................................................................................................................................ 3

Revision History ........................................................................................................................................................................ 4

About Prerequisite Environment ........................................................................................................................................ 5

Chapter 1. Considering Upgrade Techniques ................................................................................................................... 8

1.1 From SharePoint Server 2007 to SharePoint Server 2010 ............................................................................... 9

1.2 Why Consider Upgrading to SharePoint Server 2010? .................................................................................. 11

1.3 Trade-off ........................................................................................................................................................................... 13

Chapter 2. Performing In-place Upgrade ......................................................................................................................... 14

2.1 Confirming the In-place Upgrade Procedure .................................................................................................... 15

2.2 Starting the Upgrade ................................................................................................................................................... 17

Chapter 3. Upgrading by Using Database Migration .................................................................................................. 46

3.1 Planning an Upgrade that uses Database Migration ...................................................................................... 47

3.2 Confirming Work Procedure for Database Migration Upgrade .................................................................. 49

3.3 Creating New 2010 Farm Environment ................................................................................................................ 52

3.4 Performing Database Migration (Preparation) .................................................................................................. 52

3.5 Database Migration (Backup Migration Data) ................................................................................................... 55

3.6 Database Migration (Restoration) .......................................................................................................................... 59

3.7 Restoring Shared Service Databases ..................................................................................................................... 69

3.8 Post-process of Database Migration ..................................................................................................................... 77


8

Chapter 1. Considering Upgrade Techniques


9

1.1 From SharePoint Server 2007 to SharePoint Server 2010

If you compare Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010, there are

no major differences in actual server topology.

A common server topology has:

A role as a front-end Web server

A role as an application server

A database server

There are, however, significant differences in their architectures, plus new software and hardware

requirements. Typical examples are shown below.

1. Only 64-bit environment provided:

SharePoint Server 2007 provided 32-bit and 64-bit versions. It was also possible to select 32-bit or

64-bit in each layer of the server topology. (32-bit and 64-bit cannot exist together in the same layer.)

However, in SharePoint Server 2010, the entire farm needs to be configured with a 64-bit OS

and applications. This presents a big challenge if the existing SharePoint Server farm is configured

with 32-bit, or if there also exists a 32-bit environment.

SharePoint Server 2010, which is optimized for 64-bit, utilizes vast memory space and provides

better performance.

2. "Shared Service Provider" abolished:

In SharePoint Server 2007, there was a "Share Service Provider". A Shared Service Provider is a

mechanism that collectively provides services that can "conveniently be used when shared." For

example, enterprise search functions, user profile functions, business data catalog applications, and

Excel Services were collectively defined and provided as shared services.

SharePoint Server 2010 provides each service as an independent "service application", instead of

providing multiple services collectively as a "shared" service. This allows for flexible redundant

configurations.

3. Internet Explorer 6 support terminated (client side):

SharePoint Server uses Web technologies. Users use SharePoint Server through Web browsers.

While various types of browsers exist, SharePoint Server 2010 requires Internet Explorer 7 or 8 or 9

to benefit from more versatile Web technologies.


10

You can determine what upgrade techniques to employ by considering your present SharePoint

Server farm environment and the requirements of your organization in order to narrow down the

choices. The two techniques introduced by Microsoft in TechNet are as follows.

(TechNet article: Determine upgrade approach (SharePoint Server 2010))

Technique Description

In-place upgrade This technique is supported if the existing farm is configured

for 64-bit. However, your environment must satisfy the

minimum requirements, such as OS version upgrades,

additional component upgrades, and new hardware

requirements for SharePoint Server 2010.

Database migration This backs up databases capable of being migrated and

transfers them to new environments.

If a certain amount of downtime is tolerable, database

migration will be the smoothest means of updating to

SharePoint Server 2010. Note, however, that not all settings

and databases can be migrated.

This self-study guide introduces both techniques, namely in-place upgrade and database migration.

Tips: Office Upgrade from SharePoint Portal Server 2003 to SharePoint Server 2010

It is not possible to upgrade Office SharePoint Portal Server 2003 directly to Microsoft SharePoint

Server 2010. When considering migration from 2003 to 2010, you should note that the differences in

versions and hardware requirements are so great that in-place upgrade is not possible even if you use

the database migration method.

First upgrade the contents to Office SharePoint Server 2007, and then you can upgrade to SharePoint

Server 2010.

MSDN article: Upgrade from SharePoint Portal Server 2003 to SharePoint Server 2010

http://technet.microsoft.com/en-us/library/cc263447.aspx

http://msdn.microsoft.com/en-us/library/ee947141.aspx


11

1.2 Why Consider Upgrading to SharePoint Server 2010?

It takes considerable effort, cost, and time to upgrade applications that are currently running steadily.

If you are currently using SharePoint Server 2007 and it is running without any problem, why should you

consider upgrading to SharePoint Server 2010?

A comparison of SharePoint Server 2007 and SharePoint Server reveals the following improvements.

Support for rich contents besides documents and Web

SharePoint Server previously shared and managed such things as document contents, Web pages, list

data and external databases. SharePoint Server 2010 can manage rich media such as movie contents

and Silverlight contents in addition to the aforementioned, thus providing richer experiences to end-users.

Improved usability

SharePoint Server 2010 adopts the "Fluent UI" (the ribbon) that is used in Office products. This allows

users to comfortably use local client applications such as Office products and server products from

the same UI. Additionally, this fluent UI is a dynamic UI. Its contents change according to the context

of user operations. In some places, a live preview function is also available. Before fully applying

settings, you can check the expected results in real-time (simply by pointing the mouse cursor).

Furthermore, the methods of uploading and placing files have also improved. The AJAX-based UI has

no screen transitions and therefore puts users at ease. If the URLs and screens change constantly in

response to your operations, you could become unsure of what you have been doing and how you

can go back. SharePoint Server 2010, however, is intuitive and free from such problems.

High reliability and redundancy, and availability of techniques

In SharePoint Server 2010, the Shared Service Provider has been abolished and instead, individual

services are provided in independent forms. Even services that until now were impossible to make

redundant can now become redundant in multiple servers.

The place known as "single point," where redundancy was impossible, has been abolished.

Furthermore, it has become more resistant to failures and now supports as standard the "mirroring"

provided by Microsoft SQL Server 2008. This makes it possible to use solutions that can be built at

relatively low cost, while minimizing downtime during failures.

As a method of preventing disks from bloating, it conducts more advanced capacity controls such as

using binary large objects (BLOBs) and works well with storage peripheral products provided by other

manufacturers.


12

High compatibility with Office 2010 Client products

SharePoint Server 2010 maintains a high degree of affinity with Office 2010 client applications. Office

2010 now introduces SharePoint Workspace 2010 to enable the secure, efficient and off-line use of

SharePoint Server 2010 contents.

Moreover, SharePoint Designer 2010 is provided free of charge.

SharePoint Designer 2010 not only brushes up the visible design of your sites, but also provides

advanced administrative tool features, including creation of your own workflows and effective

management of users, to enable centralized management of SharePoint Server 2010. It also allows you

to create collaborative connectors for external lists, thus simplifying database collaborations.

There is now greater affinity with mobile devices. It is also possible to provide views specifically for

mobile devices and customize them.

SharePoint Server is used primarily by end-users, and most of the time it is used for their tasks. The

improved usability of SharePoint Server 2010 will no doubt increase the users' productivity and comfort.

There are still other reasons for you to consider upgrading. Why not create an environment yourself to

evaluate SharePoint Server 2010?


13

1.3 Trade-off

By upgrading, IT administrators, developers, end-users, and people of all positions can make use of the

latest technology and increase their productivity. However, the upgrade should be carried out with care

and good planning. Trade-off issues that might result from the upgrade must also be taken into

consideration.

Before upgrading to SharePoint Server 2010, consider the following issues.

Only 64-bit version provided

While SharePoint Server 2007 was provided in both 32-bit and 64-bit versions, SharePoint Server 2010

is provided only as a 64-bit version. If you are using the 32-bit version at present, you need to prepare

a new farm (even if just for a while).

Re-development of extended functions accompanying the new version

Organization-specific functions developed for the 32-bit version might require minor changes to

become compatible with the 64-bit version. Moreover, when you migrate the 32-bit environment to a

64-bit environment, a considerable amount of time might be required to conduct verification tests

throughout the farm to make sure that existing solutions run properly.

Occurrence of downtime

Whether carrying out an in-place upgrade or database migration, a certain amount of downtime will

occur. If critical tasks are being performed on SharePoint Server, you will have to plan carefully

regarding when to perform the upgrade.

Support for Internet Explorer 6 terminated

Many organizations use Internet Explorer 6. SharePoint Server 2010 does not support Internet

Explorer 6, and any attempt to display it will result in a broken layout together with a warning and

incorrect display of ribbon UIs, etc.

It could be difficult to upgrade if Internet Explorer 6 is used by other applications within the

organization.

In some cases, however, "Microsoft Certified Partner" enterprises that are well acquainted with

SharePoint technologies may provide solutions that display SharePoint Server 2010 drawings correctly

in Internet Explorer 6.


14

Chapter 2. Performing In-place Upgrade


15

2.1 Confirming the In-place Upgrade Procedure

Because in-place upgrade can pass virtually any contents from the current SharePoint Server 2007

environment to a new environment, this is the best method to ensure smooth and user-friendly

migration to new environments, provided that the current server farm meets the SharePoint Server

2010 installation requirements.

Before performing an in-place upgrade, confirm that the present farm environment is eligible for

in-place upgrade.

Items to confirm Check ✔

Within the farm, all servers run on Windows Server 2003 or 2008 64-bit OS, and

the 64-bit version of SharePoint Server 2007 is running

SQL Server 2005 or 2008 64-bit version is used as a database server for

SharePoint Server 2007

All servers within the farm that are running on SharePoint Server 2007 meet the

hardware specifications required for SharePoint Server 2010 or SQL Server 2008

You can reserve the required work time for a bulk upgrade operation

Backups are maintained for all data

If the conditions listed above are met, in-place upgrade is possible.

First, let us confirm the procedure for the in-place upgrade. The following procedure assumes that the

present environment is configured with Windows Server 2003 (64-bit) and uses SQL Server 2005 (64-bit).

If the SharePoint Server 2007 environment has been configured with Windows Server 2008, SQL Server

2008, etc., start by applying Service Pack 2 (SP2) to the SharePoint Server 2007.

From Windows Server 2003 to Windows Server 2008

Prepare environment for SQL Server 2005 (applying SP3 and CU2)

Apply SP2 to SharePoint Server 2007

Perform upgrade check


16

Temporarily remove functions and plug-ins that interfere with upgrade (optional)

Launch SharePoint Server 2010 installer (splash.hta)

Prepare prerequisite components for SharePoint Server 2010 installation

Install SharePoint Server 2010

Stop various SharePoint Server 2007 services

Start internal upgrade

Visual upgrade

Overall post-upgrade verification

Reset necessary sections

SharePoint Server 2010 upgrade completed


17

2.2 Starting the Upgrade

Before performing an in-place upgrade, make sure that the existing SharePoint Server environment is

up-to-date. To perform an in-place upgrade, the latest SharePoint Server 2007 and SQL Server software

patches must have been applied.

Specifically, the following conditions must be met.

Windows Server 2003 SP2 applied

SharePoint Server 2007 SP2 applied

SQL Server SQL Server 2005 SP3 and CU2 applied

This self-study guide introduces an in-place upgrade based on the assumption that SharePoint Server

2007 SP2 has been installed on Windows Server 2003 SP2 x64 server OS and SQL Server 2005 SP3

x64. If SP2 is not applied in the current SharePoint Server environment, be sure to apply SharePoint

Server 2007 Service Pack 2 before upgrading the OS. For information on applying SP2, see TechNet

article: Deploy software updates for Office SharePoint Server 2007.

Before the upgrade, SharePoint Server 2007 has the following sites.

Top site: http://moss2007

http://technet.microsoft.com/en-us/library/cc263467(office.12).aspx

http://technet.microsoft.com/en-us/library/cc263467(office.12).aspx


18

Human resources portal: http://moss2007/hr

Contents include "What's New", "Links", "Shared Documents", "Reimbursement Library", etc.

Example: Inside Shared Documents


19

1. Upgrade Windows Server 2003 SP2 x64 to Windows Server 2008 R2.

Tip: When selecting an OS, you need to consider whether to use Windows Server 2008 x64 or

Windows Server 2008 R2; you should use Windows Server 2008 R2 if at all possible.

(See KB962935: http://support.microsoft.com/kb/962935/en-us)

During the upgrade, the SharePoint Server search services must be stopped. In the case of

SharePoint Server 2007, there are two types of search services. Both need to be stopped.

From the Start menu, select Administrative Tools. Click Services.

From the list of Services, stop and disable Windows SharePoint Services Search and Office

SharePoint Server Search.

http://support.microsoft.com/kb/962935/en-us


20

Temporarily disable the search service, which is currently set to Automatic in Startup type. Switch

the setting to Disabled, click Apply, and then click Stop.

2. Insert the Windows Server 2008 R2 media. Click Install now.


21

Tip: Note the Windows edition.

The Windows edition can be upgraded only within the same edition.

This means that the 2003 Standard edition cannot be upgraded and installed to a different

license edition, such as 2008 Enterprise, and that the installer will stop the upgrade process as soon

as it determines the edition. When changing the edition, a new installation is required.

Select Upgrade from Which type of installation do you want?

Confirm in Compatibility Report that Office SharePoint Server 2007 functions will be disabled,

and click Next.

The OS will be restarted several times during the upgrade, after which the upgrade will be complete.


22

3. Confirm that the OS upgrade has been successful.


23

4. Re-enable SharePoint Server 2007.

Restore SharePoint Server 2007, which was disabled by the OS upgrade.

From the Start menu, select Control Panel. Click Programs and Features.

From Uninstall or change a program, select Microsoft Office SharePoint Server 2007 and click

Change.


24

Select Repair and click Continue.

When this has been restored, click Close.


25

5. Restart. Select Yes to restart immediately.

6. Launch the SharePoint Products and Technologies Configuration Wizard, and then click Next.


26

7. On the Modify server farm Settings, select Do not disconnect from this server farm, and then

click Next.

Confirm the settings for the SharePoint Central Administration Web applications.

Select No, this machine will continue to host the web site, and then click Next.


27

On Configuration Successful, click Finish.

.

8. After clicking Finish, the SharePoint Central Administration page opens.


28

9. Make sure that the SharePoint Server 2007 site starts up successfully.

The OS has now been upgraded to Windows Server 2008 R2, and the reconfiguration of SharePoint

Server 2007, which was stopped during the upgrade, has been completed.

Tips: Points to consider regarding the OS upgrade are summarized below.

Make sure that the Windows editions before and after the upgrade match

Make sure to apply SP2 to SharePoint Server 2007

* SharePoint Server 2007 SP1 or later supports Windows Server 2008, and SP2 or later supports

Windows Server 2008 R2.

To upgrade to SharePoint Server 2010, whether you select Windows Server 2008 or Windows

Server 2008 R2, SharePoint Server 2007 SP2 must be applied in advance.


29

10. Apply software patches to SQL Server 2005 SP3.

(If you are using SQL Server 2008, apply SP1 and CU2 or later.)

While SQL Server 2005 x64 SP3 can be used as it is, the latest Hotfix (CU3) must be applied.


The "SQL Server 2005 Service Pack 3 Cumulative Update Program Package 3" contains three hotfixes.

Accept the terms for the HotFix, enter your e-mail address, and submit the request.

Add Windows Server features (Windows PowerShell, Desktop Experience)

Run the SharePoint Server 2010 advance preparation tools

Apply Windows Server 2008 R2 WCF HotFix



30

11. Run "Preupgradecheck," which is a prerequisite to installing SharePoint Server 2010.

From the Start menu, click Run. Enter "cmd" to display the command prompt.

Execute STSADM.exe.

cd c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

stsadm.exe -o Preupgradecheck

A SharePoint Products and Technologies Pre-upgrade Check Report will be output. Confirm

that there are no errors in the report.


31

Tip: By default, when there are multiple servers within a farm, this command will create a report for

the entire farm. However, you can also execute it on each server to create reports. (local execution)

If any error occurs, the report will be marked as "Failed" as shown below.

If a solution to the problem is available, the link to this solution will appear.

12. Before installing SharePoint Server 2010, stop any SharePoint Server services.

From the Start menu, select Administrative Tools and click Services.


32

13. Stop all services whose names begin with "Windows SharePoint Services," as well as Office

SharePoint Server Search.

Make sure that all services related to SharePoint technologies have been stopped.


33

14. Before performing an in-place upgrade to SharePoint Server 2010, install the prerequisite software

components.

Insert SharePoint Server 2010 media into the server.

15. Click Install software prerequisites to launch it. To use this tool, a "connection to the Internet"

is required.


34

16. Accept the License Terms and proceed.

After configuring IIS and installing the required programs, restart.


35

17. Confirm that the software prerequisites have been completed, and click Finish.

18. Before starting the SharePoint Server 2010 installation, back up current data.

* At this point, no changes have been made to SharePoint Server 2007.

From Central Administration, select Backup and Restore.


36

Select the entire Farm and obtain the backup.

The backup files should be moved to a different environment that will not be affected.

19. Begin the installation of SharePoint Server 2010. Open the installation media, and run "Setup.exe".

Enter the product key of the full version, and click Continue.

Accept the License Terms. Click Continue.


37

Upgrade earlier versions appears. Click Install Now.

Tip: The only available option is Install Now. While the earlier versions provided a "Gradual

Upgrade" option, SharePoint Server 2010 only provides in-place upgrade (bulk upgrade). This

means that if you decide to perform an in-place upgrade, you must perform a similar upgrade for

all servers within the farm. This might make in-place upgrade an unrealistic option for large-scale

farms. In such cases, you can choose database migration or a hybrid method (this method

gradually and temporarily makes the databases read-only to allow access only, while continuing

the database migration upgrade from backup databases to a new farm).


38

20. The installation of SharePoint Server 2010 begins.

21. After installation, make sure that the Run the SharePoint Products Configuration Wizard now

check box is selected, and click Close.


39

22. The product configuration wizard for upgrade from SharePoint Server 2007 to SharePoint Server

2010 is launched.

23. Enter your pass phrase for the farm security.

This self-study guide assumes that you will enter "P@ssw0rd".


40

24. Select Visual Upgrade. When upgrading from SharePoint Server 2007, you can choose whether to

use the new SharePoint Server 2010 fluent UI (the ribbon) or to maintain the UI of the existing

SharePoint Server 2007. Note that this setting can be changed later.

Select Preserve the look and feel of existing SharePoint sites, and allow end users to update

their sites' user experience, and click Next.

Make sure that all processes have been completed.

The SharePoint timer job will then continue the upgrade process.


41

25. The SharePoint Server 2010 Central Administration site opens.

The termination of the upgrade configuration wizard triggers the installation of various new

functions and services. Meanwhile, a script for database upgrade is created in the background

based on various information contained in the configuration database.

Based on this, the individual content databases and service databases will be upgraded.

These upgrade processes are performed through a timer job.

The progress of the upgrade made by the timer job is displayed. The progress status is

automatically updated every minute, and finally "Successful" is displayed.

Note:

The upgrade process may take anywhere from tens of minutes to several hours, depending

on the scale of the farm and the databases. Do not operate SharePoint Server 2010 while the

upgrade is in progress.

Note that the upgrade is incomplete until "Successful" is displayed.


42

26. Confirm that all upgrade jobs have finished.

Tips:

In some cases, the upgrade timer job is marked as "Failed" in red.

In case of failure, check the log. Correct the problematic parts, and run the configuration wizard again.

Moreover, since the timer job for upgrade tries to configure services based on the Shared Service

Provider that was abolished by SharePoint Server 2010, depending on the environment, some of

the services might fail to start successfully and therefore end up being marked as having "Failed."

When that happens, one option may be to configure the remainder manually, but this depends on

how far along the configuration of SharePoint Server 2010 was when the error occurred.


43

27. After all update processes have been completed, start up the site to confirm.

Click Site Actions in the top right corner to verify that the SharePoint Server 2010 upgrade has

been completed.

28. Use Visual Upgrade to change the UI.

From Site Actions click Visual Upgrade.


44

29. When the Title, Description, and Icon window opens, select the Visual Upgrade.

Select Preview the updated user interface, and then click OK.

30. Confirm that the display is in the SharePoint Server 2010 UI.

At the top, a warning regarding the UI is displayed in a yellow strip. If the UI is displayed correctly,

the warning is no longer needed. Therefore, click View or modify this site's Visual Upgrade

settings in the yellow strip, and select Update the user interface.


45

Tip: Significance of visual upgrade

Visual upgrade functions are available only when you upgrade from SharePoint Server 2007 or

earlier versions of SharePoint Server. Although the Visual Upgrade menu is displayed when newly

installing SharePoint Server 2010, this menu cannot be used.

The visual upgrade was provided, not to continue using legacy UI, but to allow uninterrupted

operations until verifying the existing UI in new environments. This is necessary, because severely

damaged layout makes it difficult to continue operations on SharePoint Server.

Using the visual upgrade function provides organizations with time to modify their master pages,

CSS and functions in line with the 2010 UI.

Can organizations use visual upgrade to go on using the 2007 UI indefinitely? No; there are many

functions that can only be used with the new UI. In particular, functions related to page editing

cannot be fully used unless the change to the new UI is made. Use visual upgrade only as a

temporary solution.

31. Reconfirm all settings. The following are examples of items to be confirmed.

Whether the settings of the outgoing mail server and the incoming mail server have been

correctly passed on

Whether user profiles have been migrated

Whether searches can be performed successfully

Whether all sites are accessible

Whether access rights have been correctly reflected


46

Chapter 3. Upgrading by Using Database Migration


47

3.1 Planning an Upgrade that uses Database Migration

SharePoint technologies store all content data in SQL Server databases.

This makes it possible to upgrade to SharePoint Server 2010 by creating and recovering database

backups. This method supports cases where there are multiple content databases.

This technique can also be used when upgrading from a 32-bit environment to a 64-bit environment.

There are, however, some points to consider before starting a database migration.

First of all, can database migration restore "all" information maintained by the existing SharePoint

Server 2007 farm?

TechNet summarizes the advantages and disadvantages as follows. Important points are emphasized in bold.

Method Description Advantage Disadvantage

In-place

upgrade

SharePoint Server 2010

can be installed in the

same hardware. Server

farm contents and

settings can also be

upgraded as a part of the

same process.

Farm-wide settings

are preserved and

upgraded. While the

customization is valid

in the post-upgrade

environment, manual

operations might be

required, for instance,

to upgrade and

reactivate customized

sections.

While the upgrade is in

progress, the servers and

farms will be offline.

The upgrade proceeds

continuously. Therefore, you

must allocate enough time

for all contents to be

upgraded in sequence.

Database

connection

upgrade

You can upgrade the

contents of the

environment in a

separate farm. As a

result of this, you do not

upgrade any of the

services or farm settings.

You can upgrade the

databases in any order

and upgrade several

databases at the same

time. While upgrading

the databases, users

cannot use their

contents.

You can upgrade

multiple content

databases at the same

time, which results in

faster upgrade times

overall than an

in-place upgrade.

You can use a database

attach upgrade to

combine multiple farms

into one farm.

The server and farm settings

are not upgraded. You must

manually transfer settings

that you want to preserve

from the old farm to the new

farm. Any customizations must

also be transferred to the new

farm manually. Any missing

customizations may cause

unintended losses of

functionality or user experience

issues. Copying databases over

a network takes time and

bandwidth. You must plan for

that. You need direct access to

the database servers.




48

Characteristics of the database migration upgrade are summarized below.

The contents of a content database that are purposed only to attach databases will be maintained

without being lost. However, since the destination is a new environment, various settings stored in the

configuration database will not be passed on. Basically, only the contents are passed on.

Not all databases and data maintained in SharePoint Server 2007 can be migrated.

Example: configuration databases, etc. (The new farm has different configuration information, and

each service is turned into an "application.")

*Significant changes have been made to the architecture.

In an environment that was not operated using alternative access mapping, the URL might change.

Since the destination is a new server farm (new SharePoint Server 2010 farm), server names and Web

application URLs might change if alternative access mapping was not used and server names

themselves were used as access URLs.

Knowledge of the database is required to operate databases directly.

Databases and service applications must be connected manually by using Windows PowerShell.

Anything that totally cannot be migrated from 2007 requires resetting the services and recreating

information.

Databases or data that can be migrated are as follows.

Content databases (to which multiple content databases can be attached)

Content databases created for My Site

Data in databases for Shared Service Providers

(Applicable to partial information only, as there are no shared services in SharePoint Server 2010)

Databases for Single Sign-On


49

3.2 Confirming Work Procedure for Database Migration Upgrade

Before you begin data migration, you should understand the process.

Blue boxes indicate tasks that must performed during the SharePoint Server 2007 stage. Not all tasks

are mandatory, so perform these as required.

Red boxes indicate procedures for migration to SharePoint Server 2010.

Command to use:

Upgrade check STSADM.EXE -o Preupgradecheck

(This command cannot be executed if SP2 has not been applied)

Environment cleanup Deleting unused sites

STSADM.EXE -o Deletesite

STSADM.EXE -o Deleteweb

Deleting unnecessary old files created by the version administration function

Execute the command manually, or by using an application developed for

this purpose

Apply SP2 to SharePoint Server 2007

Perform a pre-upgrade check

Clean up the existing environment (slimming the database)

Note connections between all Web applications and

corresponding content databases


50


51

Create SharePoint Server 2010 farm

Start minimum services

Configure minimum settings for the SharePoint Server 2010 farm (e.g. mail settings)

Create Web applications (corresponding to what existed in the previous environment)

Create backups of SharePoint Server 2007 databases

Verify custom components

Restore content databases (to the Web applications)

Upgrade the SSP database to configure user profiles

Upgrade My Site Web sites

Restore remaining databases

Create search indexes for use in the new environment


52

3.3 Creating New 2010 Farm Environment

In order to perform database migration, a new farm that suits database migration has to be created

beforehand. For information on the installation task itself, refer to the SharePoint Server 2010 Self-study

Installation Guide (http://go.microsoft.com/fwlink/p/?LinkId=227467).

For more information on creating an environment that suits database migration, refer to the following

TechNet article.

Prepare the new SharePoint Server 2010 environment for a database attach upgrade

3.4 Performing Database Migration (Preparation)

This section describes a database migration from an environment that has SharePoint Server 2007 and

SQL Server 2005 installed, and that has a farm configuration with the server name "MOSS2007".

The destination of migration is the new SharePoint Server 2010 farm that has been created in the

separate "SharePoint Server 2010 Self-study Installation Guide".

However, the "Farm Function Preparation Wizard" that follows the "Configuration Wizard" used

in the self-study guide has been "cancelled".

1. Run "Preupgradecheck", which is a prerequisite to installing SharePoint Server 2010.

From the Start menu, click Run. Enter "cmd" to display the command prompt.

Execute STSADM.exe.


stsadm.exe -o Preupgradecheck

http://go.microsoft.com/fwlink/p/?LinkId=227467

http://go.microsoft.com/fwlink/p/?LinkId=227467



53

A Pre-Upgrade check Report will be output. Confirm that there are no errors in the report.

2. Check the list of sites for any unnecessary SharePoint Server 2007 site.

In SharePoint Server 2007, execute the STSADM.exe command.


STSADM.exe -o enumallwebs -databasename <database name>


54

The list of sites within the WSS_Content database appears as shown above.

You might find, however, that the display in the command line is difficult to read.

You can output the list of sites into a file.

For example: STSADM.exe -o enumallwebs -databasename wss_content >c:\SiteList.xml

Open the output file using an application that can neatly display XML, such as Excel 2010.

If necessary, delete unnecessary sites based on the list.


55

3.5 Database Migration (Backup Migration Data)

1. Disconnect content databases from SharePoint Server 2007.

On Central Administration, select Content Databases from Application Management. Select a

target Web application on the right-hand and confirm the content database.

Click the database name and open it.

Select Remove content database and then click OK.


56

A warning appears. Click OK. Deleting a content database only means disconnecting a relationship

with SharePoint Server; the database itself will not be deleted from the computer that is running SQL

Server.

2. After the disconnection, backup the database from the SQL Server used in SharePoint Server 2007.

From the Start menu, click All Programs - Microsoft SQL Server 2005 - SQL Server Management

Studio.

Enter "MOSS2007" in the Server name box, select Database Engine, and click Connect.


57

3. Expand Database and select the target database.

This self-study guide backs up the following databases maintained in SharePoint Server 2007.

* Database names will vary depending on the environment. The following example shows names that

an administrator provided when creating the content database. (The default is

WSS_Content_xxxxxxxxxxxxxx)

WSS_Content Content Database 1 (contains one site)

WSS_Content_01 Content Database 1 (contains one site)

WSS?Content_PersonalSites Content databases for personal sites

SharedServices1_DB Shared service database

4. Obtain backups of the databases.

Right-click the target database to display the menu.

From Tasks, select the Back Up command.


58

5. Select the content of the backup and its destination.

Database: WSS_Content (example)

Backup type: Full

Destination: After you select any folder, click OK. Confirm that the backup file exists in the specified

folder.

In a similar procedure, back up any content databases and shared service provider databases that you

plan to use.


59

3.6 Database Migration (Restoration)

Create a Web application and content database in order to restore backup data in SharePoint Server 2010.

1. From the Start menu, select All Programs, and select SharePoint Server Central Administration

under Microsoft Office SharePoint 2010 Products.

In the Quick Launch, click Application Management. Select Web Applications Management, and

click New on the ribbon.

Create a new Web application.

Configure the Web application by using the same conditions as used previously in SharePoint Server 2007.

This example uses "Classic Mode Authentification" and port 80 for Web sites.

* If such methods as form authentication were used in the 2007 version, you need to separately set

claim authentication for SharePoint Server 2010 beforehand. Refer to Configure forms-based

authentication for a claims-based Web application (SharePoint Server 2010) on TechNet for details.

http://technet.microsoft.com/en-us/library/ee806890.aspx

http://technet.microsoft.com/en-us/library/ee806890.aspx


60

Since the databases created here will be overwritten later, you can give them any name. However, to

maintain simplicity, we recommend you use names that are similar to those that you used in

SharePoint Server 2007.

2. In the Databases section, click Manage content databases.


61

3. Repeat Add a content database as many times as the number of databases to restore.

Having database names that are similar to the backup databases will make the restoration simpler.

At this point, restore the "content database" only. At this point, do not restore content

databases for personal sites or databases for Shared Service Provider.

4. In the Remove Content Database section, select the Remove content database check box, and

click OK.


62

5. Launch SQL Server Management Studio in the environment where SharePoint Server 2010 has been

installed.

Select Database Engine, SP2010 (SharePoint Server 2010 environment), and click Connect.


63

6. Right-click Databases to display the menu.

Select Restore Database.

7. From the Restore Database window, open the To database list. Select the target database.

Select From device as the restoration resource and specify the backed up files. (The backup files

should be moved to the default backup folder for SQL Server databases in advance.)


64

8. Confirm the destination and method of restoration.

To database: e.g. WSS_Content

To a point in time: Most recent possible

Backup sets to restore: WSS_Content-Full Database Backup

Select Options from the left pane.

Select Overwrite the existing database, and then click OK.


65

9. Confirm that the database has been restored correctly, and then click OK.

Restore by overwriting any content databases other than personal sites and shared services.

Tip: If the "Database is in use. Could not obtain exclusive access" error appears while restoring a

database and the restoration fails, stop the environment once. (Especially when SharePoint Server

and SQL Server are in the same environment)

However, stopping the service will cause some related services to stop, so it is important to take

caution when you do so and determine the appropriate timing.

Stop the following two services and stop the SharePoint Server running environment.

IIS Admin Service

SharePoint 2010 Timer

After restoring databases, be sure to start the above services that you have stopped.


66

10. Verify the restored content database. Some site collections and sites stored in the content databases

might require enhanced functions. In such cases, you must prepare and ensure operation of the

enhanced functions in the new SharePoint Server 2010. You need to carefully examine whether such

sites are not included before connecting the databases to SharePoint Server.

Launch Windows PowerShell (SharePoint 2010 management shell) within SharePoint Server 2010.

Execute the following command:

Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>

If there is no problem, nothing appears and the control returns to the command prompt.

Tip: If no enhancement was used when using the 2007 version, you can skip this step. However, we

request that you perform this step for the sake of confirmation. This useful command can be used

with both 2007 databases to which 2007 SP2 has been applied, as well as 2010 databases. This

mitigates the risk of connection failure when connecting the databases to SharePoint Server.

11. Consideration before connecting content databases to a Web application in the new farm

(Important)

When multiple content databases exist for a Web application and you want to connect those

content databases, you must first connect the content database that contains the "root site"

for the Web application 2007 version. You must not make an error in this step.

Before you carry out this step, verify which content database contains the root site for the Web

application that you are going to restore. After connecting a database that contains the root site, you

can connect other content databases for that Web application in any order.

Moreover, there is no need to create a site collection to store the contents prior to connecting

databases. The site collection will be created in the new environment during the database connection

process.

Therefore, never add new site collections to the new environment until all content databases

have been restored.


67

12. Connect content databases to the Web application. Launch SharePoint Management Shell (Windows

PowerShell).

Execute the following command.

Mount-SPContentDatabase -Name <name of restored database> -DatabaseServer <name of

database server> -WebApplication <URL of destination Web application>

Tip: Executing a MOUNT command to connect the database to the Web application will result in

upgrading database contents from 2007 to 2010 format. The progress of the upgrade process is

displayed real-time from 0-100%.

Any attempt to connect very large databases can cause errors that prevent successful termination.

Many errors are caused by process timeout. To prevent timeout, it is important to streamline

databases as much as possible before connecting them.

In addition, communication with the destination SQL Server can cause problems. You need to prepare

and execute an environment equipped with optimum bandwidth. To execute the above command,

administrator permissions for the local server are required.

Administrator permissions for the SharePoint Server farm are also required.


68

13. Check the behavior. Start the specified http://SP2010 site with the browser to confirm that it has

been upgraded.

14. Depending on your needs, you can configure a visual upgrade and select either the SharePoint

Server 2007 UI or SharePoint Server 2010 UI.


69

3.7 Restoring Shared Service Databases

By this point, the content databases should have been restored and users should be able to use sites

and their contents that they previously used in the 2007 environment. The next thing to be restored is

the user profile information within the shared services. The prerequisite to perform this task is that User

Profile Service has not been invoked in the SharePoint Server 2010 environment. If you want to use

wizards such as the farm advance preparation wizard, exclude User Profile Service from the target of the

wizard. (Clear the checkbox.)

1. Create an application pool for the User Profile Service.

Launch "SharePoint Management Shell" (Windows PowerShell).


New-SPServiceApplicationPool -Name <application pool name> -Account <domain\user name>


70

2. Start the Managed Metadata Service. Some information included in the User Profile is stored in the

Managed Metadata Service.

Open Central Administration, and open Application Management.

Open the Manage service on server, select the service, and click Start.


71

3. Restore service provider databases.

Open SQL Server Management Studio. Right-click Databases to restore databases.

In the Destination Database column, enter the database name. Next, restore data from the backup file.

4. Upgrade the shared service databases.

Open the "SharePoint Management Shell."


New-SPProfileServiceApplication -applicationpool <application pool name> -Name <service

application name> -Profiledbname <restored SSP database name> [-Profiledbserver <database

server name>]

Note the displayed ID, as it will be required later.


72

5. Create the service proxy.

Start the "SharePoint Management Shell" and execute the following command.

New-SPProfileServiceApplicationProxy -ServiceApplication <insert the ID copied earlier> -Name

<service proxy name> -DefaultProxyGroup

6. You can also check this from the Central Administration.

* Service applications and proxies can also be created in the GUI, but because of the upgrade process

for the Shared Service Provider databases, we recommend that you use Windows PowerShell for the

operations up to this point.


73

7. Grant permissions to the User Profile Service. After adding service accounts, grant "Full Control"

permission. In this section, add Contoso\spfarm account with administration permissions.

8. Start the User Profile Synchronization Service.

Click Manage services on server from Application Management to display the list of services.


74

It will take some time for these to fully start. Refresh the browser periodically (F5) and confirm that it

has been started.

At this point, be sure to "restart".

After restarting, verify that the Forefront Identity Manager services (two services) are marked as "Started".

9. Open the User Profile Service application that you have created and define settings for personal sites.

If an error occurs when you open the application, try again after a while.


75

10. Create a site collection to store personal sites.

If you click Create Site Collection for the personal site host within the specification of the "Personal

Site" location, which is one of the User Profile Service application items, the Web application will be

automatically set up.

Specify the URL to create it.

11. Now that a database for personal sites is ready, open SQL Server Management Studio and restore

databases by overwriting, using the same technique that you used when restoring the content

databases.

This migrates personal site information and profile information.


76

12. Restore the rest of the databases. Tasks to be performed hereafter depend on what SharePoint Server

functions your organization has been using.

If your organization has been using SharePoint Server 2007 Enterprise, perform the remaining tasks,

such as setting up a Single Sign-on Service (optional) and upgrading the URL for InfoPath Form

Services.

Refer to TechNet articles for details: Perform post-upgrade steps for a database attach upgrade

(SharePoint Server 2010)




77

3.8 Post-process of Database Migration

Restoring farm configurations using database migration can be done within a short time, and many

organizations might adopt this method. Basically, all you have to do is to make backups (copies) of the

database that contains the contents and restore them in the new environment.

Once the contents have been restored, what's next?

Unlike the in-place upgrade, database migration does not pass on "various settings".

It is only that data is attached to the "new farm"; you have to reconfigure the new farm to the extent

that it becomes operational.

Principally, settings such as the following are required.

When all contents are in place, configure the search function and create the index.

Determine the range for content crawls.

Enforce index server redundancy if needed.

Establish a link to existing application groups.

(Optional) Install Microsoft FAST Search Server 2010 for SharePoint.

Review the BCS settings.

SharePoint Server 2007 had an XML definition for the external data connection called the BDC

(Business Data Catalog), which has been renewed in SharePoint Server 2007 as BCS. In some cases,

you might need to recreate BCS.

Upgrade, install and verify the solution

If the organization has adopted custom solutions, verify that these run well in the new environment.

Review the permissions of the site

In some cases, access permissions may not be reflected even though they are defined in the GUI.

Carry out confirmation promptly, and grant access permissions again, if necessary.

Set alternative access mapping

If alternative access mapping has been used, database migration should be very easy. The reason

for this is that it can minimize the URLs that users have to change. To keep the URLs you have been

using available after migration to a new environment, you have to configure alternative access

mapping when creating (or after creating) Web applications.

Notify the end-users that the infrastructure has migrated to SharePoint Server 2010 and the effects

that this will have.

After the database migration, you will likely want to perform database attachment by using Windows

PowerShell and the upgrade processes.

We strongly recommend that you thoroughly test the upgrade methods in a test environment before

applying them to an operational environment.