Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Roll back methodology ...
Microsoft Dynamics AX (Archived)

Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

We would like to understand the approach and process of Roll back CU update in Production.

 

We are planning to upgrade our current AX application from AX2012 R3 RTM to CU13 and want to understand- what should be our approach for roll back of the application in Production if any issue.

 

I have looked at CU13 Installation guide but roll back option is not documented. Attached the installation update document for your reference.

 

Kindly provide your support and help in understanding.

*This post is locked for comments

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,156 on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    You can discuss with your (customer's) IT about the server backups. It's not something that's expected or even allowed to be done by the AX partner.

    But they can take a snapshot of the servers before you start the upgrade. And if something goes wrong during the update, the servers can be rolled back to the snapshot. But please take the snapshot only after AOSes and SQL Server service have been stopped, to minimize risk of any issues during rollback.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    Thanks Andre for the reply.

    I have tried to install just Kernel update on AX2012 R3 RTM server and tried to uninstall. It has deleted Client and Server from that dev box. So I am worried to uninstall kernel update from Computer & Programs otherwise we will have to re-install Client and Server both and it may require many works after that. I am worried to do these steps in Production if it required at any point.

    Not sure- how is the option to take full server back up and revert if needed. I have never done that.

    what is the recommended approach, can you pls suggest and share your experience.

    Thanks.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,269 Super User 2024 Season 2 on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    Hi Ajay,

    I have seen an option in the past to remove installed updates of the kernel software using the Program and Features form. Probably, you need to switch a certain view or it is not supported anymore. I had seen it on AX 2012 R2. Otherwise, it needs to be fully uninstalled and setup again. Or create PC/Server images before doing the update. But I don't have experience with the last mentioned option.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    Thanks Andre for the reply. I meant of Roll back is Back out plan. If something goes wrong during Upgrade process, how to bring the system back to previous version.

    Based on the comment, what I understood is, If we uninstall Binary from Windows->Program and Feature, this might uninstall AX Client and Server from application server and we should have AX2012 R3 Installation disk to reinstall.

    Hope, this will help you.

    Thanks,

    Ajay

  • nmaenpaa Profile Picture
    nmaenpaa 101,156 on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    Updates of binary components (AOS, client etc) can't be uninstalled. So, like Andre wrote, you would need to uninstall all components except Database, then reinstall the old version. And finally restore (pre-update) backup of model and business databases.

    Rolling back a CU is not something that you should normally do. You should test the update thoroughly in a test system to avoid any issues. In prod, rolling back will always mean losing all data that was created after the update.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,269 Super User 2024 Season 2 on at
    RE: Roll back methodology after CU Update from AX2012 R3 RTM to CU13 in Production

    Hi AJ1983,

    I might miss something in my reply, so test everything in a separate environment first.

    - Make sure you have an additional backup of the business database and model database.

    - Ensure you have setup media available to be able to re-install the client and server components (might not be needed, but for more serious issues)

    To limit the risk, first update one AOS with one client (might be on this AOS) and see if also the database update is correct.

    If something happens, you can stop all AOS services (if already running). Then use the Windows features to remove updates on the clients and the AOS machines. Then also restore the backup of the business and model databases and restart the AOS machines.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans