none
Extract PWA Site content to a new content database RRS feed

  • Question

  • I am somewhat confused by the steps here http://technet.microsoft.com/en-us/library/ee662500.aspx which outline the process to extract each 2007 PWA instance's content into its own content database in preparation for upgrading to Proj Server 2010. My intent is to have each PWA instance (http://server/program1, http://server/program2, ...) associated with its own content database. I am doing this in preparation for moving to new hardware and upgrading the system to Windows 2008 and SQL 2008. Later I will move to 2010 and I just want to separate the instances from the common content database now.

    After following those instructions I go look at the site collection list (Central Admin > App Management) and see no difference in the content dbs for any PWA instance.

    Following the steps, I backup one instance (http://server/program1). I then create a new web application using port 82 (http://server:82. Then I create a new content database in the new web application. Now that web application has 2 databases (one created in the process of creating the web app and the one created just now).

    The last step (?) is to restore the site collection backup from the first step to the second (ie new) web app on port 82. So I did that.

    This all happened with no errors. But what should I see because nothing seems any different than before? What is the step or process to associate the PWA instance (http://server/program1) with its own content database?

    Monday, August 1, 2011 9:28 PM

Answers

  • I haven't tried this, so make sure you test this on a non prod environment.

    You may be able to take your existing contentdb offline and detach and then attach your new split out contentdb to the web app. Project Server may then be able to pick up the /program1 site collection and all is good.

    HOWEVER, what you can't do is a reprovision a new PWA instance with your new contentdb being picked up for the /program1 pwa site as 2007 doesn't support this. You would have to create a new PWA instance :(

    As for the comingling of data. All your project related information will be isolated by virtue that you have created two PWA instances each with it's set of 4 x Project DB's. Only the SharePoint components will be in the same contentdb, and the SP security model will ensure security isolation. Of course, the splitting of contentdb makes perfect sense from a recoverability / disaster recovery perspective.

    Hope this helps,

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    • Marked as answer by Quized again Monday, August 1, 2011 11:05 PM
    Monday, August 1, 2011 11:01 PM
    Moderator

All replies

  • Hi,

    So these steps are to move your /program1 /program2 PWA sites out of a single contentdb into seperate contentdb's. After following the steps you outlined you should see that you now have /program1 in its own contentdb and program2 in the original (you can delete the program1 from this contentdb once you are happy you have restored it without issue).

    All you have really achieved is to move a copy of the data around in preparation for doing a 5 db attach when you go to 2010. You haven't reassociated anything within the existing PWA instances on your production environment, so the new contentdb's are just superflous at the moment. I typically don't do these type of moves until I am actually doing the migration. Moving an instance to a different web app requires testing and potentially end user communication.

    Does this make sense?

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Monday, August 1, 2011 9:51 PM
    Moderator
  • Thanks Alex! I think I underastand most of your answer. I do not see that /program1 is in its own contentdb, but maybe I am not looking at the correct thing. How do I tell that? As you mentioned in paragraph 2, the new content db seems to be just sitting there. Looking at site collection list for /program1 still shows the old content db.

    But now I understand that using these steps that the process is not completed until the actual migration is completed. Could this be accomplished in 2007 without final migration? Say I have a program that does not want to comingle data?

    I appreciate your time and help.

    Monday, August 1, 2011 10:14 PM
  • I haven't tried this, so make sure you test this on a non prod environment.

    You may be able to take your existing contentdb offline and detach and then attach your new split out contentdb to the web app. Project Server may then be able to pick up the /program1 site collection and all is good.

    HOWEVER, what you can't do is a reprovision a new PWA instance with your new contentdb being picked up for the /program1 pwa site as 2007 doesn't support this. You would have to create a new PWA instance :(

    As for the comingling of data. All your project related information will be isolated by virtue that you have created two PWA instances each with it's set of 4 x Project DB's. Only the SharePoint components will be in the same contentdb, and the SP security model will ensure security isolation. Of course, the splitting of contentdb makes perfect sense from a recoverability / disaster recovery perspective.

    Hope this helps,

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    • Marked as answer by Quized again Monday, August 1, 2011 11:05 PM
    Monday, August 1, 2011 11:01 PM
    Moderator