Moving Project Server 2010 to another server

I am having issues moving Project Server 2010 to another server. I have tried taking backup of the 4 databases in SQL and creating a new PWA instance pointing to the backed up databases after restoring. This works and allows access to the resources but the links for the PWA sites are no longer there.

What is the recommended method of moving Project Server 2010 to another server including all sharepoint content relating to the project server.
Who is Participating?
raybiesConnect With a Mentor Commented:
The content database is the same as any other SharePoint content DB.

1.- Create a new Project Application from CA (if it hasn't already been created)
2.- Go to backup/Restore > Restore from a backup
3.- Select the backup from the old server
4.- Select just the project application > restore to the new project app.

Try this on a dev environment 1st.

You can also do this using Powershell.
Import-SPWeb http://myprojectapp -Path("\\myOldbackUpOf_JUST_projectApp");
Can you describe your environment?
andyhinesAuthor Commented:
It's Project Server running on top of Sharepoint Enterprise 2010 and Windows 2008. A separate server runs SQL Server 2008 where all of the Sharepoint and Project databases sit.
The new environment is a duplicate (2 x Windows Server 2008, one with SQL Server 2008, one with Sharepoint & SQL).

I now understand that I've missed copying the content database and that's why I get the error listed above. Even when I do copy the content database however it still gives the same problem. I'm clearly missing something but not sure what.

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

1.- Make sure the SP/PS binaries are exactly the same in both environments
2.- Setup SP and PS on the new environment (envNew)
3.- Do a farm backup (envOld)
4.- Restore backup to (envNew)
5.- For server settings backup/restore use the PS Resource Kit
The above is the recommended way.

I'd test this for you, but I stopped using PS in favor of just the Project Sites... so I don't have the 4 DB's or the Project Application at hand.
andyhinesAuthor Commented:
Hi. Thanks for this. I've actually moved the 4 main databases and am using these as part of the new PWA system. I forgot to copy the content database across though and I'm struggling to understand how to do this retrospectively. I still have the old server available and I haven't yet created any new projects. Can I simply backup on the old server, restore on the new and then link this content database to my PWA instance ?

Can you provide a short sequence of steps ? Thanks,
andyhinesAuthor Commented:
Thnaks for your help. The bit that was causing me the problem was when trying to recreate the PWA site because this failed citing an invalid name. Removing and recreating the IIS site resolved this. Probably because we'd already created one. Also the patch levels weren't identical between old and new servers so that involved an extra couple of steps. All working now though.

Regards - Andy
andyhinesAuthor Commented:
Good advice. Required slightly more understanding on my part than I had at the start of the process.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.