• Article

Database-attach full upgrade to Project Server 2010

 

Applies to: Project Server 2010

Topic Last Modified: 2013-06-06

Important

Upgrading from the Project Server 2010 public Beta to the Project Server 2010 released version is explicitly blocked and not supported. This restriction applies to both the in-place and database-attach upgrade methods.

When you upgrade from Microsoft Office Project Server 2007 to Microsoft Project Server 2010 by using the database attach upgrade process, you upgrade only the content for your environment, and not the configuration settings. Using a database attach upgrade process is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. It is also required if you are upgrading from Office Project Server 2007 deployed on a hardware that only supports a 32-bit server operating system.

Database-attach upgrade to Project Server 2010 can be done in either of two ways:

  • Database-attach full upgrade: Migrates the project data stored in the Office Project Server 2007 databases, plus the Microsoft Project Web App (PWA) site data stored in a SharePoint content database.

  • Database-attach core upgrade: Migrates only the project data stored in the Office Project Server 2007 databases.

This article provides the procedures required to perform a database attach full upgrade. For information about different types of methods for upgrading to Project Server 2010, see Project Server 2010 upgrade overview.

Process overview

When you perform a database attach full upgrade, you will back up the required databases in the old farm and then restore them in the new farm. When you restore the SharePoint content database that contains your Project Web App site data and add it to the new farm, the upgrade process runs and upgrades the database. After you restore the Office Project Server 2007 databases, they are upgraded to Project Server 2010 when they are used to provision a Project Web App instance in Project Server 2010. While both the database attach upgrade process and the in-place upgrade process are similar in functionality, the database attach upgrade keeps the original Office Project Server 2007 environment intact because you are using backup copies of the databases for the upgrade processes.

Note

The featured called “Project Web Access” in Office Project Server 2007 is now called “Project Web App” in Project Server 2010.

Before you begin

Before you begin the database attach full upgrade to Office Project Server 2007, review the following information about permissions, hardware requirements, and software requirements. Follow the specified steps to install or configure prerequisite software or to modify settings.

Review required permissions

You must have at least the following permissions to complete the procedures in this article:

  • On the database server from which the databases are being detached you must be a member of the following roles:

    • The db_owner fixed database role.

    • The db_backupoperator fixed database role.

  • On the server farm to which the databases are being attached, you must be a member of the local Administrators group, and you must be a member of the following roles on the database server:

    • The dbcreator fixed server role.

    • The db_owner fixed database role.

  • In some environments, you must coordinate the move procedures with the database administrator. Be sure to follow any applicable policies and guidelines for handling databases.

Review required hardware and software

You must be running one of the following products on the database servers to perform these procedures:

  • On your Office Project Server 2007 environment: the Microsoft SQL Server Client tools for SQL Server 2000, SQL Server 2005, or SQL Server 2008. These are required to back up your required databases.

  • On your Project Server 2010 environment: a 64-bit version of one of the following products:

    • SQL Server 2008 Service Pack 1 with Cumulative Update 2

    • SQL Server 2005 Service Pack 3 with Cumulative Update 3

Note

Project Server 2010 databases can only be hosted on 64-bit versions of these two versions of SQL Server.

Perform prerequisite steps

Before you back up the databases, you must prepare for the upgrade by following these steps:

  1. Create a new server farm environment. For information about creating the new environment, see Deploy Project Server 2010 to a server farm environment.

  2. If you have custom site definitions in the old environment, create new site definitions and upgrade definition files for these site definitions and deploy them to the new environment.

Database attach full upgrade overview

A database attach full upgrade will upgrade your Office Project Server 2007 databases and will also restore the Project Web Access site's content database to your Project Server 2010 farm. The following databases are upgraded in a database attach full upgrade:

  • Draft

  • Archive

  • Publish

  • Reporting

  • SharePoint content database (containing your Project Web Access site data)

