6

What is the best approach to creating a Developer Copy sandbox of another sandbox ? I've read that you essentially need to deploy everything from one sandbox to the other. My question is how do I start the new Sandbox ? It sounds like I need a blank sandbox which I can start deploying all of my components into - but I don't know how to create that "blank" one.

Is this the right approach ? How do I create that "blank" sandbox ? Any kind of advice I can get would be greatly appreciated.

Thank you.

|improve this question
  • You create a sandbox from your production org. Am I missing something? – Mike Chale Nov 20 '13 at 21:35
  • I'm not trying to make a sandbox which is a copy of Production. I want to create a sandbox which is a copy of ANOTHER sandbox. – Zoom_v Nov 20 '13 at 21:40
  • And I don't think I'd be able to create another sandbox from Production and just deploying everything from the original sandbox into the new one because it will have all of the components which are in Production still left in there afterwards. At least that's what I think. – Zoom_v Nov 20 '13 at 21:45
5

To make a copy of a Sandbox, you would need to deploy configuration metadata from one instance to the other using the metadata API. You can use either the Eclipse IDE, Ant, MavensMate or BrainEngine to move metadata from one instance to another. There is no copy function from one sandbox to another like there is when burning a sandbox from production.

|improve this answer
  • Thank you @greenstork. So, I'm confused on how to do that. How would I do that in Eclipse ? I want to copy Sandbox A and make Sandbox B - so how I do take all of those components from Sandbox A and deploy them to a sandbox that hasn't been created yet ? How do I start on that ? I'm sorry if I've got stupid questions but I've never crated a new sandbox like this before. – Zoom_v Nov 20 '13 at 21:50
  • Just create Sandbox B and then deploy from Sandbox A to Sandbox B – greenstork Nov 20 '13 at 21:51
  • If you're asking about how to create a new sandbox, directions can be found here: help.salesforce.com/apex/… – greenstork Nov 20 '13 at 21:56
  • But if I do that then Sandbox B will start out as a copy of Production, and deploying from Sandbox A to B won't get rid of all the Production components which I do not want in Sandbox B, right ? I would end up with objects with fields that are in Prod which I do not necessarily want in this new Sandbox B along with other components from Prod which I do not want. Or am I missing something ... ? If I were to create a giant deploy package from Sandbox A to B would Eclipse highlight in red all of the components in Sandbox B which are not in the package and allow me to select them to delete them ? – Zoom_v Nov 20 '13 at 22:01
  • 1
    Sandboxes are designed to be recent copies of production for the purpose of ultimately developing and deploying code to production. If you don't need metadata from production it begs the question of why use a sandbox at all, why not just a dev instance. – greenstork Nov 20 '13 at 22:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.