MODx Database Recovery

Hello,

I have just suffered a hard drive failure with the hard drive containing a solid 60+ hours of Modx work.

I have a backup of the entire folder in which the site was stored and I have physical .MYD, .MYI and .FRM database file backups.

I shouldn’t imagine this is very hard to sort out, but my knowledge of MySQL is incredibly limited and I have tried all morning to find a solution, but have failed repeatedly. If anyone can help I am prepared to discuss fees.

Thanks,

Henry

Get your new environment setup and working and then it should be as simple as restoring the files (mysql/data/ is where the db files would go).

Quote from: OpenGeek at Jan 14, 2008, 10:09 AM

Get your new environment setup and working and then it should be as simple as restoring the files (mysql/data/ is where the db files would go).

I have tried this and faced a succession of errors. I have spoken to Susan Ottwell and she’s examined the individual files and has said that none of the info is coming up in a plain-text editor and is therefor likely to be corrupt.

What would be a failsafe approach to examining the files to see if they are corrupt or not?

I have uploaded the MySQL files and a zipped copy of the ModX installation here:

http://www.wymondhamrugby.com/backups/

I’ve never had to do this myself (thank God), but I would first try to recover the DB locally, and then check with either phpMyAdmin or an app like HeidiSQL if everything looks OK. Maybe you’ll have to restart mySQL to see the changes.

I was able to open the modx-files ($Root001\Dir2800), but there’s some garbage characters there. Not sure how important those are, but most looks OK.

e.g.

Quote from: ganeshXL at Jan 14, 2008, 11:16 AM

I’ve never had to do this myself (thank God), but I would first try to recover the DB locally, and then check with either phpMyAdmin or an app like HeidiSQL if everything looks OK. Maybe you’ll have to restart mySQL to see the changes.

I was able to open the modx-files ($Root001\Dir2800), but there’s some garbage characters there. Not sure how important those are, but most looks OK.

e.g.

<h1><span class="h1">Horizontal Earthy Lines</span></h1>
[[downloadbox2? &preview=`backgrounds/background4.jpg` &filetype=`.PNG` &scalable=`tick` &editabletext=`cross` &resolution=`20x20` &layered=`cross` &fonts=`N/A` &download=`backgrounds/background4.png` ]]

<h1><span class="h1">Fine Diagonal Lines</span></h1>
[[downloadbox2? &preview=`backgrounds/background3.jpg` &filetype=`.PNG` &scalable=`tick` &editabletext=`cross` &resolution=`4x4` &layered=`cross` &fonts=`N/A` &download=`backgrounds/background3.png` ]]

<h1><span class="h1">Subtle Grey/Black Stripes</span></h1>
[[downloadbox2? &preview=`backgrounds/background2.jpg` &filetype=`.PNG` &scalable=`tick` &editabletext=`cross` &resolution=`40x40` &layered=`cross` &fonts=`N/A` &download=`backgrounds/background2.png` ]]

Ah, interesting. However I should have probably specified that I had a few different sites running and I’m thinking the corrupt databases are the files proceeded by wymondham_

How would I check with phpAdmin if everything looks okay? I can’t import the files unless they are .SQL. I found an app called MySQLRecovery, but it just generates bizarre .SQL files with no differentiating content.

You could put all the .frm, .MYD and .MYI files into a folder named wymondham then from a command line try to repair them using myisamchk. I tried that, and got an error that these were not ISAM tables. They should be, so I’m presuming they are corrupted.