locked
WSS 3.0 migration to MOSS 2007 RRS feed

  • Question

  • Hi,

        I have been assigned a task for migrating WSS 3.0 to MOSS 2007. Actually, we have 6 web applications in WSS 3.0.  Also I have to migrate the databases from SQL 2005 to SQL 2008.

        I am also worried weather version mismatch can create any problem for the upgrade? Should I apply the same patches to both wss 3.0 and MOSS 2007 before upgrading them? Does the same thing apply to the SQL Server? At the time of installing MOSS, should I have to create a config database again? Also Should I take any precautions before doing this task?

        I would really appreciate if anyone can provide me a steps for doing this.

    Thanks,
    Sam.
    • Edited by Mike Walsh FIN Friday, July 24, 2009 6:32 AM " " removed from around the Title. They should be used only when quoting an error message
    Thursday, July 23, 2009 11:56 PM

Answers

  • Hello,

    Have you seen these instructions?  http://technet.microsoft.com/en-us/library/cc262342.aspx

    If you are upgrading on the same server or a farm you will use the same configdb that already exists for WSS 3.0.  As Andre says you should test before you do anything.  Also make sure you have everything backed up. 

    Regarding your performance and Windows 2008 OS.  If you are planning on changing the OS as well I would recommend that you upgrade to 64-bit if you are not already using it.  This is where you will see the most performance increase.

    Thanks,

    Aseem Nayar – MSFT


    This posting is provided "AS IS" with no warranties, and confers no rights
    Friday, July 24, 2009 8:18 PM
  • Also, check out this page to help you choose an upgrade path:  http://technet.microsoft.com/en-us/library/cc263447.aspx  It has a nice matrix with a breakdown of pros and cons of various migration paths.

    Read as much as you can on the topic before you start the work; it's not always a fun task, but it'll help you make the right decisions down the road.
    Andre Galitsky, MS-Certified SharePoint Administrator, Lexington, KY -- My SharePoint Blog: http://www.sharepointnomad.com
    Saturday, July 25, 2009 2:36 PM
  • Hi,

     

    you need not to perform step 2 to create subsites in the MOSS 2007, because these site are in the content databases, once the content databases were attached in the MOSS 2007, the old sites could be reused in MOSS 2007.

     

    I suppose you were building a new farm, the step 3 is also optional.

     

    To your last two questions, you need first backup your content database using SQL Server, then you could restore the backup with another name, it would not affect your original WSS 3.0 farm.

     

    It is suggested to do a trail migration before implementing in your production server.

     

    See Deploy new server farm and migrate content (http://technet.microsoft.com/en-us/library/cc303436.aspx) for more information.

     

     

    Hope the information can be helpful.

    -lambert


    Sincerely,
    Lambert Qin | Microsoft TechNet Managed Forum Support
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, July 30, 2009 2:32 AM

All replies

  • In order to successfully complete this project, you will first need to do some research on available migration options and create a migration plan that will work for you and your environment.  A good place to start would be this MS SharePoint Server TechCenter site:

    http://technet.microsoft.com/en-us/library/cc303420.aspx

    The next step would be to create a Test instance of your production environment.  Try to replicate your Prod settings and configuration as closely as possible, including user accounts, security updates, app instances, etc.   (Creating a virtual clone of the production box works really well.) Then you'll be able to simulate your upgrade in a Test environment without breaking anything important.  After the upgrade, perform thorough QA testing to ensure that all of your web apps are functioning correctly.

    A few more thoughts:  Install all latest MS patches and updates before you start the migration.  Migrate from WSS to MOSS first, then update SQL 2005 to SQL 2008.  Create (and test) backups for every site collection and application that will be migrated.  MOSS requires a number of new databases to be created, so plan accordingly and make sure that you have the database server infrastructure to support it.  Above all, go slow, backup everything, and test your work.
    Andre Galitsky, MS-Certified SharePoint Administrator, Lexington, KY -- My SharePoint Blog: http://www.sharepointnomad.com
    Friday, July 24, 2009 4:17 PM
  • Hi Andre,

                 Thanks for the reply. As you know we have sql 2005 with WSS 3.0 and we are upgrading it to MOSS 2007 with sql 2008. Actually I have 3 scenarios.

    1) If I Install the MOSS 2007 over wss 3.0 on the same server, then at the time of installing MOSS, will it ask me for the Config database name? if so then what name should I give? Should I have to use the same config database name of wss 3.0?

    2) If I go for a new farm, then should I use the same name of config database at the time of MOSS installation or different one? Should I go for SQL 2008 directly in this scenario?

    Among these 2 scenario, which one is the better one?

    3) Right now, we are using windows 2003 operating system, we are also looking at the option of windows 2008 OS. will it improve the performance? So according to you, we should go for this option at this stage or we can do it later on after upgrading wss 3.0 to MOSS. will tis option cause any problems for us in upgrade process.

    I would really appreciate your help in resolving this task.

    Thanks,
    Sam.
    Friday, July 24, 2009 7:24 PM
  • Hello,

    Have you seen these instructions?  http://technet.microsoft.com/en-us/library/cc262342.aspx

    If you are upgrading on the same server or a farm you will use the same configdb that already exists for WSS 3.0.  As Andre says you should test before you do anything.  Also make sure you have everything backed up. 

    Regarding your performance and Windows 2008 OS.  If you are planning on changing the OS as well I would recommend that you upgrade to 64-bit if you are not already using it.  This is where you will see the most performance increase.

    Thanks,

    Aseem Nayar – MSFT


    This posting is provided "AS IS" with no warranties, and confers no rights
    Friday, July 24, 2009 8:18 PM
  • Also, check out this page to help you choose an upgrade path:  http://technet.microsoft.com/en-us/library/cc263447.aspx  It has a nice matrix with a breakdown of pros and cons of various migration paths.

    Read as much as you can on the topic before you start the work; it's not always a fun task, but it'll help you make the right decisions down the road.
    Andre Galitsky, MS-Certified SharePoint Administrator, Lexington, KY -- My SharePoint Blog: http://www.sharepointnomad.com
    Saturday, July 25, 2009 2:36 PM
  • Thanks Andre/Aseem for the reply.

    If I go for new Hardware and use the database migration approach then here I am giving the steps which i will follow. Can you please check them and let me know if I miss anything?
     
    1) create all the web applications under MOSS 2007 manually with the same names as in WSS 3.0.
    2) each web application has some subsites so I will also create all these subsites manually in MOSS 2007.
    3) Delete the content databases attached to the web applications in WSS 3.0.
    3) Attach the content database with the same names as in WSS 3.0 to the web applications of MOSS 2007 and delete the content databases which will be created during the web application creation under MOSS 2007.

            I have one question here. If for some reason, this doesn't work then how can I attach these databases back to the WSS 3.0 ? is stsadm utility supported by WSS 3.0 properly?or, Should I copy all the WSS content databases with different names and then attach it to MOSS? Does it work?

            If possible can you please provide me the steps for this?

            Also, right now our WSS is running under 2 Quad Core processor so for MOSS, will it work fine?

    Please Advise.

    Thanks,
    Sam

    • Edited by srpatel Monday, July 27, 2009 7:12 PM correction
    Monday, July 27, 2009 7:02 PM
  • Hi,

     

    you need not to perform step 2 to create subsites in the MOSS 2007, because these site are in the content databases, once the content databases were attached in the MOSS 2007, the old sites could be reused in MOSS 2007.

     

    I suppose you were building a new farm, the step 3 is also optional.

     

    To your last two questions, you need first backup your content database using SQL Server, then you could restore the backup with another name, it would not affect your original WSS 3.0 farm.

     

    It is suggested to do a trail migration before implementing in your production server.

     

    See Deploy new server farm and migrate content (http://technet.microsoft.com/en-us/library/cc303436.aspx) for more information.

     

     

    Hope the information can be helpful.

    -lambert


    Sincerely,
    Lambert Qin | Microsoft TechNet Managed Forum Support
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, July 30, 2009 2:32 AM