Cloning
Posted: 6. Dec 2013, 20:01
Hello,
I am using Virtual Box 4.2.12 r84980 in a windows environment.
What I am trying to do: I have begun to create several machines that are in various stages of our install process. Meaning, each machine has different components at a specific stage of install (ie machine 1 with operating system + sql, machine 2 with operating system + sql + software application). I felt this was a more efficient way to have stages ready pending what needs to be emulated/created. The alternative had been to start from the beginning each time to build a machine.
How I did it: I referenced an article on cloning in order to create my different stage machines. I wanted to use the most recent machine, clone it and then bring it up to the next stage before cloning it again. That way each machine is the same but unique. The article was found at techrepublic with the subject of clone-and-move-virtual-machines-in-virtualbox
My Issue/ Concern: In the article it references to copy the clone to an external or shared drive since the process creates the clone on my C drive. After the clone has been copied and moved, the article asks to create a new machine by pointing at the newly copied files (which, by the way, are not .vdi flies but .vbox and vmdk). However, when you go through the clone process it automatically creates a machine pointing at the c drive files in the virtual box rather than allowing you to create your own, pointing at the newly copied files on your external drive. My concerns are twofold. Since the machines are all pointing at the files on my C drive, I am concerned about running out of room down the road. Secondly, can you (or should you try to) point the newly created machines at the copied files on the external?
I am open to any advice of the questions above and also advice if I should be creating machines in a different way.
Thank you
I am using Virtual Box 4.2.12 r84980 in a windows environment.
What I am trying to do: I have begun to create several machines that are in various stages of our install process. Meaning, each machine has different components at a specific stage of install (ie machine 1 with operating system + sql, machine 2 with operating system + sql + software application). I felt this was a more efficient way to have stages ready pending what needs to be emulated/created. The alternative had been to start from the beginning each time to build a machine.
How I did it: I referenced an article on cloning in order to create my different stage machines. I wanted to use the most recent machine, clone it and then bring it up to the next stage before cloning it again. That way each machine is the same but unique. The article was found at techrepublic with the subject of clone-and-move-virtual-machines-in-virtualbox
My Issue/ Concern: In the article it references to copy the clone to an external or shared drive since the process creates the clone on my C drive. After the clone has been copied and moved, the article asks to create a new machine by pointing at the newly copied files (which, by the way, are not .vdi flies but .vbox and vmdk). However, when you go through the clone process it automatically creates a machine pointing at the c drive files in the virtual box rather than allowing you to create your own, pointing at the newly copied files on your external drive. My concerns are twofold. Since the machines are all pointing at the files on my C drive, I am concerned about running out of room down the road. Secondly, can you (or should you try to) point the newly created machines at the copied files on the external?
I am open to any advice of the questions above and also advice if I should be creating machines in a different way.
Thank you