There are some way to restore database from a stopped AWS instance.
My case is a in-accessable ubuntu instance, it has been miss config firewall (may be) and only snapshot of linux partition left.
MySQL 5.7 InoDB
I will update guide and link latter.
Notes some key mistakes:
- Pay attentions to mysql error log after restore.
After override ibdata and some database folder in /var/lib/mysql etc. I miss (by the guide) that, I have to copy the ibdata log too.
- My error log go speedy to over 12GB on 16GB partition, it go to full hard drive capactity.
- So when I remove the log file and stop MySQL, it can not be start again.
I guess that when I replace ibdata and some other database, mysql see the not match between index, ID of log or record in system DB, so it output err log.
Default may be MySQL do not limit log size so it exceeded the SDD 16GB instance.
...
My case is a in-accessable ubuntu instance, it has been miss config firewall (may be) and only snapshot of linux partition left.
MySQL 5.7 InoDB
I will update guide and link latter.
Notes some key mistakes:
- Pay attentions to mysql error log after restore.
After override ibdata and some database folder in /var/lib/mysql etc. I miss (by the guide) that, I have to copy the ibdata log too.
- My error log go speedy to over 12GB on 16GB partition, it go to full hard drive capactity.
- So when I remove the log file and stop MySQL, it can not be start again.
I guess that when I replace ibdata and some other database, mysql see the not match between index, ID of log or record in system DB, so it output err log.
Default may be MySQL do not limit log size so it exceeded the SDD 16GB instance.
...
Nice work, your blog is concept-oriented, kindly share more blogs like this
ReplyDeleteAWS Online Training Bangaalore