Lost all my nodes after backup
| Project: | backup |
| Version: | 5.x-3.0 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | dmuth |
| Status: | active |
Jump to:
Got error 28 from storage engine query: taxonomy_node_get_terms SELECT t.* FROM term_node r INNER JOIN term_data t ON r.tid = t.tid INNER JOIN vocabulary v ON t.vid = v.vid WHERE r.nid = 4082 ORDER BY v.weight, t.weight, t.name in /home/marketing/drupal/includes/database.mysql.inc on line 172.
Got error 28 from storage engine query: user_access SELECT DISTINCT(p.perm) FROM role r INNER JOIN permission p ON p.rid = r.rid WHERE r.rid IN (2,6) in /home/marketing/drupal/includes/database.mysql.inc on line 172.
These are two of the many Error logs I get after I made a backup, I haven't had this happen before.
The only difference this time was that I tried using "Backup from Parent Directory" ... which spit out an error about not being able to rename the file. So I deselected that and tried again, which brings me to the horrible mess I'm at right now. Drupal Administration still works fine, but all my menus and node content have dissapeared! The Node tracker still sees everything though...
Luckily I have another backup system which works and that I will restore from, but I just thought you guys should know!!!
#1
Whoa, that really sucks. Sorry to hear about this. :-(
I did some Googling on that error, and it looks like the underlying issue is MySQL freaking out when it runs out of disk space. More details are here: http://drupal.org/node/44160
I would suggest checking with your sysadmin/webhost and seeing what's up with that machine.
As for why you lost all of your nodes, I do not know. I can only guess that MySQL went crazy when it ran out of disk space. That's definitely uncool behavior on the part of MySQL.
I don't want to quite mark this as "closed" yet, but I am going to mark it as "postponed" for now, just so that the issue doesn't drop off my list.
If you could check with your sysadmin/webhost about disk space, I'd be interested in hearing if that turns out to be the case or not. If I can be of any help in resolving this, feel free to call on me.
Good luck!
-- Doug
#2
You were right Doug!
I guess I didn't really understand the Backup from Parent Directory -- it ended up being like 8 gigs or something and when my guy deleted those from the temp folder everything went back to normal.
Crisis averted.
#3
Whoa, that's a lot of data!
I'll mark this bug as closed. :-)
#4
Even without using "Backup from parent directory," this bug can occur. And unfortunately, if you aren't root on your system, and don't have immediate access to the system administrator, it can be very difficult to resolve. For example, I just broke my site and the system administrators are unavailable for the weekend. Is there a way for the module to check for sufficient free space before running the backup? This is a pretty ugly failure mode.