In the move process, you will use Office Project Server 2007 tools and SQL Server 2005 tools. Moving all of the databases from one database server to another database server consists of the following steps:

(In some environments, the database administrator must perform certain steps. Those steps begin with "[DBA]".)

1. Perform a full backup of the default Shared Services Provider (SSP).

2. Completely stop the farm by quiescing it from SharePoint Central Administration and stopping the services associated with Office Project Server 2007 and by stopping the Project Server Timer Service, the Project Server Queue, and Project Server Eventing Services.

3. [DBA] Back up the following farm databases by using SQL Server tools:

   • Draft database

   • Published database

   • Archive database

   • Reporting database

   • Content database

     Important:
     There may be more than one Content database in the Project Server farm.

4. [DBA] Copy or move the backup files to the destination database server.

5. [DBA] Restore all of the databases on the destination database server by using SQL Server tools.

6. [DBA] Replicate all of the SQL Server logins, fixed server roles, fixed database roles, and permissions for these databases to the destination server.

Important:
Membership in the db_backupoperator fixed database role is the minimum required to complete this procedure.

Important:
It is important that the queue service is emptied and stopped to prevent data inconsistencies.

In some environments, the DBA must perform these steps.

Back up databases on the source database server

Important:
Read access to the shared folder on the source computer and Write access to the shared folder on the destination computer is the minimum required to complete this procedure. In some environments, the DBA must perform these steps.

Copy or move the backup files to the destination database server

Important:
Membership in the dbcreator fixed server role is the minimum required to complete these procedures. You must add the Farm Administrator account to the dbcreator fixed server role to perform this procedure. The account can be removed from the role after the recovery operation is completed. In some environments, the DBA must perform these steps.

Restore databases on the destination database server

For information about how to copy SQL Server roles and permissions to the destination database server, see Microsoft Help and Support article 246133, How to transfer logins and passwords between instances of SQL (http://support.microsoft.com/kb/246133). For troubleshooting information, see Microsoft Help and Support article 240872, How to resolve permission issues when you move a database between servers that are running SQL Server (http://go.microsoft.com/fwlink/?LinkId=123469).

Important:
Membership in the Administrators group on the local computer is the minimum required to complete these procedures.

Restart the server

1. Create a new Web Application on port 1 using a different name than the Project Web Access site to be restored.

2. Using the SharePoint Central Administration Web site, delete the content database that was created with the new Web application on port 1.

3. On the server that is running Windows SharePoint Services, enter the following commands at a command prompt:

   cd \program files\common files\microsoft shared\Web server extensions\12\bin

   Stsadm –o addcontentdb –url http://<servername>:1 –databasename <databasename>

   The <servername> placeholder is the name of the server that is running Office Project Server 2007, and the <databasename> placeholder is the name of the content database. In SharePoint Central Administration, verify that the content database is attached as expected.

4. At a command prompt, type the following commands to get a list of all of PWA sites.

   cd \program files\common files\microsoft shared\Web server extensions\12\bin

   stsadm -o enumsubwebs -url http://<servername>:<port number>/<pwainstancename> > c:\sites.txt

   The <port number> placeholder is the port where the site resides. In this scenario, the site was created on port 1.

   The <pwainstancename> placeholder is the instance name for Project Web Access.

   Important:
   The stsadm command will save the Sites.txt file to the root directory of drive C.

5. Open the Sites.txt file in Notepad, and then make the changes as appropriate for the EXPORT command for your Project Web Access workspace.For each of the PWA sites listed in the newly created Sites.txt run the following command:

   stsadm -o export -url "http://<servername>/<pwainstancename>/<workspacename>" -filename "c:\<backupdir>\<workspacename>\" -nofilecompression -includeusersecurity -versions 4

   The <workspacename> placeholder is the name of the workspace, and the <backupdir> placeholder is name of the directory where you want to save a backup of the workspace.

6. On the File menu, click Save As, name the file Export<pwainstancename>.bat, and then save the file as a text file to the following directory:

   drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin

7. Change the EXPORT command in the Sites.txt file to an IMPORT command. The following is an example of the IMPORT command:

   stsadm -o import -url "http://<servername>/<pwainstancename>/<workspacename>" -filename "c:\<backupdir>\<workspacename>\" -nofilecompression -includeusersecurity

8. On the File menu, click Save As, name the file Import<pwainstancename>.bat, and then save the file as a text file to the following directory:

   drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin

9. Run the Export<pwainstancename>.bat file. This may take a long time if there are many workspaces.

10. Provision a new Project Web Access site by using the same instance name and databases. Or, use a new instance name with the databases.

11. Run the Import<pwainstancename>.bat file.

    Important:
    This may take a long time if there are many workspaces.

12. Browse the Project Web Access site to make sure that the sites are functional.

    Important:
    If the project workspaces are not linked, you must either manually edit the URL of each project to its newly restored Project Workspace in the Project Workspaces section of PWA, or run the Project Workspace Site Relinker tool. For more information about this tool, see Project Workspace Site Relinker tool.

13. Delete the temporary Web application in SharePoint Central Administration, and then use Internet Information Services (IIS) to verify that it was removed.

14. Delete the restored content database on the server that is running SQL Server.

1. One Web application with one content database.

2. Two site collections with separate content databases — the first collection/database for the root Project Web Access Site, and the second collection/database for Project Workspaces. This arrangement allows you to restore Project Web Access without renaming the Project Web Access site in the future.

3. For larger organizations, we recommend several site collections — one for each department or location in order to avoid any future backup and recovery complexity.