Thread Details
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 355 subscribers
  • Views 979 views
  • Users 0 members are here
Forum Actions
Related

How to Update SugarCRM 9.0x to 11.0x

Manish kumar

Dear Helper Team,

I am using SugarCRM 9.0x Enterprise and want to update Latest 11.0x Ep How we can update please guide me for update to latest version.

We have 4 Instance 

1-Developer instance (Development coding purpose only )

2-UAT Instance ( after development code will test UAT)

3-Staging Instance (After UAT testing passed code moved to stating)

4- Main Production Instance (after stating final code testing code will move to production this is live instance)

All Instance are same replicas of  Production with single license.

I want To update my Developer instance as of now for all working functionality testing purpose if all current functionality will worked then i will update to all instance.

Question-1- if i update my development instance to 11.0x then is others instance working same version 9.0x or automatically updated.?

               2-is update all instance manually.?

              3- how we can update only my development instance 11.0x and other instance same as 9.0x as of now.?

              4-After testing how we can update all instance ?

              5-directly we can update 9.0x to 11.0.x ?
              6-We can degrade if we found any issue ?

Thanks.

Parents
  • 0

    There are some steps to follow on upgrading your instances:

    DEV

    Upgrade as per following upgrade packages:

    1. SugarEnt-Upgrade-9.0.3-to-10.0.0.zip
    2. SugarEnt-Upgrade-10.0.x-to-10.0.5.zip
    3. SugarEnt-Upgrade-10.0.5-to-11.0.2.zip

    Make sure DEV's source code is under GIT, so it is easier to track fixes on broken features after upgrading.

    Run test cases on upgraded DEV and apply the appropriate fixes if found issues.

    Make sure the fixes are committed into GIT

    UAT

    Upgrade the instance in order to get the upgraded database.

    git pull full code from DEV or only the fixes for upgrade related issues if UAT has no all DEV's features.

    Let users run UAT

    and so on

    Answering your questions:

    1. The instances are not synched unless you define it via DevOps
    2. Pretty much manual. At least for DEV it SHOULD be manual, so you can track any possible errors raised by packageScan. You can automate upgrading on other instances
    3. Answered above
    4. Answered above
    5. No! Answered above, there are 3 steps, or 4 if your instance is not on 9.0.3
    6. Make sure you have bkp of instance/database before upgrading it. It is not possible to downgrade it after upgrading.
    André Lopes
    Lampada Global
    Skype: andre.lampada
Reply
  • 0

    There are some steps to follow on upgrading your instances:

    DEV

    Upgrade as per following upgrade packages:

    1. SugarEnt-Upgrade-9.0.3-to-10.0.0.zip
    2. SugarEnt-Upgrade-10.0.x-to-10.0.5.zip
    3. SugarEnt-Upgrade-10.0.5-to-11.0.2.zip

    Make sure DEV's source code is under GIT, so it is easier to track fixes on broken features after upgrading.

    Run test cases on upgraded DEV and apply the appropriate fixes if found issues.

    Make sure the fixes are committed into GIT

    UAT

    Upgrade the instance in order to get the upgraded database.

    git pull full code from DEV or only the fixes for upgrade related issues if UAT has no all DEV's features.

    Let users run UAT

    and so on

    Answering your questions:

    1. The instances are not synched unless you define it via DevOps
    2. Pretty much manual. At least for DEV it SHOULD be manual, so you can track any possible errors raised by packageScan. You can automate upgrading on other instances
    3. Answered above
    4. Answered above
    5. No! Answered above, there are 3 steps, or 4 if your instance is not on 9.0.3
    6. Make sure you have bkp of instance/database before upgrading it. It is not possible to downgrade it after upgrading.
    André Lopes
    Lampada Global
    Skype: andre.lampada
Children
No Data