Project Server 2013 Migration from Staging to Production Farm

In this article, I’ll explain How to Migrate / Move a PWA Instance from one farm to another in Project Server 2013?

Project Server 2013 Migration from Staging to Production Farm

Project Server 2013 Migration Steps:

Project Server 2013 Migration steps in details (Source Farm):

(1) Specify the web application content databases.

  • Open SharePoint Management Shell as Administrator.
  • Run Get-SPContentDatabase
Get-SPContentDatabase -WebApplication http://epm

Project Server 2013 Migration from Staging to Production Farm

  • In my case, I have two content databases.
    • WSS_Content.(The Main web application Content Database).
    • WSS_Content_PWA.(An independent Content Database for PWA Instance).

(2) Specify the PWA instance with its ‘Project Web App‘ database.

  • Open SharePoint Management Shell as Administrator.
  • Run Get-SPProjectWebInstance
Get-SPProjectWebInstance

Get-SPProjectWebInstance - PWA Migration

  • In my case, I have one PWA instance http://epm/pwa’ with project database called
    • ProjectWebApp.

(3) Take a full database backup for the ‘Project Web App‘ database.

  • Open SQL Server Management Studio.

Project Server 2013 Migration from Staging to Production Farm

  • Connect to the SQL Server instance.

Project Server 2013 Migration from Staging to Production Farm

  • Backup the following Databases:
    • ProjectWebApp.

Project Server 2013 Migration from Staging to Production Farm

  • Right click on Database name > Tasks > Back Up.

Project Server 2013 Migration from Staging to Production Farm

  • Ensure Backup type is Full > Disk > Select the back up path > OK.

Project Server 2013 Migration from Staging to Production Farm

  • Backup has been taken successfully.

Project Server 2013 Migration from Staging to Production Farm

hint-iconAlternatively, you can use the following T-SQL to take a full database backup:

BACKUP DATABASE WSS_Content_PWA
TO DISK = 'C:\WSS_Content_PWA.BAK'
GO

(4) Take a full database backup for the web application content databases.

  • Repeat the above backup steps for the following content databases:
    • WSS_Content.
    • WSS_Content_PWA.
  • Once you have finished, check the backup path to make sure that the required databases backup has been taken as shown below.

Project Server 2013 Migration from Staging to Production Farm

(5) Backup all the deployed SharePoint solutions (WSP) in your farm if exist.

backup all the deployed WSP solution in your farm

  • Create a ‘WSPSolutions’ folder at any location.
  • Open SharePoint Management Shell as Administrator.
  • Run the below cmdlets to backup all the deployed WSP solution in your farm.
$FolderPath = "c:\WSPSolutions"
foreach ($solution in Get-SPSolution)
{
   $id = $Solution.SolutionID
   $title = $Solution.Name
   $filename = $Solution.SolutionFile.Name
   $solution.SolutionFile.SaveAs("$FolderPath\$filename")
}

Project Server 2013 Migration steps in details (Destination Farm):

(1) Project Server 2013 destination farm preparation steps:

In this article, I don’t cover the detail steps to prepare the Project Server 2013 destination farm, I just will outline the main steps that should be applied to be ready as the following:

  • Install and Configure SharePoint Server 2013 with SP1 Enterprise Edition.
  • Install Project Server 2013 with SP1.
  • Install the latest Cumulative Update that already installed in source farm.

warning-iconThe Project Server 2013 destination farm build number must be higher than the source farm build number or at least have the same build number of source farm (Not lower than the source farm) to avoid this error “This content database has a schema version which is not supported in this farm”

noteTo determine the build number of your source farm and get the latest CU that already installed. Check Find the latest Cumulative Update / Farm Patch Level that has been installed in a SharePoint Farm

(2) Take a full database backup.

  • To enable the rollback in case of the migration process failed, It’s recommended to take a full database backup for the following databases:
    • ProjectWebApp.
    • WSS_Content.
    • WSS_Content_PWA.

(3) Dismount the Project Web Instance as mentioned below.

  • Open SharePoint Management Shell as Administrator.

run-sharepoint-management-shell-as-administrator

  • Run the below cmdlet to get all provisioned PWA instances on the farm.
Get-SPProjectWebInstance

Project Server 2013 Migration from Staging to Production Farm

  • You can also get the provisioned PWA instances via Central Administration as mentioned below.
    • Open Central Administration > Application Managemet.
    • Click on Mange Service Application.Application Management - Manage Service Applications
    • Click on PWA service application to show all the PWA instances that already provisioned in the farm.

PWA migration manage pwa in central administration

  • Dismount the existing Project Web Instance to disconnect the SharePoint site collection from the Project Web App database by running the below cmdlet.
Dismount-SPProjectWebInstance -SiteCollection "http://SERVER/pwa"

Dismount-SPProjectWebInstance

  • You should now note that the PWA instance has been removed in the Central Administration > Manage PWA.

Project Server 2013 Migration from Staging to Production Farm

