locked
Sharepoint 2010 upgrade approach ? RRS feed

  • Question

  • Hi all, i have this question about our planned SP 2010 Upgrade approach:

    1. We have two new Windows 2008 R2 Servers - WFE2010 , DB2010.
    2. DB2010 is where we have SQL server 2008 R2 and WFE2010 is where we installed SP 2010,  WFE2010 is pointing to DB2010 - these 2 servers constitute our SP 2010 Farm.
    3. We got a database backup from the existing production SP 2007 farm and attached it to a web app in SP 2010 farm(WFE2010 and DB2010) thru Database attach upgrade method. We call this web app as UatWebApp
    4. Added all the customizations : in-house solutions , 3rd party solutions
    5. We made this  new SP 2010 farm as UAT env temporarily so that we our Users can test it thoroughly and we can fix them.
    6. Once UAT is done, our plan is to :
     a. create a new Web App in the SP 2010 farm called ProdWebApp
     b. get the latest database backup from the SP 2007 farm
     c. Attach it to ProdWebApp  thru Database Attach Upgrade method
     d. Associate this ProdWebApp with all the service applications that were originally associated with UAT web app.
     e. Deploy all the customizations and fixes to ProdWebApp
     f. Release this as our new SP 2010 Prod env

    Please let me know if you see any flaws in this procedure ?

    Thanks in Advance,
    Santosh.

    Wednesday, May 16, 2012 1:12 AM

Answers

All replies

  • Good!
    Wednesday, May 16, 2012 3:51 AM
  • yeah, all the steps you said is perfect
    • Marked as answer by dotnetchef Tuesday, June 5, 2012 7:17 PM
    Wednesday, May 16, 2012 6:20 AM
  • The one thing that strikes me as missing is you haven't mentioned running the "stsadm -o preupgradecheck" command on your 2007 environment to pre-empt any issues


    Paul Turner http://redmanta.co.uk/blog Twitter: @RedMantaUK MCTS:WSS,MOSS,2010 MCITP:2010.
    Please remember to click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.

    Wednesday, May 16, 2012 7:31 AM
  • Hi Paul, pre-upgrade check was done - i forgot to mention it above.  Thanks to everyone for taking time to read my question and respond.

    Thanks,
    Santosh.

    Wednesday, May 16, 2012 2:43 PM
  • Please Mark this post As Helpful if it was useful.
    Friday, May 18, 2012 4:00 AM
  • Hi all, just one more question before i mark as answered - in the above steps what if i change the step 6 as:
    Once UAT is done, our plan is to :
    a. Remove the existing content db attached to UatWebApp
    b. get the latest database backup from the SP 2007 farm 
    c. Attach it to UatWebApp thru Database Attach Upgrade method
    d. change the UatWebApp name to ProdWebApp or add an alias name to it and release it as our new SP 2010 Prod env

    in this way by re-using the existing web App, we are expecting that we don't need to re-deploy custom solutions as dlls are already in GAC and web.config
    refers them as part of earlier deployment. How does this plan sounds?

    Thanks Again,
    Santosh.
    Friday, May 18, 2012 3:09 PM