parkmo

[DB_NAME]: DB-name to recovery. /dev/shm Usage: First, check your memory if you can use shm directory.   For recovery speed, I use /dev/shm/ directory. Process flow. 01. Stop DB  service mysqld stop 02. Stop web-service. (If you don't use, block DB-connection by using firewall-cmd.)  service httpd stop 03. Change DB-mode on server.cnf   set innodb_force_recovery = 5 on /etc/my.cnf.d/server.cnf 04. Start DB for recovery.  service mysqld start 05. Run DB-dump.  mysqldump -u root -p --databases [DB_NAME] > /dev/shm/[DB_NAME].sql 06. Stop DB  service mysqld stop 07. Change DB-mode on server.cnf (normal mode)  set innodb_force_recovery = 0 on /etc/my.cnf.d/server.cnf 08. Backup old DB-files. (Run follows if you necessarily need backup.)  mkdir /backup/DB_BackupTmp  mv /backup/DB/ibdata1 /backup/DB_BackupTmp  mv /backup/DB/ib_logfile0 /backup/DB_BackupTmp  mv /backup/DB/ib_logfile1 /backup/DB_BackupTmp  mv /backup/DB/[DB_NAME] /backup/DB_BackupTmp 09. Start DB  service mysqld start 10

1. broken hdd disk backup  1) remote-server nc -v -l [port] > hdd_backup.img  2) equipment of broken hdd dd if=/dev/sda | nc -v [remote-server IP] [port]   ex)  1) remote-server nc -v -l 2222 > hdd_backup.img  2) equipment of broken hdd dd if=/dev/sda | nc -v 1.1.1.1 2222 2. use recovery tool  testdisk (http://www.cgsecurity.org/wiki/TestDisk_Download) 3. run fsck from img file  # losetup --offset 32256 /dev/loop2 harddrive.img  # fsck /dev/loop2  and again testdisk reference: https://major.io/2010/12/14/mounting-a-raw-partition-file-made-with-dd-or-dd_rescue-in-linux/ https://bbs.archlinux.org/viewtopic.php?id=136766