CRM Backup and Re-deploy

I have three CRM servers: dev, stage and prod.
I am currently live with prod and would like to reset the dev and stage to what Prod currently is. I have tried moving the DB’s around and importing a new organization to no avail. I have used the attached document and followed it exactly. This is important for our disaster recovery plan as well.
So what is the best way to take a CRM system and move it to different machines (clean SQL 2008 and clean install of CRM using existing or new).
I am using CRM 4.0 Professional .

I tried this:

1. Install Windows Server 2003 or Windows Server 2008, and make sure that the computer is in the same domain as the Microsoft Dynamics CRM Server. In addition, you should use the same database name and disk structure. If you change either of these, you must take additional steps to correctly restore the SQL Server databases.

6. If Microsoft SQL Server Reporting Services and the Microsoft Dynamics CRM 4.0 Connector for Microsoft SQL Server Reporting Services are also installed on the instance of SQL Server, restore the ReportServer and ReportServertempDB databases. For more information about how to restore databases, see Backing Up and Restoring Databases (http://go.microsoft.com/fwlink/?linkid=100249).

7. If you restored the MSCRM_CONFIG database, you must run Microsoft Dynamics CRM Server Setup and use the Connect to existing databases option on the Specify Deployment Options page. If you did not restore the MSCRM_CONFIG database and the database is functioning correctly, you use the Import Organization feature in Microsoft Dynamics CRM Deployment Manager to reassociate the organization database with the Microsoft Dynamics CRM system. For more information about how to import an organization, see the Deployment Manager Help.

I get an Invalid User ID even witha the administrators account I ran the install under. The account is a domain admin with local admin righs.

In that case, on the dev and stage computers I would delete the CRM organizations in the CRM deployment manager, then delete the relevant databases on the SQL servers (but not the MSCRM_CONFIG database,

All servers are set up the same. They are all seperate machines (VMs) running on a server. The setups should all be the same. Basic run through the wizards. Nothing special out of the box. Each server has a single instance (tenant) running on them. All SQL versions are the same, 2008 SP1.

In that case, on the dev and stage computers I would delete the CRM organizations in the CRM deployment manager, then delete the relevant databases on the SQL servers (but not the MSCRM_CONFIG database, only the database that corresponds to the organization).

Then
- on the production server, backup the CRM organization database in SQL server
- restore that backup to the SQL Servers for dev and stage.
- on dev and stage, import the newly restored organization database using the Deployment Manager

That should give a duplicate of the production database on dev and stage.

If you have items outside the CRM database (e.g. plug-ins) then you will need to copy those over too.

Featured Post

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

This is a walkthrough guide I wrote whilst upgrading my on-premise MS Dynamics CRM 3.0 deployment to 4.0. This covers the actual installation of the product to a working level for my system, I ran into a lot of issues that the steps below fixed so h…