A database attach full upgrade differs from a database attach core upgrade in the fact that the core upgrade will only upgrade your Office Project Server 2007 databases, migrating only your Office Project Server 2007 project data. If you only want to upgrade your Office Project Server 2007 project data, see Database-attach core upgrade to Project Server 2010.

To perform a database attach full upgrade, you must follow these general steps:

  1. Verify your Project Server 2007 data

  2. Extract your Project Web Access site from a content database to a new content database (Optional)

    Note

    This extraction is only required if your Project Web Access site data is not contained in its own site collection (and therefore, its own content database). Doing this step extracts your Project Web Access site data from an existing content database and then puts it in its own content database.

  3. Back up the databases in SQL Server

  4. Restore the backup copies to the new farm

  5. Add the restored content database to the Project Server 2010 farm

  6. Provision a new Project Server 2010 PWA instance using the restored databases

  7. Diagnose failures

  8. Configure for post-installation

  9. Verify whether the migration has been successful

These steps require that you have Project Server 2010 installed in your environment. You do not need to configure a Project Web App site prior to doing this procedure. You also do not need to do post-installation configuration such as configuring for Exchange Server integration or reporting, which can be done after upgrading. For more information about installing Project Server 2010, please see Deploy Project Server 2010 to a server farm environment.

Verify your Project Server 2007 data

You must verify that your Office Project Server 2007 data is in a valid state to help ensure that your upgrade will be successful. You must verify the following:

  • All projects should be checked-in.

  • The Project Web App site name of "ProjectBICenter" is reserved in Project Server 2010. Verify that Office Project Server 2007 does not use this as a Project Web App site name.

  • The list name of "Project Detail Page" is reserved in Project Server 2010. Verify that Office Project Server 2007 Project Web Access does not contain a list with this same name.

  • Resolve all custom field and lookup table name conflicts with names that are reserved in Project Server 2010. See the Custom field and lookup table name conflicts section for more information.

Custom field and lookup table name conflicts

There are certain custom fields and lookup tables name that are reserved in both Office Project Server 2007 and Project Server 2010. If you are upgrading from Office Project Server 2007, verify that you do not have custom field names that are in conflict with the names reserved for Project Server 2010. If any of these names are used in the current Office Project Server 2007 database, the custom fields and outline codes must be changed in Office Project Server 2007 before proceeding further with the migration. Use Microsoft Office Project Professional 2007 connected to a Office Project Server 2007 instance to validate and take corrective action.

Reserved outline code names

Outline code name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Department

X

Flag Status

X

Reserved custom field names

Custom field name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Sample Approved Finish Date

Project

X

Sample Approved Start Data

Project

X

Sample Areas Impacted

Project

X

Sample Assumptions

Project

X

Sample Business Need

Project

X

Sample Compliance Proposal

Project

X

Flag Status

Task

X

Sample Goals

Project

X

Sample Post-Implementation Review Date

Project

X

Sample Post-Implementation Review Notes

Project

X

Sample Primary Objectives

Project

X

Project Departments

Project

X

Project Impact

Project

X

Sample Proposal Cost

Project

X

Sample Proposed Finish Date

Project

X

Sample Proposed Start Date

Project

X

Relative Importance

Project

X

Resource Departments

Resource

X

Extract your Project Web Access site from a content database to a new content database (Optional)

Note

Only use this procedure if you do not have a separate content database for your Project Web Access site data.

If you do not have a separate content database for your Project Web App site, your Project Web App site data may share its content database with data from other sites. In this situation, we recommend that you extract the Windows SharePoint Services site collection for PWA into a new content database.

Using this procedure has the following requirements.

  • You must have a fully functional Office Project Server 2007 farm.

  • You must have administrative access to the computer in which the farm is running.

  • In your Office Project Server 2007 farm, you must have at least one Web application (other than the Web application where your Project Web App site exists). A new Web application on https://server:82 is an example of such an application.

  • You know where your Stsadm command-line tool exists. The default location is: %PROGRAMFILES%\Common Files\Microsoft Shared\Web Server Extensions\12\BIN.

