Migrating a Project Web Access instance (Project Server 2007)
Updated: November 20, 2008
Topic Last Modified: 2008-12-03
Microsoft Office Project Server 2007 provides various methods for backing up, restoring, or migrating a Project Server farm, Web applications, and content databases. This article discusses the variations in those methods based on specific needs and outcomes.
Restoring by provisioning Project Web Access to another site is a preferred method for restoring a corrupted Project Web Access instance. This method involves attaching the content database at http://servername and then provisioning the Project Web Access site and the four project databases to a new Project Web Access site at
http://servername/newpwa. Workspaces can then be re-linked to the new Project Web Access site.
Storing the content in a separate database involves attaching a content database to a new Project Web Access site such as http://servername/workspaces, while maintaining a provisioned Project Web Access site at the original location of http://servername/pwa and then relinking the workspaces.
This method completely restores Project Web Access and the content databases to their original state by temporarily attaching the content database somewhere else, such as http://servername/else. Then you would provision the new Project Web Access site at the original location, say http://servername/pwa, and then use the Stsadm export command to take each site from the content database at http://servername/else. Then, using the procedure found in Back up and restore the Project Server 2007 farm, you can import all of your sites back under the newly provisioned site at http://servername/pwa. This method is the most complicated, and you should take into consideration how many Project Web Access sites exist in the database that need to be exported and imported to the new Project Web Access site.
|Links to tasks may break when performing this procedure.|
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.
If this will be the only instance or it is the first instance of Office Project Server 2007 to be installed on the server farm, do the following:
|On the target server farm:|
[ ] Run Setup and select the Complete Server Installation Type.
Run the SharePoint Products and Technologies Configuration Wizard:
[ ] Configure the farm services and start the Project Application service.
Create Web applications:
[ ] Create the Shared Services Provider.
This is a general checklist of the steps needed to prepare the server farm for migration. For more detailed information about installing Office Project Server 2007, see Deploy Project Server 2007 to a server farm environment.