Exporting PWA data

[ricardo.marques01]

Hi

My purpose is to get the PWA database from one server and put it on
another, all the docs that i have read from Microsoft is about
migration. Not write my purpuse atm.

I don't wanna export SSP, or web applications data, only data from
PWA. Don't know if it's possible or not.

Any hints on this?

Thanks

 

[Dave]

You can move the data by making a SQL backup of the four Project Server
backups and the copy it over the newly created instance of project server.
Let me know if that works for you.


This question keeps popping up on this newsgroup, I wonder if someone could
put up a write up for this so that we can point everyone to it.

Regards,
Dave

 

[Marc Soester [MVP]]

Hi Dave,

I think the reason why noone has written this up is because it is actaully
comlicated. Moving Projects is no big deal, but most companies want to move
their entire system ( including WSS). this is where the complication is. We
experienced many challanges moving a system from one to another server and
unfortunalty it is not straith forward and lots of manual stuff to think
about.

Having said this, it would be great if MS could publish a document which
outlines the steps as MS would recommend it.

 

[Dave]

Hello Marc,

I agree with you. Moving the system in 2003 was so easy but it seems to have
become way too complicated in 2007. It would be nice if you could share your
experiences with moving the WSS sites over to a new instance. We tried to do
it once but we could not decouple (If I can call it that) the Project
Workspace from the new instance it kept pointing to the original Project
Workspace address and deleting this site corrupted the original workspaces.

With regards to Microsoft, I have given up on them, I would be happy if they
just came out with a user manual for Project Server.

Dave

 

[Marc Soester [MVP]]

Hi Dave,

yeap you are spot on, 03 was much easier

In a nutshell we essentially use the command prompt to export all worskpaces
from the exisiting server. we then import the workspaces into the new
environment after we imported the Projects. We wrote a script that does it
and at this stage we found it to be the savest way to move exisiting wss
data.

There are quite a lot of manual steps for example if you have changed the
PWA homepage ( added lists or webparts) we have to do this manually, also if
the workspace template has any columns from the PWA site we have to
re-connect them to the stp file. At least this seem to be the savest way
right now.

Let's hope that MS recognises the importance of moving data from one to
another environment without necessarily re-inventing the wheel every single
time you move systems. A true enterprise system should have this
functionality build in. Most serious organisations have a developement, test
and production environment and need to move data from one to another system
easliy. I can not comprehent that MS would miss such a most important
functionality. Never mind, lets hope the next release will be better in this
regard.
Take care
Marc

--
Marc Soester [MVP]
National Manager: EPM
http://marcsoester.blogspot.com

 

[ricardo.marques01]

Why can't Backup\Restore on Farm work for this?

 

[Marc Soester [MVP]]

Richardo, this function only works when you restore the image on the same
server where you backed it up from.

 

[Anna B]

Marc,

I am trying to move several workspaces from Production to Development environment. STSADM can backup and restore workspaces, but doesn't re-link URLs. You posted that in your company this step is manual. Could you please give more details?

Thank you,
Anna

You can move the data by making a SQL backup of the four Project Server
backups and the copy it over the newly created instance of project server.
Let me know if that works for you.


This question keeps popping up on this newsgroup, I wonder if someone could
put up a write up for this so that we can point everyone to it.

Regards,
Dave

On Tuesday, April 15, 2008 4:26 AM MarcSoesterMV wrote:
Hi Dave,

I think the reason why noone has written this up is because it is actaully
comlicated. Moving Projects is no big deal, but most companies want to move
their entire system ( including WSS). this is where the complication is. We
experienced many challanges moving a system from one to another server and
unfortunalty it is not straith forward and lots of manual stuff to think
about.

Having said this, it would be great if MS could publish a document which
outlines the steps as MS would recommend it.

--
Marc Soester [MVP]
National Manager: EPM
http://marcsoester.blogspot.com


"Dave" wrote:

 

[Anna B]

Marc,

I am trying to move several workspaces from Production to Development environment. STSADM can backup and restore workspaces, but doesn't re-link URLs. You posted that in your company this step is manual. Could you please give more details?

Thank you,
Anna

You can move the data by making a SQL backup of the four Project Server
backups and the copy it over the newly created instance of project server.
Let me know if that works for you.


This question keeps popping up on this newsgroup, I wonder if someone could
put up a write up for this so that we can point everyone to it.

Regards,
Dave

On Tuesday, April 15, 2008 4:26 AM MarcSoesterMV wrote:
Hi Dave,

I think the reason why noone has written this up is because it is actaully
comlicated. Moving Projects is no big deal, but most companies want to move
their entire system ( including WSS). this is where the complication is. We
experienced many challanges moving a system from one to another server and
unfortunalty it is not straith forward and lots of manual stuff to think
about.

Having said this, it would be great if MS could publish a document which
outlines the steps as MS would recommend it.

--
Marc Soester [MVP]
National Manager: EPM
http://marcsoester.blogspot.com


"Dave" wrote:

 

[Carl Dalton]

For MOPS2007 you can use the WSSSiteRelinker from here

http://technet.microsoft.com/en-us/library/cc197498(office.12).aspx

this should reattach the various URL's in the web app (content db) to
the MOPS published DB by pointing it to the relevant content db to
index against.