I need to replicate prod backup to my dev environment AX 20212

(3) Share

Report

Posted on by CU05031448-0

1,323

Dear team,

Before starting the development, I like import prod db to my dev environment. So, that I can start dev on latest data.

Once finished, can I get latest db+application?

Pls let me know the process to proceed.

Thanks in advance

Categories:

Microsoft Dynamics AX

I have the same question (0)

All responses (7)

Answers (1)

Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Talk to the administrator of the production environment. (S)he can create a backup of the database and provide necessarily changes to the data according to company policies. For example, addresses of integration endpoints needs to change from production ones and sensitive information about customers must be removed. Then you'll simply import the backup through SQL Server Management Studio.

If you copy the production data, you'll likely want to take the modelstore DB too, to avoid issues with object IDs. Customizations should be stored in source control and you'll get from there by using "Get latest".

Was this reply helpful? Yes No
CU05031448-0 1,323 on at

Like (0)

Report
Copy link

Link copied!

Thanks Martin for the response.

Kindly let me know what means application here? Is it model store?

Is I need to take backup of both db

Microsoft Dynamics AX and

Microsoft Dynamics AX _Model store ?

Then only I can get latest changes on my dev?

Kindly confirm pls

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

The application means things like tables, classes, forms etc. The data means record inside tables, such as customers and orders.

What exactly you should do depends on the deplyoment strategy of your company (or your implementation partner). You need to talk to responsible people on your project, not just to same strangers on internet. Taking both databases ensures that objects ID in the application and the database will match, but maybe you don't need to worry about it. It depends on your particular situation.

No, it won't give you latest code. It'll give you code that has already been deployed to production, but newer code may be in testing or development, and some code may not be deployed to production at all (such as automated tests). The latest code is in source control. If your company uses no source control, ask the head of development about processes followed in your company. We can't just guess your team works.

1 people found this reply helpful.

Was this reply helpful? Yes No
Sohaib Cheema 49,677 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

+

another point I would want to add is the Environment Specific settings. There are many parameter tables, that need change/update just after the database restore and before you turn on the AOS service.

Was this reply helpful? Yes No
Verified answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

To replicate your production backup to a development environment in Dynamics AX 2012, here’s a general process you can follow:

Backup Production Database:

Use SQL Server Management Studio (SSMS) to create a full backup of your production AX database.

Restore to Development Environment:

Restore the backup to your development SQL Server instance.

Ensure the database name matches your dev environment expectations or update the AOS configuration accordingly.

Update Configuration:

In AX 2012, update the SYSSERVERCONFIG and SYSCONFIGURATION tables to reflect the dev AOS instance.

Clear cached data like SysLastValue and SysSetupLog if needed.

Recompile and Synchronize:

Open AX client in dev and perform a full compile.

Run database synchronization to ensure schema alignment.

Update Service Accounts and URLs:

Update any service account references, email settings, or URLs that point to production.

Application Layer:

If you also need the latest application layer (code), export the modelstore from production and import it into dev using AXUtil or PowerShell.

Security and Licensing:

Ensure dev environment uses appropriate licenses and restricts access to sensitive production data.

Please verify if this helps you proceed with the environment setup.

Thanks and best regards,

Daniele

Note: This response was prepared with support from Copilot to ensure clarity and completeness.

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
The AI-generated reply was marked as an answer, but many parts are actually quite misleading. Use it with care; AI bots don't really understand the intricacy of things.

For example:

It ignores object IDs and the impact of your deployment strategy on how you can safely restore the database. The process described below would likely cause problems with object IDs in the transactional database not matching IDs in the modelstore database.

It doesn't discuss sensitive customer data. Remember GDPR, for example. This may have serious consequences.

It tells you to update tables like SysServerConfig but not how you should update them and when it's needed at all.

It suggests copying modelstore with AXUtil, but if you want the modelstore DB, you could simply backup and restore it together with AxDB.

It tells you to compile code and then restore the modelstore, which makes no sense.

It tells you to first run the environment and only then updating URL pointing to production systems and such things. At that point, damage might have already been done. This needs to be handled before starting AX.

Was this reply helpful? Yes No
Sagar121 1,160 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Do you need anything here?

Was this reply helpful? Yes No