M
M
maniac_by2020-05-28 12:34:08
MySQL
maniac_by, 2020-05-28 12:34:08

Transferring the database via mysqldump does not help, why?

Hello. Tried to drag MYSQL 5.6 to 5.6 on another server

mysqldump -u user -p jira > jira.sql
перенести jira.sql на другую машину
mysql -u user -p jira < jira.sql


Firstly, the database size is only 310 MB. And when deployed, only the basic user / system settings are obtained, plus about a hundred requests. Is there another way to capture the entire database or check why the database dump is breaking?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
M
maniac_by, 2020-06-08
@maniac_by

Generally. I had to increase the performance of the machine. Because the error could not be resolved. And deploy using xml backup

K
ky0, 2020-05-28
@ky0

If something "breaks" in you, errors would be visible during the dump / restore.

V
Vitaly Karasik, 2020-05-28
@vitaly_il1

In general, everything is correct.
You can add "--routines --triggers". And it is worth adding the name of the database for the dump.
And why are you sure that the original database is larger?
You can compare the size on the old and new machines

SELECT table_schema "DB Name",
        ROUND(SUM(data_length + index_length) / 1024 / 1024, 1) "DB Size in MB" 
FROM information_schema.tables 
GROUP BY table_schema;

By the way, if this is really Jira, then I advise you to export / import using Jira itself.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question