none
Conflcits on creating a new PWA instance with old pwa data on a new web application on the same server RRS feed

  • Question

  • Hi ,

    We are planning to create new PWA instance to segregate different projects.

    Conflicts on creating a new PWA instance with old pwa data on a new web application on the same server. We don't want to un provision the old pwa also.

    Then we want to delete unwanted projects in old and new PWA instances. T


    Ram

    Tuesday, October 15, 2013 12:22 PM

All replies

  • Hello Ram,

    No, you wont be able to do this , since each side collection has unique ID in the SharePoint farm. When you backup and restoring existing content database to another web application keeping old content database active, all old site collection will be hidden and  sites will be made available via new web application.

    Only way is to build test farm perform your segregation , and use DB attach method to update  production site.


    Hrishi Deshpande Senior Consultant

    Tuesday, October 15, 2013 10:22 PM
    Moderator
  • After segregating the two PWA's, If we move two PWA's to Production site then also there will be same content db and Project Server 4 db's right. But some projects will be deleted in each PWA.

    Do we face any issues.


    Ram

    Monday, October 21, 2013 9:45 AM
  • Any suggestions please

    Ram

    Friday, November 8, 2013 9:59 AM
  • Hi

    You can export the site collection and import it to a different web-application. In this way site collection ID will be changed.

    Then you can use this imported site collection to provision the PWA.

    Friday, November 8, 2013 12:26 PM