Some times you might get any error on R1Soft MySQL restore like,
“Error restoring MySQL database – MySQLD executable not found!”
Here we are going to see an alternative to restore a database from R1Soft backup from command line when the restoration from GUI fails.
How it works:
When we start an R1Soft MySQL restore, it makes a temporary MySQL instance on the client server. We need to find the sock file for it to generate the MySQL dump. You would need to start another restore from the interface to get the instance again.
Click on the ‘Logs’ section from the R1Soft interface to find the exact directory where it creates the file.
SSH to the client server and go to the directory. Here the location is ‘/var/lib/r1soft/tmp/r1soft-mysql-restore-tmp-c90efce0-bd5c-4410-9dae-fca73c268fd6’
cd /var/lib/r1soft/tmp/r1soft-mysql-restore-tmp-7800bc15-c68d-4007-8ta8-6bcb47f5dec6 # ll total 173136 drwx------ 4 root root 4096 Jul 20 23:51 ./ drwx------ 23 root root 4096 Jul 20 23:50 ../ -rw-rw---- 1 mysql mysql 153092096 Jul 19 04:12 ibdata1 -rw-rw---- 1 mysql mysql 5242880 Jul 20 23:51 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jul 19 04:10 ib_logfile1 drwx--x--x 2 mysql mysql 4096 Jul 15 10:44 mysql/ -rw-rw---- 1 root root 13679684 Jul 20 23:51 mysqld.err -rw-rw---- 1 root root 7 Jul 20 23:51 mysqld.pid srwxrwxrwx 1 root root 0 Jul 20 23:51 mysqld.sock=
Now you’ve the sock file /var/lib/r1soft/tmp/r1soft-mysql-restore-tmp-7800bc15-c68d-4007-8ta8-6bcb47f5dec6/mysqld.sock
You need to use that particular socket to generate the dump.
mysqldump -S /var/lib/r1soft/tmp/r1soft-mysql-restore-tmp-7800bc15-c68d-4007-8ta8-6bcb47f5dec6/mysqld.sock dbname > dbname.sql
A dump will be generated from the date you’ve selected to restore at first (R1Soft Panel). Once the dump is generated, you can restore it to its database.
mysql -u root dbname < dbname.sql
