locked
CRM 4.0 Upgrade Planning Question RRS feed

  • Question

  • Hello CRM experts,


    We're on CRM 3.0 and planning on upgrading to CRM 4.0 very soon. We have laid out the upgrade plan as follow, and we would like your input if the upgrade plan is sustainable in our environment.

    Basically the process is to build up a 'test CRM 4.0' in our domain where we can test all CRM 4.0 functionalities and see if all add-ons work correctly. During this 'test', we want the CRM 3.0 server to stay online to serve all users while the upgrade is in progress, also in case there are any problems with the 4.0 upgrade.

    Our upgrade step:
    1. Backup CRM 3.0 database.
    2. Install CRM 3.0 on a vmware environment.
    3. Upgrade CRM 3.0 on that vmware environment to CRM 4.0.
    4. Install CRM 4.0 on a new CRM server (that is going to be our new production CRM 4.0 server)
    5. Restore the CRM 4.0 database from vmware to this new CRM server.

    A few questions about this:
    1. In this upgrade plan, we will have 2 online CRM server: the CRM 3.0 that will be available during the upgrade process, and the test CRM 4.0. Will there be any problems with these two CRM servers online at the same time?

    2. Our vmware environment is on a separate domain from our production, which is in the test domain. Would there be any problems (such as user mapping, etc) created by this? Or is it safer to make the vmware environment together with the production domain?

    Thank you very much for your help in this, much appreciated.

     

    -Elizabeth K.


    • Edited by kurobenko Tuesday, February 16, 2010 8:19 PM
    Tuesday, February 16, 2010 7:34 PM

Answers

  • Hi Eliszabeth,

    1. No, but if both are online at the same time and the v3 system is productive, the two databases will be in a different state, as your users work on the v3 system. So I would recommend to test the upgrade, addons, ... on the test system. If everything is fine, make a new upgrade with the old system. This depends on the decision whether you need the data which is entered in the mean time.

    2. There is absolutely no problem. You have to redeploy the old system in the new environment.

    For a basic upgrade path, see [1]

    • Marked as answer by Jim Glass Jr Wednesday, February 17, 2010 7:07 PM
    Tuesday, February 16, 2010 8:07 PM

All replies

  • Hi Eliszabeth,

    1. No, but if both are online at the same time and the v3 system is productive, the two databases will be in a different state, as your users work on the v3 system. So I would recommend to test the upgrade, addons, ... on the test system. If everything is fine, make a new upgrade with the old system. This depends on the decision whether you need the data which is entered in the mean time.

    2. There is absolutely no problem. You have to redeploy the old system in the new environment.

    For a basic upgrade path, see [1]

    • Marked as answer by Jim Glass Jr Wednesday, February 17, 2010 7:07 PM
    Tuesday, February 16, 2010 8:07 PM
  • ckeller, thanks for your quick response!

    Sorry I didn't put the final upgrade plan for this; when everything else is done, we're going to redeploy everything from the CRM 3.0 production, back to vmware to be upgraded, and then to CRM 4.0 production.

    So basically the full upgrade plan would be:

    Phase A: Preparing New CRM 4.0 server
    1. Backup CRM 3.0 database.
    2. Install CRM 3.0 on a vmware environment.
    3. Upgrade CRM 3.0 on that vmware environment to CRM 4.0.
    4. Install CRM 4.0 on a new CRM server (that is going to be our new production CRM 4.0 server)
    5. Restore the CRM 4.0 database from vmware to this new CRM server.
    6. Testing with CRM 4.0 server (Add-on, Outlook-CRM client, etc).
    7. 100% ready with the upgrade (this probably will take 1-2 weeks).
        And then we redo everything from the start again, but this time everything else will be ready. Then we move to the next phase:

    Phase B: Complete CRM 4.0 Restore
    8. Backup the more updated CRM 3.0 database (this must be done when no users on the production system).
    9. Upgrade the CRM 3.0 database on VMWare to version 4.0.
    10. Restore the CRM 4.0 database from VMware to the 100% ready CRM 4.0 server.

    I know there are many repetitions in this upgrade process, as in this upgrade plan we're trying to do the CRM 4.0 upgrade with the minimal downtime, as they might be problems with the CRM add-ons, clients, etc. That's why we make it into two phases.

    Thanks so much for your input in this, much appreciated!

    -Elizabeth K.

    Tuesday, February 16, 2010 8:19 PM
  • Hi Elizabeth,

    from my point of view, you upgrade plan looks good. 
    We use mostly the same approach when upgrading systems of our customers.
    Tuesday, February 16, 2010 8:23 PM
  • THe only  recommendation I can add is to perhaps do all in the same domain.  If you have dozens of users it will save you time as you will not have to 'remap' the users.  We have had minor 'glitches' remapping the users, but nothing major.  Everything else looks very similar the way we do upgrades.
    Alex Fagundes - www.PowerObjects.com
    Wednesday, February 17, 2010 4:39 AM
  • Thank you for your inputs ckeller and Alex! Seems like we're not going on this route since having two instances of CRM on same domain and same SQL server might slow the performance.. we're still looking for a more sustainable way now..

    Appreciate your help in this :)
    Wednesday, February 17, 2010 5:03 PM