...
| Code Block |
|---|
FLUSH TABLES WITH READ LOCK; SHOW MASTER STATUS; |
This will show master current master status on master DB server. We will need this later when replicating the DB in the slave DB server in the slave. Leave this session as it is until replication is completed:
...
| Code Block |
|---|
MariaDB [kinton]> show slave status\G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 10.60.13.25
Master_User: replicator
Master_Port: 3306
Connect_Retry: 10
Master_Log_File: localhost-bin.000002
Read_Master_Log_Pos: 3713036
Relay_Log_File: localhost-relay-bin.000002
Relay_Log_Pos: 691
Relay_Master_Log_File: localhost-bin.000002
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 3713036
Relay_Log_Space: 989
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1...
1 row in set (0.00 sec)
|
Once Slave_IO_State is "Waiting for master to send event" replication is finished. Then, close the first session on master DB server where locks were set and master status was requested to release locks and you are done.
...