none
Extract your Project Web Access site from a content database to a new content database (Optional) RRS feed

Answers

  • Hi

    let us assume, you had in your 2007 Environment a web application with one Content database (what would be the Default).

    Then this Content database might contain more than just one site collection. You can check that in central Administration / manage Content databases.

    e.g. it might contain

    /
    /pwa
    /sites/site1
    /sites/site2
    /sites/searchcenter

    If you would now like to upgrade your /pwa to 2010 and take with you not only the Project data itself, but also the layout of the start page, some documents in the /pwa/shared documents library and also the Project workspaces with their data, you can either take the whole Content database with you to the 2010 farm and attach it. In that Case you would also migrate all the other sites to 2010. Or you could shift only the /pwa site to a separate Content database to take only that site with you over to 2010 and leave the rest where it is.

    Kind regards

    Christoph


    Christoph Muelder | Senior Consultant, MCSE, MCT | SOLVIN information management GmbH, Germany

    Saturday, February 2, 2013 3:50 PM

All replies

  • Hi,

    In Project Server 2010, 5 DB set was introduced in order to ease Admin's life when need to migrate PWA from one server to another. 

    In 2007 you could restore your 4 Project Server databases, then point your provision job at these 4 and you’d have a new PWA instance using those DBs.  If you wanted your workspaces too then you’d need to copy the sites or if you’d had the forethought to use a different web application for sites then it could be even easier.

    In 2010 MS has introduced the 5 dB restore –so you can now restore your Content database containing your PWA site (and potentially all your Project sites, and your 4 Project Server databases, attach the Content DB to a web application and then you can provision and it will use this PWA site and the databases – rather than complaining that the /PWA site already exists – which was the case in 2007.  So this is excellent – and makes it much easier to move a complete copy of the instance around.

    For more details, see the Brain Smith blog here. 

    The step you have pointed is required to extract your PWA content DB, to move your project sites to 2010 as well. you can ignore this step if you are not bothered about moving your Project Site + sites data to new provisioned PWA 2010.

    hope this helps.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )

    Thursday, January 31, 2013 7:26 AM
  • Hi

    let us assume, you had in your 2007 Environment a web application with one Content database (what would be the Default).

    Then this Content database might contain more than just one site collection. You can check that in central Administration / manage Content databases.

    e.g. it might contain

    /
    /pwa
    /sites/site1
    /sites/site2
    /sites/searchcenter

    If you would now like to upgrade your /pwa to 2010 and take with you not only the Project data itself, but also the layout of the start page, some documents in the /pwa/shared documents library and also the Project workspaces with their data, you can either take the whole Content database with you to the 2010 farm and attach it. In that Case you would also migrate all the other sites to 2010. Or you could shift only the /pwa site to a separate Content database to take only that site with you over to 2010 and leave the rest where it is.

    Kind regards

    Christoph


    Christoph Muelder | Senior Consultant, MCSE, MCT | SOLVIN information management GmbH, Germany

    Saturday, February 2, 2013 3:50 PM