There's nothing much to do about that actually. It's a single thread so large databases are going to take a very long time to restore.What can I do to speed up the restoring process?
There's nothing much to do about that actually. It's a single thread so large databases are going to take a very long time to restore.
One of the databases at a client of mine takes a little over 2 days to restore from scratch.
To a certain extend. It's still going to be a slow and tedious process, even if you tuned it perfectly.On some forum it said that adjusting in my.cnf can speed up the process.
In that case I recommend not changing anything. You can tune MySQL quite a lot but if you don't know what you're doing you will likely "over" tune things or tune the wrong things. This will only make it worse, not better.But honestly saying I don't know what I should change there.
OPTIMIZE TABLE reorganizes the physical storage of table data and associated index data, to reduce storage space
and improve I/O efficiency when accessing the table. The exact changes made to each table depend on the
storage engine used by that table.
I have 5 database ,the total size of them is more than 1 GB.
So as solution I made a sh script to take backup of the database as tar file.Now the size of the tar file is 100 mb and it becomes easy to restore now.
But tables with InnoDB engine are corrupted so I converted to myisam engine.