none
Services in Farm and Migration to 2010 RRS feed

  • Question

  • Hi,

    I am using Project Server2007 with SharePoint 2007 and SQL server 2008 r2 on multi server farm.

    My Farm has:
            2 web servers,
            1 project server,
            1 SharePoint central administration server,
            1 search server and a Database Server.

    I am running ‘Windows SharePoint Services Web Application’ services only on my 2 web servers and am not running on SharePoint Server. Is it right? And when I will perform migration to 2010, on which server will I first run the SharePoint Wizard?

    I appreciate your help.

    Thanks!

    Tuesday, December 11, 2012 7:31 PM

Answers

  • Hi there,

    I would recommend building a new 2010 farm and using a database attach upgrade approach:

    http://technet.microsoft.com/en-us/library/ee662500(v=office.14).aspx

    Regarding the Windows SharePoint Services Web Application service, Central Admin doesn't need it but it depends what else you have running on that server.

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, December 11, 2012 8:43 PM
    Moderator
  • Only reason people afraid of in-place upgrade is because of unknown issues which might surface during upgrade process which could be show stopper. To move forward you have to resolve each identified issue, which eventually delays entire process. Also we wont have a leverage to roll back instantly if something goes wrong.

    You could rebuild your SP2 farm with SharePoint 2010 , perform db attach migration , provide access to UAT tester and once all is well, rebuild existing production SharePoint 2007 with 2010 for db attach method. Make sure that you have Full Farm and DB backup. Also if you have any custom solutions or web parts have complete documentation and package ready in case of roll back.

    If you are using virtualized farm app, wfe and db server then make sure to take snapshot at the same time.

    Hope this helps


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Tuesday, December 18, 2012 6:31 PM
    Moderator

All replies

  • Hi there,

    From what you have said, I take it you are running an in-place upgrade? If so, you run the Wizard on the Server that hosts Central Admin first then on the other servers. See this guide:

    http://technet.microsoft.com/en-us/library/ee662104(v=office.14).aspx

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, December 11, 2012 8:22 PM
    Moderator
  • Hi there,

    If you have migrating from 2007 to 2010, then most preferable method is db attach method. Are you planning to perform in-place upgrade?


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Tuesday, December 11, 2012 8:29 PM
    Moderator
  • Thanks Paul for your response,

    Yes, I am planning in-place upgrade.

    Could you also inform me whether i need to run ‘Windows SharePoint Services Web Application’ services on the server that hosts Central Administration? 

    Thanks!

    Tuesday, December 11, 2012 8:30 PM
  • Hi there,

    I would recommend building a new 2010 farm and using a database attach upgrade approach:

    http://technet.microsoft.com/en-us/library/ee662500(v=office.14).aspx

    Regarding the Windows SharePoint Services Web Application service, Central Admin doesn't need it but it depends what else you have running on that server.

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, December 11, 2012 8:43 PM
    Moderator
  • Thanks Paul and Hrishi four suggestion.

    In my farm, I already have SharePoint with sp2 which is needed for migration. Can you please inform me what are the potential threads if I perform in-place migration.

    What if I deploy the farm in UAT as a backup and perform migration in Production environment?

    Tuesday, December 18, 2012 6:23 PM
  • Only reason people afraid of in-place upgrade is because of unknown issues which might surface during upgrade process which could be show stopper. To move forward you have to resolve each identified issue, which eventually delays entire process. Also we wont have a leverage to roll back instantly if something goes wrong.

    You could rebuild your SP2 farm with SharePoint 2010 , perform db attach migration , provide access to UAT tester and once all is well, rebuild existing production SharePoint 2007 with 2010 for db attach method. Make sure that you have Full Farm and DB backup. Also if you have any custom solutions or web parts have complete documentation and package ready in case of roll back.

    If you are using virtualized farm app, wfe and db server then make sure to take snapshot at the same time.

    Hope this helps


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Tuesday, December 18, 2012 6:31 PM
    Moderator
  • I am prefering In-Place migration because my content Db has more than 100,000 workspaces which takes 48 hours only to attach the Content DB. This cost of 2 days is too much acn can be avoided on in place-migration. I would definitely consider imaging the physical servers before migration. thanks for your responses! :)
    Thursday, February 7, 2013 12:49 AM