Administrace komentářů

Děkuji vám za odpovědi.

server:/var/lib/mysql # ls -lh
total 176M
-rw-rw---- 1 mysql mysql   56 Jan 22  2015 auto.cnf
drwx------ 2 mysql mysql 4.0K Nov 22 12:23 drupal_afnet
drwx------ 2 mysql mysql  12K Feb 14 17:43 drupal_kef
drwx------ 2 mysql mysql 4.0K Jun 24  2016 exstres
-rw-rw---- 1 mysql mysql  48M Feb 20 15:14 ib_logfile0
-rw-rw---- 1 mysql mysql  48M Feb 20 14:56 ib_logfile1
-rw-rw---- 1 mysql mysql  12M Feb 20 15:14 ibdata1
drwx------ 2 mysql mysql 4.0K Dec 13  2013 luxcal
drwx------ 2 mysql mysql  36K Feb  9 12:52 moodle
drwx------ 2 mysql mysql 4.0K Mar  3  2016 mrbs
drwxrwx--- 2 mysql mysql 4.0K Jun 20  2016 mysql
-rw-r--r-- 1 mysql mysql    3 Jun 20  2016 mysql_upgrade_info
drwx------ 2 mysql mysql 4.0K May 20  2013 openmeetings
drwx------ 2 mysql mysql 4.0K Jun 20  2016 performance_schema
drwx------ 2 mysql mysql 4.0K Jan 12  2014 pokusy
drwx------ 2 mysql mysql 4.0K Nov 14  2013 postfix
-rw-r----- 1 mysql mysql  68M Jun 20  2016 server.err
-rw-rw---- 1 mysql mysql    6 Feb 20 15:14 server.pid
drwx------ 2 mysql mysql 4.0K Nov  6  2013 squirrelmail
drwx------ 2 root  root  4.0K Feb 20 15:11 test

Jestli máte na mysli /var/lib/mysql/mysql tak její tabulky vidí i PhpMyAdmin, takže jsou nejspíš v pořádku.

Ty odkazy jsem si prošel a některé tipy i vyzkoušel bez valného úspěchu.

Ve výše uvedeném odkaze je ještě postup, který bych rád vyzkoušel, ale nerozumím přesně bodu 2:

1. should copy the mysql data folder (/var/lib/mysql -- linux OR C:\ProgramData\MySQL\MySQL Server 5.1\data -- windows)
2. in the new server stop the mysql and paste all the folders pertaining to different databases , except the main "mysql" database.
3. make sure to copy and paste "ibdata1" file from the backed up folder into the new server "mysql data folder".
4. make sure to give permission to "mysql" user for that file (windows user need not worry).
5. restart mysql you should be able to see all the backed up databases correctly configured , and you should be able to access the table data without getting that error (1146).