docker exec -it mysql-master bash
mysql -u root -p비번
스키마 존재여부 확인
SHOW DATABASES;
저는 yml로 스키마까진 만들어뒀습니다.
mysql> SHOW DATABASES;
+--------------------+
| Database |
+--------------------+
| flight_data |
| information_schema |
| mysql |
| performance_schema |
| sys |
+--------------------+
5 rows in set (0.01 sec)
SOURCE /tmp/0228data.sql;
/tmp/경로에 0228.sql 파일을 미리 옮겨두었습니다.
mysql> SOURCE /tmp/0228data.sql;
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 1 row affected (0.00 sec)
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
이런식으로 데이터베이스 마다 알아서 탑재됩니다.
mysql> SHOW tables;
+-----------------------+
| Tables_in_flight_data |
+-----------------------+
| booking |
| flights_data |
| forprice |
| user |
+-----------------------+
4 rows in set (0.00 sec)
mysql> select * from user;
+---------+-----------+-----------+--------------------------------------------------------------+---------------------+--------+---------------+
| user_no | user_name | user_id | user_pw | email | gender | phone |
+---------+-----------+-----------+--------------------------------------------------------------+---------------------+--------+---------------+
| 1 | ??? | hong123 | password123 | hong@example.com | ? | 010-1234-5678 |
| 2 | ??? | kim456 | password456 | kim@example.com | ? | 010-8765-4321 |
| 3 | ??? | sonny1234 | $2a$10$GC2lVMMcvULQvNOa2JKZZOag/fgtjM.U4QHD2PLjySReKyliEL0gm | sonny1234@naver.com | M | 01099991111 |
+---------+-----------+-----------+--------------------------------------------------------------+---------------------+--------+---------------+
3 rows in set (0.00 sec)
백업한 데이터가 누락없이 잘 탑재된것 같습니다.
'SQL&DB' 카테고리의 다른 글
| GTID마스터 슬레이브 (0) | 2025.03.04 |
|---|---|
| mysql server_id (0) | 2025.03.04 |
| DB 두 가지 복제 방식을 비교 (0) | 2025.02.27 |
| Mysql-Master&Slave 구성 (0) | 2025.02.27 |
| mysql-commit (0) | 2025.02.27 |