Microsoft Dynamics CRM (Archived)

copy Production database to Test

(0) Share

Report

Posted on by RamKumarb

828

Hi Everyone,

im trying to set up a new Test environment for CRM 2016 on-premises,

i need to copy the users , customization , reports and everything in Production database (Prod_CRM) to Test .

is it a good approach to backup Prod_CRM database from Production sql server and restore the same in Test database in Test Server and use deployment manager to import ?

should i have to do the same for MSCRM_Config database (Since it contains some setting for dynamics CRM) ?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi Ram,

Yes, your understanding is correct. You need to take a back of prod and then use import organization in deployment manager. MSCRM_Config is the deployment database common for your entire crm deployment. You don't need to do anything on this.

You can refer the below article, its old but still holds true-

www.crmcodex.com/.../how-to-backup-and-redeploy-an-organisations-database

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Hi Ram,

That would be the correct approach.

You don't need to backup/restore the Config database. That will already exist in your Test environment and any information from the database that you import will be configured there.

Backup your production DB, Restore in SQL on Test and use deployment manager. Although not required, I would restore the database using a different name. For example if you production is CRM_MSCRM, restore it as CRMTest_MSCRM. Also with deployment manager use CRMTest as the name of the database (display name does not matter).

This is also important if you are using IFD to keep names different between the instances.

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi Ram,

Your understanding is correct , few clarification -

If you are using same server creating new organization then you don't need to worry about config database you can use same config database. You just need to restore MSCRM DB in different name and pointing to the MSCRM DB import the organization. You also don't need to worry about all users ,customization , reports everything will be move new organization.

If you have completely different environment for Application or DB server , then you need to have another CRM instance where you need to restore both the database.And using Deployment manager imort the Organization DB. You might be face some challenges to map all the users if you are not using same AD. Also you need to point the separate report server at the time of organization import and off course everything will be moved in new test instance.

Was this reply helpful? Yes No
ngetz 145 on at

Like (0)

Report

What about the OrganizationID in the config database? Shouldn't we change it in MSCRM DB and if so, import a new config database and update it there as well?

Was this reply helpful? Yes No