Refreshing Dev and Test with a snapshot of Production

I am fairly new to TeamSite administration (mostly have been working with form development). Recently we took a tactical approach to redesigning our website and only made changes in Prod. I now want to come back and refresh our dev and test enviornments with a snapshot of our production server, but I am not sure about the correct way to go about this.

A few things I was thinking were:
1. Make a backup of Prod and then restore it into Test and Dev.
- Not sure if this will cause conflicts with hardcoded server names or anything like that

2. Migrate a recent edition of our site over to dev and test
- I dont think this will work because it just moves content, not all of the config files right?

3. Go through the backend and copy all of the files and folders over from Prod to test and dev

This is a one time thing to sync the enviorments and I am not looking for the exact steps, just highlevel overview to research.

thanks,
Brett

Find more posts tagged with

Comments

santosh013

I am fairly new to TeamSite administration (mostly have been working with form development). Recently we took a tactical approach to redesigning our website and only made changes in Prod. I now want to come back and refresh our dev and test enviornments with a snapshot of our production server, but I am not sure about the correct way to go about this.

A few things I was thinking were:
1. Make a backup of Prod and then restore it into Test and Dev.
- Not sure if this will cause conflicts with hardcoded server names or anything like that

2. Migrate a recent edition of our site over to dev and test
- I dont think this will work because it just moves content, not all of the config files right?

3. Go through the backend and copy all of the files and folders over from Prod to test and dev

This is a one time thing to sync the enviorments and I am not looking for the exact steps, just highlevel overview to research.

thanks,
Brett

Hi,
We generally go from DEV->UAT-> Prod.
Not able to understand why you are planning to go reverse.
And also can you provide the no. of pages and DCTs/DCRs made/modified per day.

Thanks.

balzer

I understand that typically we move from Dev to Test to Prod, but we were pressed for time and just made changes in the Prod enviornment. Now, I am trying to get back to the dev -> test -> prod model, but need to go back and sync up dev and test with all of the changes (and content) out on PROD. I am looking to only do this once, not make it a continous process.

Adam Stoller

You need to do a combination of things - both of which entail (require) a decent knowledge of the system and the customizations.

. If you can do everything within 30 days you can just use the trial license, but if you find that you like it as a utility (which I think you will) I strongly encourage you to get actual licenses for it (they're not that expensive and it helps to support continued good development from them)For 'C' I'd consider either OpenDeploy or iwmigrate. The former is good for a surface copy and doesn't require removing pre-existing baseline content on the target servers; the latter is for completely removing and then re-creating the PROD branches on the other two environments (and thus requires you to be concerned about 'B' activities post-migration)

santosh013

I understand that typically we move from Dev to Test to Prod, but we were pressed for time and just made changes in the Prod enviornment. Now, I am trying to get back to the dev -> test -> prod model, but need to go back and sync up dev and test with all of the changes (and content) out on PROD. I am looking to only do this once, not make it a continous process.

Hi,
There are not only the pages and the DCTs but the configuration files too.
I hope you will have to manually compare everything and put everything in respective environment if you don't use any external repository (such as SVN).

Thnaks.