电脑重装系统后如何恢复Mysql数据库

1、把原来mysql安装目录下的data文件夹拷出来；

2、卸载掉原来的mysql；

3、重新安装mysql；

4、拷出来的data文件夹里，除了mysql、test子文件夹外的子文件夹，全部都是数据库

在linux卸载mysql数据库：

a）查看系统中是否以rpm包安装的mysql

1

2

3

[root@linux ~]# rpm -qa | grep -i mysql

MySQL-server-5149-1glibc23

MySQL-client-5149-1glibc23

卸载MySQL-server-5149-1glibc23和MySQL-client-5149-1glibc23

1

2

[root@linux ~]# rpm -e MySQL-client-5149-1glibc23

[root@linux ~]# rpm -e MySQL-server-5149-1glibc23

b)查看有没有mysql服务

1

2

[root@linux ~]# chkconfig --list | grep -i mysql

mysql 0:off 1:off 2:on 3:on 4:on 5:on 6:off

删除mysql服务

1

[root@linux ~]# chkconfig --del mysql

c)删除分散mysql文件夹

1

2

[root@linux ~]# whereis mysql

mysql: /usr/lib/mysql /usr/share/mysql

分别删除

1

2

[root@linux lib]# rm -rf /usr/lib/mysql/

[root@linux lib]# rm -rf /usr/share/mysql

通过以上几步，mysql应该已经完全卸载干净了！！！

查看已经安装的服务

rpm –qa|grep -i mysql

-i 作用是不区分大小写

yum remove mysql mysql-server mysql-libs compat-mysql51

rm -rf /var/lib/mysql

rm /etc/mycnf

查看是否还有mysql软件：

rpm -qa|grep mysql

有的话继续删除

可以看到有两个安装包

MySQL-server-5619-1linux_glibc25x86_64rpm

MySQL-client-5619-1linux_glibc25x86_64rpm

删除这两个服务(去掉后缀)

rpm –e MySQL-client-5619-1linux_glibc25x86_64

rpm -e MySQL-server-5619-1linux_glibc25x86_64

查看残留的目录：

whereis mysql

然后删除mysql目录：

rm –rf /usr/lib64/mysql

删除相关文件：

rm –rf /usr/mycnf

rm -rf /root/mysql_sercret

最关键的：

rm -rf /var/lib/mysql

如果这个目录如果不删除，再重新安装之后，密码还是之前的密码，不会重新初始化！

网上查了很久都没有文章提到这个，最后还是自己摸索找出来的。

卸载完成！怎么确定是不是真的卸载干净了呢？

一是看安装输出：

如果没有卸载干净，安装server时输入只有两行：

[root @localhost opt]# rpm -ivh MySQL-server-5619-1linux_glibc25x86_64rpm

Preparing ########################################### [100%]

1:MySQL-server ########################################### [100%]

卸载干净了安装输入如下：

[root @localhost opt]# rpm -ivh MySQL-server-5619-1linux_glibc25x86_64rpm

Preparing ########################################### [100%]

1:MySQL-server ########################################### [100%]

2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated Please use --explicit_defaults_for_timestamp server option (see documentation for more details)

2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages

2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 123

2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO

2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions

2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 1280M

2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool

2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file /ibdata1 did not exist: a new database to be created!

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file /ibdata1 size to 12 MB

2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file /ib_logfile101 size to 48 MB

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file /ib_logfile1 size to 48 MB

2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file /ib_logfile101 to /ib_logfile0

2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781

2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new

2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created

2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active

2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables

2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created

2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables

2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created

2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start

2014-09-23 07:22:45 26041 [Note] InnoDB: 5619 started; log sequence number 0

A random root password has been set You will find it in '/root/mysql_secret'

2014-09-23 07:22:46 26041 [Note] Binlog end

2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting

2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown

2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated Please use --explicit_defaults_for_timestamp server option (see documentation for more details)

2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages

2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 123

2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO

2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions

2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 1280M

2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool

2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda

2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active

2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start

2014-09-23 07:22:48 26065 [Note] InnoDB: 5619 started; log sequence number 1625977

2014-09-23 07:22:48 26065 [Note] Binlog end

2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting

2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown

2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987

A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !

You will find that password in '/root/mysql_secret'

You must change that password on your first connect,

no other statement but 'SET PASSWORD' will be accepted

See the manual for the semantics of the 'password expired' flag

Also, the account for the anonymous user has been removed

In addition, you can run:

/usr/bin/mysql_secure_installation

which will also give you the option of removing the test database

This is strongly recommended for production servers

See the manual for more instructions

Please report any problems at >

以上就是关于电脑重装系统后如何恢复Mysql数据库全部的内容，包括:电脑重装系统后如何恢复Mysql数据库、如何彻底卸载linux系统下的mysql数据库、centos中怎么删除mysql数据库等相关内容解答，如果想了解更多相关内容，可以关注我们，你们的支持是我们更新的动力！