Dynamics Community Forum Thread Details

Cloning a production environment

We have an environment where application modifications are supposed to move from a DEV environment to UAT environment to PROD.

I've discovered that our DEV environment is not up to date. In act it is an older version of GP that we do not use.

How can I safely clone the production environment to development? I would like to have to prevent installing all of the software, third party tools and customizations all over again for numerous reasons. We have a dedicated database server for each environment. I know how to move and restore the databases to different servers, but once we clone the application server to DEV, what steps should be taken to point everything the DEV database server?

Once you get the DEV database server configured with the GP databases and GP login information, the application server, as far as Dynamics GP goes, it's much as far as setup, though I don't know what third party and customizations you have.

For Dynamics GP, it would just be a matter of getting Dynamics GP at the same exact version/build as your GP databases are currently on, with the same modules/features installed.

The ODBC DSN would be configured to point to the correct DEV database server/SQL instance where the GP databases exist.

If you're cloning an existing production server, I'd recommend verifying what I mentioned with the GP instance's version/build and that the ODBC DSN is pointing to the correct SQL instance.

I'm sure others on the Forums have more information on cloning an environment they can share.

Thanks

Quick Links

Leaderboard