# PRODUCTION Mysql 5.6 DB crashed leaving orphaned partitions and the files are gone. **URL:** \ **Category:** Percona Server for MySQL 5.6\ **Created:** [October 18, 2019, 11:26pm UTC](https://forums.percona.com/t/production-mysql-5-6-db-crashed-leaving-orphaned-partitions-and-the-files-are-gone/7251 "2019-10-18T23:26:31Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\ **Post date:** [October 22, 2019, 6:11am UTC](https://forums.percona.com/t/production-mysql-5-6-db-crashed-leaving-orphaned-partitions-and-the-files-are-gone/7251/3 "2019-10-22T06:11:42Z")
Hello again [SteveS0922](https://www.percona.com/forums/member/43271-steves0922) Some notes from our tech team: best practice in this situation would be to restore from a backup + binary logs? Could you give us some idea of the size of the very large tables that we’re dealing with? Whatever you try out, you should make sure that they have a backup beforehand. If you can’t recover using this as guidelines it feels more likely that it’s beyond the scope of the Forum to get the right answer to you. Here are a couple of blogs and webinars that could be helpful, if you need clarification on any of the points don’t hesitate to come back. [URL][https://www.percona.com/blog/2017/10/23/mysql-point-in-time-recovery-right-way/[/URL]](https://www.percona.com/blog/2017/10/23/mysql-point-in-time-recovery-right-way/%5B/URL%5D) [URL][https://learn.percona.com/database-backup-and-recovery-best-practices-focus-mysql-recording[/URL]](https://learn.percona.com/database-backup-and-recovery-best-practices-focus-mysql-recording%5B/URL%5D) --- _[View the full topic](https://forums.percona.com/t/production-mysql-5-6-db-crashed-leaving-orphaned-partitions-and-the-files-are-gone/7251)._