The CreatorCon Call for Content is officially open! Get started here.

What are the steps to follow before, during and after (Initial) Clone from Test to Prod

Vijay Talupula
Tera Guru

‎06-05-2017 09:19 PM

Guys,

Instances Version: Istanbul

As part of the Implementation, we are moving (It is the First Move ) all the changes implemented from Test to Prod (Clone) and then planning to do Clone from Prod to Dev so that we can make sure all our customer instances are in Sync. So, we would like to make sure a smooth movement of it and looking for a Checklist.

1) What is the checklist for Pre Clone ?

2) Is there any thing need to make sure during Clone ?

3) What is the checklist for Post Clone ?

4) Any version (Istanbul) specific cautions need to be taken care during this entire process ?

5) Also looking for any experiences (related to issues in PROD) from any body after the clone ?

I would appreciate for the help on this at the earliest possible.

Labels:
0 Helpfuls
  • 3,301 Views
8 REPLIES 8

bernyalvarado
Mega Sage

‎06-05-2017 09:27 PM

Hi Vijay,



We perhaps could write a book just with the questions you're asking First, I'll like to clarify that moving things from Test to Prod using a clone is not a normal practice. I can't think right away of downsides of doing if it's your first deployment to Production and it does not contain any change that you will like to keep. Since you will be doing many other deployments from Test to Prod I'll rather recommend you doing the deployment using update sets on which you retrieve the completed update sets in Test into Production and then apply these according your deployment plan.



Thanks,


Berny


0 Helpfuls

Vijay Talupula
Tera Guru
In response to bernyalvarado

‎06-05-2017 10:01 PM

Hi Berny,



Thanks for your information. Yes, I agree with you about deployment from Test to Prod via update set would be best option But as this is the initial implementation where many teams worked and might have touched common artifact(s) and not taken the order of the update sets to be committed in PROD. So this time we have decided to go with Clone and next deployments are as usual Update sets commit.


0 Helpfuls

bernyalvarado
Mega Sage
In response to Vijay Talupula

‎06-05-2017 10:09 PM

You're welcome Vijay!! I just wanted to provide some helpful insight.



I must confess i like the creativity of doing the deployment to Production using a clone. Please keep us posted how it goes.



Thanks,


Berny


0 Helpfuls