Recover InnoDB Data & Backup
Budget / Salary₹1,500–12,500
TypeFreelance project
LocationRemote
Posted2 hours ago
My MySQL 5.5.18 instance is limping along after a corruption event—system tables open, but every InnoDB table throws errors. The server is only “partially functional,” so I have powered it down and kept all data files intact (ibdata, ib_logfile*, .frm, .ibd, relay/binlogs, my.cnf). Remote log-in isn’t possible; you will need to walk me through everything step-by-step while I work directly on the box.
What I need is a complete, reliable FULL backup of every database, including the damaged InnoDB tables, so I can spin up a fresh 5.7+ server later. I am comfortable following detailed terminal commands; I just need an expert plan and real-time guidance to:
• Mount the data directory in a safe environment (ideally using Percona XtraBackup, mysqlbackup, or a comparable tool).
• Set the appropriate innodb_force_recovery level, dump out the data, and verify logical consistency.
• Export users, routines, triggers, and events so nothing is lost.
• Package the final .sql or .xbstream files, ready for import elsewhere.
• Leave me with a short post-mortem outlining what was salvaged and any objects that proved unrecoverable.
Deliverable is the full backup set plus clear commands/scripts and notes so I can reproduce the process if needed. If you have handled 5.5 InnoDB crashes before and can guide over chat or video while I execute, let’s get started right away.
What I need is a complete, reliable FULL backup of every database, including the damaged InnoDB tables, so I can spin up a fresh 5.7+ server later. I am comfortable following detailed terminal commands; I just need an expert plan and real-time guidance to:
• Mount the data directory in a safe environment (ideally using Percona XtraBackup, mysqlbackup, or a comparable tool).
• Set the appropriate innodb_force_recovery level, dump out the data, and verify logical consistency.
• Export users, routines, triggers, and events so nothing is lost.
• Package the final .sql or .xbstream files, ready for import elsewhere.
• Leave me with a short post-mortem outlining what was salvaged and any objects that proved unrecoverable.
Deliverable is the full backup set plus clear commands/scripts and notes so I can reproduce the process if needed. If you have handled 5.5 InnoDB crashes before and can guide over chat or video while I execute, let’s get started right away.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.