Moving Microsoft Project Server from one server to another

Question

SQL Server

Hello everybody.

There was a need to transfer one of the servers with Microsoft Project Server 2007 from one piece of hardware to another.
And since I hadn’t seen the project settings before, the question arose: “How can this topic be done quickly?”

In general, the idea is this: backup the Project Server database on the old server.
Then install the Project instance on the new server and then replace the new database with the one that I will deploy from the backup from the old server.
True, I have doubts that this option will work, but still.

Then I thought, maybe there is some tool designed specifically for moving, this is a fairly common problem.

Still have a question? And in general, is it mandatory to install Sherpoint on the same machine?

In general, I ask the community for help, since there is no time or opportunity to conduct experiments at the moment :(

Answer 1

Of course, I understand that two months have already passed, but nevertheless, I can share my experience. In the official migration manual, this process is somehow vaguely described, so I developed my own by trial and error.
Briefly, the sequence of actions is as follows:
1. We put on a new SharePoint server (WSS or MOSS) and Project Server. We update to the same versions as on the current server (up to hotfixes). We start the configuration wizard, start the services. We DO NOT create web applications for content.
2. Back up the farm on the old server using the standard stsadm utility (stsadm -o backup -directory -backupmethod full). You can also do this through the Admin Center. We spread the backup to the network share, open full access for the account under which we will restore.
3. On the new server, we restore the backup using stsadm (you can try it through the Administration Center, but I did not test it). I changed the server name and the number of servers, so it was impossible to restore the entire farm. In this case, you need to restore the web applications and SSPs sequentially (stsadm -o restore -directory -backupid -item <web application_or_SSP_name> -restoremethod new). During the restore process, you need to set new server names and URLs. If you have a 1:1 migration - i.e. one server and its name will be the same, you can try to restore the entire farm (without the -item parameter). To preview backup/restor objects, use the (-showtree) option.
4. After that, Project's project workspaces may fall off SharePoint. For relinking, you can useProject Workspace Site Relinker tool .
In fact, the same database + some additional data is backed up through a regular backup / restore. Therefore, additional fuss with accounts and access rights in SQL and other things disappears.