Migrate a Project Web App instance in Project Server 2010

Provisioning Project Web App to another site

Restoring by provisioning Microsoft Project Web App to another site is the preferred method for restoring a corrupted Project Web App instance. This method involves attaching the content database at https://servername and then provisioning the Project Web App site and the four project databases to a new Project Web App site at https://servername/newpwa. Workspaces can then be re-linked to the new Project Web App site.

Storing site content in a separate database

Storing the content in a separate database involves attaching a content database to a new Project Web App site such as https://servername/workspaces, while maintaining a provisioned Project Web App site at the original location of https://servername/pwa and then relinking the workspaces.

Restoring a Project Web App site completely

This method completely restores Project Web App and the content databases to their original state by temporarily attaching the content database somewhere else, such as https://servername/else. Then you would provision the new Project Web App site at the original location, say https://servername/pwa, and then use the Windows PowerShell export command to take each site from the content database at https://servername/else. Then, using the procedure found in Back up and restore the Project Server 2010 farm, you can import all of your sites back under the newly provisioned site at https://servername/pwa. This method is the most complicated, and you should take into consideration how many Project Web App sites exist in the database that need to be exported and imported to the new Project Web App site.

Migrating Project Server to an existing server farm

When you are migrating to an existing farm, the steps are the same as migrating to a new farm, but first you must decide if you will add your content database to one of the existing Web applications (as described above) or if you plan to add your content database to a newly created Web application.

There are a number of reasons why you might choose to create a new Web application, but perhaps the most common is that the content that you are migrating requires a different kind of authentication than is offered on the existing server. For example, imagine that the existing server is configured to authenticate Windows users but the new content requires forms-based authentication. In this case, you would need to create a new Web application. You might also need to extend your Web application, and in that case, you would also need to create a new Web application.

If you are in an extranet environment where you want different users to access content by using different domains, you might also need to extend a Web application to another Internet Information Services (IIS) Web site. This action exposes the same content to different sets of users by using an additional IIS Web site to host the same content.

Preparing to migrate a Project Server instance

If this will be the only instance or it is the first instance of Project Server 2010 to be installed on the server farm, do the following on the target server farm:

This is a general checklist of the steps needed to prepare the server farm for migration. For more detailed information about installing Project Server 2010, see Deploy Project Server 2010 to a server farm environment.