Does anyone use virtualization to create faster disaster recovery for a development environment?

I was very tired of the dying development box, and then I had to reinstall the list of tools that I use in development.

This time, I think I'm going to configure the development environment on a virtual virtual machine and save it to an external hard drive so that I can quickly create a development environment after I fix the real computer.

This seems to be a good way to do a “hardware agnostic backup” and be able to quickly return to a quick result after a disaster.

Has anyone tried this? How well does it work? Did it save your time?

+3
source share
7 answers

I used all my developments for virtualization using VirtualBox.

Basically, I have a Vbox Debian image file tagged on a DVD. When I have a new project, I copy it to one of my external hdds and configure it in my project.

As soon as my project was delivery, I copy the image from my external hdd to a blank DVD and burn it.

+2
source

I did it with great success, we had it in our QA environment, and we also used Undo disks, so if we wanted to test, for example, Microsoft fixes, we could minimize the window to the previous state.

, , SQL Server, . , . ; .

+1

, , - VirtualBox, OpenSolaris ZFS. () , - , QA.

+1

. , - ( - ) .

+1

-, , . , , , , .

, , , , IMO.

0

, , . , , , . , , .

Linux, Windows Mac, .

.

- , .

0

. , , . , (IIRC, - VBox) PIV. , . , , , CPU/.

, , , , - .

Now a short word about Windows, since the other systems on which I did this are not a problem. The sections that you image should not change between them. Not a problem for other OSs, but one of them decided to put Profiles on Windows smack dab in system files. I just want nothing in my profile (or on my desktop, which is in my profile) that I don’t want to lose.

-1
source

All Articles