To extract Project Web Access site content from a content database to a new content database:

  1. Identify the URL of the site collection you want to back up (for example, https://server/PWA).

  2. Use the following Stsadm command to back up the site collection:

    Stsadm -o backup -url <SiteURL> -filename <FullPathToBackupFile>

    For example: Stsadm -o backup -url https://server/pwa -filename c:\temp\backup.bak

  3. Use the following Stsadm command to create a new content database in your second Web application.

    Stsadm.exe -o addcontentDB -url <NewWebAppURL> -ds <SQLServerName> -dn <NewContentDBName>

    For example: Stsadm.exe -o addcontentDB -url https://server:82 -ds CorpSQL1 -dn PWAContentDB

  4. Use the following Stsadm command to restore the site collection to the second Web application.

    Stsadm -o restore -url <SiteURL> -filename <FullPathToBackupFile>

    For example: Stsadm -o restore -url https://server:82/NewPWA -filename c:\temp\backup.bak

    Make sure the site URL that you intend to use while restoring does not already exist in the new Web application (or else this procedure will fail). You are not required to use the same name you used during backup.

    The name you use to restore should be the name you intend to use when you upgrade the data to Project Server 2010.

Back up the databases in SQL Server

Follow the appropriate procedure to back up your Office Project Server 2007 databases and your Project Web Access site content database in SQL Server 2000, SQL Server 2005, or SQL Server 2008 (depending on which you are using to host the databases). Repeat the procedure for each of the following databases in the original server farm:

  • Content

  • Project Server_Draft

  • Project Server_Archived

  • Project Server_Published

  • Project Server_Reporting

At the end of this procedure, you will have created duplicates of each database.

To back up a database in SQL Server 2000

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. In SQL Server Enterprise Manager, expand Microsoft SQL Servers.

  3. Expand SQL Server Group.

  4. Expand (local) (Windows NT).

  5. Expand Databases.

  6. Right-click the database that you want to back up, point to All Tasks, and then click Backup Database.

  7. In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then, in the Backup area, select Database - complete.

  8. In the Destination area, either select an existing destination or do the following:

    1. Click Add.

    2. In the Select Backup Destination box, select File Name, and then, next to the File Name box, click Browse.

    3. In the Backup Device Location - (local) dialog box, in the File name box, type a file name, and then click OK.

    4. Click OK again to close the Select Backup Destination dialog box.

  9. Click OK to start the backup process.

  10. Click OK to acknowledge that the backup process is complete.

Repeat the previous procedure to back up the remaining required databases.

To back up a database in SQL Server 2005

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  2. In the Connect to Server box, fill in the connection information, and then click Connect.

  3. After you connect to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by expanding the server name.

  4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

  5. In the Source area, in the Database box, verify the database name.

  6. In the Backup type box, select Full.

  7. Under Backup component, select Database.

  8. In the Backup set area, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.

  9. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.

  10. Click OK to start the backup process.

Repeat the previous procedure to back up the remaining required databases.

To back up a database in SQL Server 2008

  1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.

  2. In the Connect to Server box, fill in the connection information, and then click Connect.

  3. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.

  4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

  5. In the Source area, in the Database box, verify the database name.

  6. In the Backup type box, select Full.

  7. Under Backup component, select Database.

  8. In the Backup set area, in the Name box, either accept the default backup set name or type a new name.

  9. In the Destination section, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.

  10. Click OK to start the backup process.

If you need more information about backing up databases in SQL Server, see the following articles:

Restore the backup copies to the new farm

After you have configured the new Project Server 2010 server farm, you can restore the backup copies of the databases on the SQL Server instance that you are using to host your Project Server 2010 databases. Note that you must restore to a 64-bit version of SQL Server 2008 SP1 with CU2, or 64-bit SQL Server 2005 SP3 with CU3. Start with one database, and then verify that the recovery has worked before you restore the other databases.

The following section provides procedures for restoring the backups.

To restore a backup copy of a database in SQL Server 2005 Enterprise Edition

  1. In SQL Server Management Studio, right-click Databases, and then click Restore Database. The Restore Database dialog box appears.

  2. In the Restore Database dialog box, on the General page, in the To database box, type the name of the database you are restoring.

  3. In the To a point in time box, keep the default (Most recent possible).

  4. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.

  5. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.

  6. In the Backup location area, click Add.

  7. In the Locate Backup File dialog box, select the file that you want to restore, and then click OK.

  8. In the Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.

  9. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.

  10. Click OK to start the recovery process.

Repeat the previous procedure to restore the remaining required databases.

To restore a backup copy of a database in SQL Server 2008 Enterprise

  1. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.

  2. Right-click Databases, and then click Restore Database. The Restore Database dialog box appears.

  3. In the Restore Database dialog box, on the General page, type the name of the database to be restored in the To database list.

  4. In the To a point in time box, retain the default (Most recent possible).

  5. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.

  6. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.

  7. In the Backup location area, click Add.

  8. In the Locate Backup File dialog box, select the file that you want to restore, click OK, and then, in the Specify Backup dialog box, click OK.

  9. In the Restore Database dialog box, under Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.

  10. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.

  11. Click OK to start the recovery process.

Repeat the previous procedure to restore the remaining required databases.

For more information about restoring databases in SQL Server, see the following articles:

Add the restored content database to the Project Server 2010 farm

After restoring the Windows SharePoint Services Content database, you need to add it to the Project Server 2010 farm.

Note

Ensure that the Web application in your Project Server 2010 farm does not contain a site with the same name as the one you are upgrading.

Add the content database to the Project Server 2010 farm

  1. Open a Command Prompt window as Administrator, and navigate to:

    %PROGRAMFILES%\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

  2. Run the following:

    STSADM.EXE -o addcontentDB -url <WebAppURL> -databaseserver <SQLServerName> -databasename <WSSContentDBName>

    For example: STSADM.EXE -o addcontentDB -url http://contoso -ds Contoso1 -dn WSS_Content

    The database name should be the exact name of the content database you restored to SQL Server in the previous procedure. When the command prompt returns, the step has been completed.

  3. Monitor the upgrade logs for failure. The Upgrade logs are located at: %PROGRAMFILES%\Common Files\Microsoft Shared\Web Server Extensions\14\Logs

  4. If there are any reported failures, navigate to the PWA site—http://<server>/<instance>/_layouts/settings.aspx (for example, http://contoso/pwa/_layouts/settings.aspx). If this page loads successfully, proceed to the next procedure.

Provision a new Project Server 2010 PWA instance using the restored databases

In Project Server 2010, you can now create a Project Web App instance using the Office Project Server 2007 databases you restored to SQL Server in the previous step. When the instance is created, the restored databases will be upgraded to Project Server 2010.

Create a Project Server 2010 Project Web App instance using the restored Project Server 2007 databases

  1. On SharePoint Central Administration Web site, in the Application Management section, click Manage service applications.

  2. On the Manage Service Applications page, click Project Server PSI Service Application.

  3. On the toolbar, click Manage.

  4. On the Manage Project Web App Sites page, click Create Project Web App Site.

  5. On the Create Project Web App Site page:

    1. In the Project Web App Site Location, select the SharePoint Web application that you are using to host Project Web App. Also specify the appropriate Project Web App path.

    2. In the Administrator Account fields, keep the default values.

    3. In the Primary Database field, type the name of the database server where your restored Office Project Server 2007 databases are located.

    4. Verify that the names of the Project Server databases match the names of the restored Office Project Server 2007 databases that you will use. If they do not, change them so that they match.

      Important

      The databases names must be exact matches with the restored Office Project Server 2007 database names in SQL Server. If the names do not match, a new Project Server 2010 database will be created and the restored Office Project Server 2007 database will not be upgraded.

    5. Click OK.

Project Server will start the PWA site creation process. Click Refresh occasionally to view the status of the instance provisioning. Be patient as this occurs, as it may take a while to finish. When the site creation process has finished, the status shown on the PWA site list is Provisioned.

The URL can now be used to connect Internet Explorer, the Project client, and custom-code based clients to Project Web App.

Note

The first invocation of the Internet Information Services (IIS) application pool that contains the Project Web App application can be slow as the .NET Framework application is loaded and compiled.

Diagnose failures

If your Project Web App instance does not provision successfully, the provision process will return a status of Failed, at which point you can check the upgrade logs for additional details about the failure.

The upgrade log is located in the following default location: %PROGRAMFILES%\Common Files\Microsoft Shared\Web Server Extensions\14\Logs

Each upgrade attempt creates a new log, so view the most current logs. You can view the correct log file by noting the Date/Time stamp that is embedded in the log file name (for example, Upgrade<DateTime>.LOG). Open the log files in Microsoft Excel and search for “Failure” to find more information about the why the upgrade failed. For example, the log file may describe the failure occurring because of an invalid custom field name in the data. You would then need to return to Office Project Server 2007 and fix the issue (possibly by renaming the custom field). You would then need to run through the steps in this procedure again (back up and restore the databases, and then create a new instance in Project Server 2010).

If the upgrade log does not give you any insight in correcting the problem, contact Microsoft Support Services.

Configure for post-installation

After you create the Project Web App instance to upgrade your Office Project Server 2007 databases to Project Server 2010, you can do additional post-installation steps to make the deployment more functional. For example, additional post-installation configuration steps include the following:

  • Configure bulk update for project sites

  • Configure reporting for Project Server 2010

  • Configure Excel Services in Microsoft Office SharePoint Server 2007

  • Configure single sign-on

  • Configure the cube building service

  • Configure Time Reporting periods

  • Configure Exchange integration

The first item in the list, "configure bulk update for project sites," is always necessary in a full database-attach upgrade, and it is described in this article. The other items may be necessary, depending on the features you are using in your environment. For more information about these steps, see Install and configure Project Server 2010.

Configure bulk update for project sites

Because full upgrade includes upgrading project sites from Office Project Server 2007 to Project Server 2010, you have to update the upgraded project site URLs for the new Web application in the Project Server 2010 environment. After you upgrade, the upgraded project sites have invalid URLs that have to be changed to reflect the Project Server 2010 Web application in the new environment. You can use the Bulk Update Project Sites configuration settings on the Project Server 2010 Server settings page (Operation Policies section) to make bulk changes to your project sites' site path information from one Web application to a different one. The change allows you to re-link the upgraded project sites to their upgraded projects.

To configure the bulk update for project sites

  1. On the Project Server 2010 Server Settings page, in the Operational Policies section, click Bulk Update Project Sites.

  2. On the Bulk Update Project Sites page, in the Update Site Paths section, for the Previous Site Path section, in the Web Application field, select the previous site application (default value). In the Previous Site section, in the Path Site URL field, enter the previous site URL.

  3. In the New Site Path section, in the Web Application field, select the Project Server 2010 Web application. In the New Site Path section, in the Site URL field, enter the new Site URL.

  4. In the Update Content Types section, verify that Update Content Types is selected (default). This setting makes sure that Project Issues, Risks, and Document content types are updated in their new environment so that object links are functional.

  5. In the Project Site Permissions section, verify that Synchronize site permissions is selected (default). This makes sure that upgraded users who previously had access to the Project site in the old environment are now able to access the upgraded project site in Project Server 2010.

  6. Click Update.

After you have updated, you can verify that your upgraded projects are now linked to their corresponding project sites. You can verify this on the Project Sites page in the Operational Policies section of Project Server 2010 Server Settings. If relinking was successful, URLs appear in the Site Address column.

Verify whether the migration has been successful

Open Project Web App and check whether your data has migrated correctly. Run your regular testing on this server. If you notice any differences from normal behavior, document them and contact Project Server 2010 Support Services.