Hi Mustafa,
I think we must back to topic.
Did you mean to say that my solution is wrong?If file database backup already exists in server, many options to restore:
There are even more options to use a dump.
The method you suggested is not the only one.But I can certainly read your thoughts between the lines. It can be avoided tell people "how to use an extra layer" of problems.
Mysql dump, backup and restore is helpful when there is a purpose. Creating mysql dump, it simply makes a file with SQL statements in ASCII format. One can compress it for certain reasons.
Mysql dump with SQL statements in ASCII format is necessary when one should make a version upgrade from Mysql 4--- > 5 or technical pre-requisites changes like INNODB ---> MyISAM.
When all pre-requisites between two servers are equal and a manual transfer is in question,
there is no reason for a mysql dump, backup and restore. Why?
Under the mysql database directory /var/lib/mysql there are files with extensions like MYI, MYD, etc. in mysql format. These files will operate under any name of the database under the same mysql server architecture and driver connecting it.
THESE MYSQL FILES ARE NOT SERVER DEPENDENT AND ARE PORTABLE TO ANY SERVER.
So one converts these files to a text file inserting SQL INSERT statements and make one file 10 - 100 times bigger. Then one transfers to a different server. And then one reconverts it back again.
This is a step that can be completely avoided. There are many tutorials available for such a process with php scripts, also interactive. So ofcourse one can use method of back/restore. One can ofcourse give solution to this, when necessary. But this is not always necessary.
Young webmasters will not realize this.
There are experts reading such exchanges and your messages are evaluated by the international community. There are journalists writing articles on Kloxo-MR...