virtualbox.org

i hate to say this, but, seems the last 10 days of my work is gone.
When installed v 2.02 things got somehow screwed, and i think i clicked the darn "snaphot" thing . And, man, this thing does not ask i to confirm any action.
So i began to guess what to do with the "states" of the machine.

The result is it seems to be rolled back to december 2007, and that is a very bad thing. I know i had another snapshot, which it was the one i was working.
Of course, i had it because i didn't notice until, at least, may .

When i went to from v 1.6.x v 2.0, i backed up, i mean i copied all the stuff, into a separate directory, and that was a week ago.
So, i have that, but i have absolutely no clue how to make it work. The thing does not "import" anything, just register only new machines.

Now, the question is how i recover the data with that "original snapshot" , so i can only loose a week or so ?

Absolutely yours,

Pablo .

Pablo,

I've done a few posts on related topics in the last few days. When you say that you copied "copied all the stuff" what exactly do you mean? Exactly what files? If it is all then even though it's not supported, I should be able to talk you through merging the contents back into the VBox registry hierarchy. In the meantime, to save me having to repeat myself have a read through my tutorial All about VDIs which explains how snapshots work and how they are referenced through the VirtualBox.xml file. I realise that is my be a little heavy going, but this is a lot less work then redoing all your work.

TerryE, thanks for your input .

Well, i copied the machines and vdi folders, to a separate folder.

I'm looking at your post, but with vdi and sav files, things does not seem to be very keen .

i tried to build a new vm, then added the copied vdi as a second disk, as i don't know how to "merge" that with the sav file, but all i can see is december 2007 data also.
I've been looking on :
http://muralipiyer.blogspot.com/2008/02 ... entic.html

which has been posted on these forums, but, vditools does not seem to like hardy amd64build , as there are all requirements fullfilled in the system,
but vditool can't see them, like VBoxDD.so and VBoxRT.so . Maybe i should install a 32 bit linux to use it.

i don't know...

Pablo .

Pablo, don't start changing you backup or you might just break what you've got. As I said, I can talk you through it but only if you don't make things worse!! Did you back up the VirtualBox.xml?

TerryE, thanks for your time .

I've been doing my homework, recovering work .

I installed a new VB, now v 1.56, the last i cand consider "stable" enough for me. I have done it with a full allocated disk, to prevent any new losses .
I guess i learned, of course, the tough way.

Sh*t happens and you have to face it, at a point in time.

Maybe it will take another week to recover lost work, but i can handle.

Pablo.

PS: next time,i will evaulate before installing new versions. VB 2.02 is buggy for me .