Download The Great Database Consolidation, Project Server 2010 to 2013

PC319
Project Server 2010 databases
Project Server 2010 Archived Database
Project Server 2010 Draft Database
Project Server 2010 Published Database
Project Server 2010 Reporting Database
Project Service 2013 PWA Database
http://technet.microsoft.com/en-us/library/cc197298.aspx
http://go.microsoft.com/fwlink/p/?LinkId=259648
PROJECT SERVER 2013 UPGRADE PROCESS
This model describes the required steps to upgrade from Microsoft Project Server 2010 to Project Server 2013.
A
PLAN & PREPARE
4
Before starting to upgrade, you must understand what is in your SharePoint 2010 Products farm
and set up a new farm based on SharePoint 2013 Products.
Now that the databases are available in the new farm, you can attach and upgrade them. The upgrade
process can be divided into two phases:

You can do this by opening the SharePoint 2013 Management Shell, and then running the following
command to list the Project Server 2013 cmdlets:
There is no in-place upgrade method. The database-attach method is the only supported method
for upgrading from Project Server 2010 to Project Server 2013.

Get-Command *SPProject*
A
Review hardware and software requirements. The database-attach upgrade method requires you
to install a Project Server 2013 destination environment to which you migrate your Project Server
2010 data. It is important to understand the requirements needed to install the farm.
5
Plan for clients. Project Professional 2013 connects to Project Server 2013. There is no backward
compatibility feature that allows connectivity from earlier versions of Project Professional. In Project
Server 2013, additional Web browsers are supported for Project Web App users. They are the same
Web browsers that are supported for SharePoint Server 2013.
GATHER INFORMATION & PLAN FOR
CUSTOMIZATIONS
Gather current configuration information about your Project Server 2010 environment so that you
can create it on your Project Server 2013 destination environment. This includes:
Alternate access mappings
Authentication providers and authentication modes in use
Quota templates
Customizations
Managed paths
Self-service site and management settings
Incoming and out-going email settings
Identify and evaluate customizations in your environment and determine if you want to reapply
them in your Project Server 2013 environment. During the upgrade process, several Windows
PowerShell test cmdlets can be run on your databases to verify if specific customizations can cause
issues with upgrade. In most cases, customizations do not cause the upgrade process to fail.
DEPLOY YOUR PROJECT SERVER 2013 FARM
If you turn off backward compatibility mode (BCM) in your Project Server 2010 environment, you
must also open and save the enterprise global template.
After you disable BCM, you cannot re-enable it. If you want to keep BCM enabled in your
environment, you can set up an intermediate Project Server 2010 farm, restore backup copies of
your Project Server 2010 databases on it, and then disable BCM on it.
6
C
CHECK YOUR DATA FOR KNOWN ISSUES
If your Project Server 2010 Published database contains resource accounts in which the
WRES_Account field contains an empty string (the expected value is NULL), upgrade of this database
fails. To check for this condition, run the following SQL script on the backup copy of your Project
Server 2010 Published database:
Use ProjectServer_Published
select RES_Name, RES_TYPE, RES_ID from MSP_RESOURCES where WRES_ACCOUNT =''
If accounts with this condition are found, run the following SQL script on the same database to fix
any accounts with this condition:
Use ProjectServer_Published
Update MSP_RESOURCES set WRES_ACCOUNT = null where WRES_ACCOUNT =''
B COPY DATABASES
After you have prepared the new environment, you can copy and upgrade databases.
The following database types are required to upgrade to Project Server 2013:
In new farm
Content databases
Install the software
Install the following on your farm servers:
Content Database
containing PWA site
data
Database servers: SQL Server 2008 R2 or SQL Server 2012
B
Project Server 2010 databases
Project Server 2010 Archived Database
2
Project Server 2010 Draft Database
PROJECT SERVER UPGRADE PHASE
The following occurs during the Project Server upgrade phase:
Project Server 2010 Published Database
Project Server 2010 Reporting Database
To perform a database-attach upgrade, copy your databases from your original farm to
your new farm.
Original SQL Server
Configure the farm
Configure the following on your farm on the Central Administration site:
Start the Project Server Application service on the farm.
Create the Project Server service application.
Create a Web Application for the Project Web App site you
plan to upgrade.
Most actions take place
in SQL Server
Management Studio
Database servers
Content
databases