(4) Dismount PWA Instance Content Database.

  • Dismount the PWA content databases from its currently associated web application that host the PWA instance.

Content database in central admin before perform dismount

  • Perform a ‘Dismount-SPContentDatabase‘ for the PWA content database.
Dismount-SPContentDatabase WSS_Content_PWA

dismount-spcontent-database

noteThe Dismount-SPContentDatabase cmdlet detaches the content database from the Web application, but it does not delete the content database from SQL Server.but it does not delete the content database from SQL Server.

  • After you have performed ‘Dismount-SPContentDatabase’ you should note that the dismounted database has been removed from Content Databases in central administration as shown below

Content database in central admin after perform dismount

(5) Dismount web application Content Databases.

  • Again, Dismount the ‘WSS_Content’ Content Database.
Dismount-SPContentDatabase WSS_Content

dismount-content-datatabase

  • The Content Database is now dismounted successfully as shown below.

after-dismount-pwa-and-web-application-content-database

(6) Restore the source databases backup.

  • Now we are ready to restore the database backup from the source farm to the destination farm by doing the following:
    • Move the databases backup from the source farm to appropriate path in SQL Server of the destination farm.
      • ProjectWebApp.
      • WSS_Content.
      • WSS_Content_PWA.
    • Open the SQL Server Management Studio > Connect to your instance.
    • Perform the restore operation for each database as shown below.

Restore PWA database

restore-pwa-database

Restore PWA instance database in Project Server 1.gif

noteA tail-log backup is unnecessary if you are moving or replacing (overwriting) a database.

Restore PWA instance in Project Server

Restore PWA instance database in Project Server

  • Repeat the above steps for other databases.

(7) Mount ‘WSS_Content’ content database.

  • Once the restore operation is done, we should now mount (reattach) each database again to its web application as mentioned below:
    • Run the ‘Mount-SPContentDatabase’ for ‘WSS_Content’ database to attach it to its web application that host the PWA instance.
Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer"
-WebApplication http://sitename

Mount-SPContentDatabase

(8) Mount ‘WSS_Content_PWA’ content database.

  • Again, Mount ‘WSS_Content_PWA’ database to the web application that host the PWA instance.
Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer"
-WebApplication http://sitename

Mount-SPContentDatabase in project server

(9) Mount ‘ProjectWebApp’ project database.

  • Now you should Mount the ‘ProjectWebApp’ database to the web application that host your PWA instance.
Mount-SPProjectDatabase "MyDatabase" -DatabaseServer "MyServer"
-WebApplication http://sitename

mount pwa database in project server
(10) Mount the PWA Instance.

  • Mount the PWA Instance to associate the PWA site collection to its Project Web App database.
Mount-SPProjectWebInstance -SiteCollection "http://SERVER/pwa
-DatabaseServer" "SQLSERVER" -DatabaseName "ProjectWebApp"

Mount-SPProjectWebInstance

  • Go back to central administration > to make sure that the PWA Instance has been mounted and provisioned successfully.

PWA migration manage pwa in central administration

(11) Deploy your custom WSP solution if exist.

  • Copy all DLL files in ‘bin‘ folder of source web application that located in \\inetpub\wwwroot\wss\VirtualDirectories\[Web Application Port Number]\bin

Project Server 2013 Migration from Staging to Production Farm

backup all the deployed WSP solution in your farm

(12) Change the site collection administrator.

  • To avoid the below access permission issue.

Sorry, this site hasn’t been shared with you.

PWA migration sorry this site hasnt been shared with you

  • Change the Site collection administrator for the web application as the following:
    • Open Central Administration > Application Management > Change Site Collection Administrators > Select your Web Application > Select the PWA site collection.
    • Remove the old site collection administrator then add the new site collection administrator of the current farm.

Change site collection administrator in central administration

(13) Change PWA Instance Administrator.

  • Open Central Administration > Application Management > Manage Service Application.
  • Application Management - Manage Service Applications
  • Click on PWA service application to show the provisioned PWA instances.
  • Edit yourPWA instance as shown below.change pwa administrator
  • Provide the New PWA instance administrator.

set pwa administrator account

(14) Perform a Bulk Update connected SharePoint sites.

  • Perform a Bulk Update to re-linking the projects with its related connected SharePoint sites as the following:
    • Go to Central Administration > General Application Settings > PWA Settings > Manage.

Manage pwa settings in central administration

PWA settings bulk update connected sharepoint sites

bulk update connected sharepoint sites

(15) Update Project Server Cube settings

  • Go to Central Administration > General Application Settings > PWA Settings > Manage > OLAP Database Management.

olap database management

Enjoy 🙂

Advertisements

2 thoughts on “Project Server 2013 Migration from Staging to Production Farm

  1. Hi. Thanks for the details. But for me the workflows which is already there in the EPM are not moving into the next level. Can you help me on that

    Like

Leave a Reply

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

WordPress.com Logo

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

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s