First, I want to thank you for saving my butt this weekend .. I was a victim of what I'm sure will be known as "The Great ValueWeb-Hostway Migration Catastrophe of '07" ..
Basically, some yutz spilled coffee (or sneezed, or chewed, or whatever) .. and wrecked the hard drive on my dedicated server .. and I spent the weekend (after already being down for 72 hours) restoring eight websites - three of which were blogs. The Backup files worked beautifully .. no problems at all .. so thanks for such a great plug-in!
I did notice, that when I went to import via phpMyAdmin, next to the "Browse" button there was listed a 2048K maximum filesize note ... two of my .sql files were right around 1900K .. so I guess I'm running out of room .. so .. um .. what do I do then?
The sql files are just text files, so you can split them up into smaller chunks if necessary. If the file extension is .sql.gz instead of just .sql, then you'll need to unzip it first.
First, I want to thank you for saving my butt this weekend .. I was a victim of what I'm sure will be known as "The Great ValueWeb-Hostway Migration Catastrophe of '07" ..
Basically, some yutz spilled coffee (or sneezed, or chewed, or whatever) .. and wrecked the hard drive on my dedicated server .. and I spent the weekend (after already being down for 72 hours) restoring eight websites - three of which were blogs. The Backup files worked beautifully .. no problems at all .. so thanks for such a great plug-in!
I did notice, that when I went to import via phpMyAdmin, next to the "Browse" button there was listed a 2048K maximum filesize note ... two of my .sql files were right around 1900K .. so I guess I'm running out of room .. so .. um .. what do I do then?
Thanks again.
-fQ-
The sql files are just text files, so you can split them up into smaller chunks if necessary. If the file extension is .sql.gz instead of just .sql, then you'll need to unzip it first.
Cool ... thanks.
-fQ-
RSS feed for this topic
Reply
You must log in to post.