Back Up Code

Hi Guys,

So I have been playing with virtualisation for development so that I can have differently configured installs depending on what I need to develop. I have begun to use source control and I have to say the roll back feature alone is worth it.

One of the issues is though before I used source control or virtualisation I used to just grab the code folder and back it up. What is the best method to back up now?

Would it be to just save a copy of the virtual machine? Or would it be to make a copy of the database?

I have plenty of space so I could make alternating copies of the VM no problem if that is what the easiest option is.

It depends what you need to backup! Does the database hold all your source code? Or do you have setup files, etc that you also need to keep? I'm not sure but does the virtual machine allow you to change the size of the VM after you have initially set it up?

At the moment I only have source but of course this can change to include other stuff. I don't know if you can change the size after the fact but why would you need to?

Source control and backup are two different things - while source control utility like Visual SourceSafe allows restoring, comparing, etc code from some point in time it [SourceSafe] needs to be backed up as well.
Backups need to be done on a regular basis and regardless of any source control you might have - perhaps to external hard drive or even flash drive (if not much to backup).

That is what I thought, I have all my Development data plus the VM on a seperate HDD so I think the easiest thing to do is to just back up the HDD!

But as far as "source control" you should still use some utility like the SourceSafe.

Oh I do, In the VM I have SourceGear Vault installed!

Quote:

---

Originally Posted by DeanMc

I don't know if you can change the size after the fact but why would you need to?

---

I was thinking of space taken up by the vm! If you have multiple machines that are big in size and only use a fraction of the space on each the remaining space could be put to better waste rather tha just wasted.

I'm not sure I see the advantage of developing in a VM. Testing, yes, but developing? For testing rolling back the VM to a clean state is very useful.

Plus you have the issue of the licensing costs for the tools. Each VM needs a license, just as if you were using multiple physical machines.

Visual Studio may give us an out here though, at least in some versions and editions: Microsoft Visual Studio 2008 License Terms

I would have thought that too but after playing around with VM's it seems to make sense. Originally I had my PC chalk full of different installations as well as all my personal rubbish, now I can still have my personal rubbish and programming on the same pc but they are separated!

Maybe the "personal rubbish" ought to be in a VM too? Then you can just carry the VHD along to a new machine when you replace the old one.;)

I had thought of that but I like the idea that my development machine is clean of my music and pictures etc, The other fact is when beta products come out I can play with them safely without upsetting other applications or installations that I may have ;0