New SQL Server
Use the SQL Server backup and restore process to copy the databases to the new
environment. Optionally, set the databases to read-only in SQL Server to preserve
access to the original farm data, without allowing changes.
Service application
databases
Web and Application servers: Install the prerequisites for
SharePoint Server 2013, and then install SharePoint Server 2013
(which is required for Project Server 2013). Install Project Server
2013.
Restore
3
CONTENT DATABASE UPGRADE PHASE
The following occurs during the Content Database upgrade phase:
Back up







1
Content Database Upgrade – Attach and upgrade the SharePoint Content database that contains
your Project Web App site data.
Project Server Upgrade – Consolidate your Project Server 2010 databases, attach them to the
Project Server 2013 PWA instance, and then upgrade the data.
Your Project Server 2010 databases must be in Native mode (non-backward compatibility mode) in
order for them to upgrade successfully.
There is no direct upgrade path from Project Server 2007 to Project Server 2013. You must first
upgrade your Project Server 2007 farm data to Project Server 2010, and then upgrade to Project
Server 2013.
2
VERIFY THAT YOUR DATABASES ARE IN NATIVE MODE
UPGRADE DATA
C
You use Windows PowerShell cmdlets to execute many of the procedures required to upgrade to
Project Server 2013. On the computer on which you installed Project Server 2013, it is important to
verify that you have the ability to open the SharePoint 2013 Management Shell, and that you are
able to access the Windows PowerShell cmdlets for Project Server 2013.
KEY ITEMS TO NOTE FOR UPGRADE
1
PREPARE YOUR WINDOWS POWERSHELL ENVIRONMENT
© 2012 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
A
B
Content databases
Content Database
containing PWA site
data
Project Server 2010 databases
Project Server 2010 Archived Database
Project Server 2010 Draft Database
Project Server 2010 Published Database
Project Server 2010 Reporting Database
C
A
A
A
A
B
C
Step
#
Description
PowerShell cmdlet
1
Check the SharePoint content database that contains your Project Site
data for errors that can cause upgrade to fail.
Test-SPContentDatabase
2
Attach and Upgrade the SharePoint Content Database.
3
Add your account as a secondary owner of the PWA site collection
that you want to upgrade.
4
If you are migrating Project Server 2010 users who were using
Windows Classic authentication over to claims-based authentication
when upgrading to Project Server 2013, you will need to run the
following Windows PowerShell cmdlet. If this is not done, your users
will not be able to log on to Project Web App after upgrade.
5
Run a health check on the PWA site collection to view upgrade
warning information.
Test-SPSite
6
Upgrade the Project Web App site from SharePoint 2010 mode.
Upgrade-SPSite
Mount-SPContentDatabase
Set-SPSite
(Get-SPWebApplication
<webappURL>).migrateUsers($true)
Step
#
PowerShell cmdlet
(summary)
PowerShell cmdlet
(Format)
1
TestSPContentDatabase
Test-SPContentDatabase –Name <contentdbName> –WebApplication <URL>
-ServerInstance <servername>
2
MountSPContentDatabase
Mount-SPContentDatabase –Name <contentdbName> –WebApplication <URL> DatabaseServer <servername> -NoB2BSiteUpgrade
3
Set-SPSite
Set–SPSite -Identity <sitecollectionName> -SecondaryOwnerAlias <account>
4
(Get-SPWebApplication
<webappURL>).migrat
eUsers($true)
(Get-SPWebApplication <webappURL>).migrateUsers($true)
5
Test-SPSite
Test–SPSite –Identity <URL>
6
Upgrade-SPSite
Upgrade–SPSite –Identity <URL> –versionupgrade
Project Server 2010 databases
Consolidated Project Server 2013 database
Project Server 2010 Archived Database
Project Server 2010 Draft Database
Project Server 2010 Published Database
Project Server 2010 Reporting Database
Project Service 2013 PWA Database
Parameter
Description
–WebApplication
Specifies the SharePoint web application that you created for the Project Service
Application.
The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or
a valid name of SharePoint web application (for example, MyOfficeApp1); or an instance of
a valid SPWebApplication object.
Specifies the instance of the database service on which the databases are located.
The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid
name of a SQL Server instance (for example, DBSvrInstance1); or an instance of a valid
SPDatabaseServiceInstance object.
The name of the ProjectServer2010_Archive_Database that you restored on SQL Server.
-Dbserver
-ArchiveDbname
-DraftDbname
The name of the ProjectServer2010_Draft_Database that you restored on SQL Server.
-PublishedDbname
The name of the ProjectServer2010_Published_Database that you restored on SQL Server.
-ReportingDbname
The name of the ProjectServer2010_Reporting_Database that you restored on SQL Server.
-ProjectServiceDbname
The name that you want to call the Project Server 2013 Project Web App database.
Web Server
SenseiWEB01
App Server
SenseiAPP01
SharePoint Web Application
http://senseiprojectserver.com
DB Server
SenseiDB01
Project Server 2010 databases
ProjectServer2010_Archive_Database
ProjectServer2010_Draft_Database
ProjectServer2010_Published_Database
ProjectServer2010_Reporting_Database
Consolidated Project Server 2013 database
ProjectService2013_PWA_Database
Consolidated Project Server 2013 database
Project Service 2013 PWA Database
Parameter
–Name
Description
The name of the Project Web App database to mount or create
-DatabaseServer
The name of the instance of SQL Server where the database is located.
-WebApplication
The web application that the Project Web App database will mount to.
ProjectService2013_PWA_Database
Parameter
–Name
Description
Specifies the name of your Project Web App database.
–WebInstance
Specifies the SharePoint web application that the Project Web App database is associated
with.
-Databaseserver
Specifies the instance of the database service on which the Project Web App database is
located.
The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid
name of a SQL Server instance (for example, DBSvrInstance1); or an instance of a valid
SPDatabaseServiceInstance object.
Upgraded ProjectService2013_
PWA_Database
ProjectService2013_PWA_Database
Parameter
-Name
Description
Specifies the name of your Project Web App database.
–WebApplication
Specifies the SharePoint web application you created for the Project Service Application.
The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or
a valid name of SharePoint web application (for example, MyOfficeApp1); or an instance
of a valid SPWebApplication object.
-DatabaseServer
The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid
name of a SQL Server instance (for example, DBSvrInstance1); or an instance of a valid
SPDatabaseServiceInstance object.
Upgraded ProjectService2013_
PWA_Database
Parameter
-DatabaseName
–SiteCollection
-DatabaseServer
Description
Specifies the name of your Project Web App database.
Specifies the site collection you created for the Project Service Application.
Specifies the instance of the database service on which the Project Web App database is
located.
The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid
name of a SQL Server instance (for example, DBSvrInstance1); or an instance of a valid
SPDatabaseServiceInstance object.
Parameter
-Identity
Description
Specifies the URL of the Project Web App instance.
Parameter
-Identity
Description
Specifies the URL of the Project Web App instance.
Parameter
-Identity
-URL
Description
pwasite is the name of the installed SharePoint feature being enabled
Specifies the URL of the Project Web App site collection.
http://senseiprojectserver.com/pwa
Enable-SPFeature
Remember to stop by Sensei Booth #407 to say hi and pickup your free Reference Card
http://technet.microsoft.com/en-us/library/ee662104.aspx
http://technet.microsoft.com/en-us/library/cc197298.aspx
http://technet.microsoft.com/en-us/library/cc303399.aspx
Remember to stop by Sensei Booth #407 to say hi and pickup your free Reference Card
Remember to stop by Sensei Booth #407 to say hi and pickup your free Reference Card
MyPC fill out
evaluations
& win prizes!
www.msprojectconference.com