remote ftp backup not working

[zenkul]

yes, there is some many option for backup/restore, depends on we condition

@MRatwork,
why stop development "raw backup" like Kloxo-DR method ?

[Kloxo-DR]

Hi zenkul,

yes, there is some many option for backup/restore, depends on we condition
@MRatwork,
why stop development "raw backup" like Kloxo-DR method ?

In 2008, I had a bad fight with Ligesh about this aspect also, amonst my argument with him regarding security features.

By not implementing the RAW BACKUP method, he introduced an additional layer of problems that prevails even today.

If the mysql database was functional on the old server, keeping the mysql pre-requisites the same, it MUST function on the new server.

I argued with Ligesh and questioned him why he was "kind of exporting" to make a backup from those MYI/MYD files to re-contruct the database to the same MYI/MYD files in a new location.

With the reconstruction one gets into 100s of problems, where the table file name.MYI will be the same before in the old server and name.MYI after in the new server.

His only argument was that it is possible that there are different mysql versions and configurations.

What if not?

With the current state of Kloxo-MR, the architecture is reached to a way far more advanced level, although Mustafa creates his own little world with his scripts breaking the Linux integrity.

Thats why I also support you, and your request to Mustafa, to completely abolish the "backup/restore" method and implement the transfer oF EXACT COPIES IN COMPRESSED FORMAT OF ALL FILES OF MYSQL DATABASES without one single byte exported and imported.

Backup could also be done with php ---> ASCII and restore could be ASCII ---> php back again.

Backup could also be done with html ---> ASCII and restore could be ASCII ---> html back again.

Does this make sense?

Now, with Kloxo-MR with an advanced level of data exchanges features with FTPs, and those install and fix scripts harmonizing through yum repos, it is really non-sense to use the "backup/restore" method.

Then, after abolishing, everyone can ofcourse use the "backup/restore" method on mysql level when they want, should the pre-requisites of environment changes.

After implementing the "RAW METHOD", Kloxo-MR will achieve the highest form of integrety in transfer of data between datacebters or servers and and archiving the data.

[MRatWork]

What's the 'raw method'?. So, what's different with method by Kloxo-MR (also Kloxo-MR)?.

[Kloxo-DR]

Hi Mustafa,

What's the 'raw method'?. So, what's different with method by Kloxo-MR (also Kloxo-MR)?.

Uh, I was perhaphs not very clear about this, as well as zenkul. Zenkul ment in his description of my psyedoname "Kloxo-DR", when he refered to RAW method.

Lets define both, the current method as "BACKUP method" and my suggestion as "RAW method", as zenkul proposed" the name (which is really very accurate description of the method). This is what happens:

1) BACKUP METHOD

Currently, backup function makes:

Code: [Select]

mysql> dump client_name_db_name;
When the backup function is executed, it will make an export to dump data from mysql server using the mysql functions. It will convert all the data in tables of the database and wrap it with (INSERT"") STATEMENTS. It can grow really very large, depending on the data inside table.fields.

Advantage:

a. It remains mysql version independent.
b. Many external programs are able to import such dumps.

We do not require both above.

2) RAW METHOD

Suggestion is:

tar -cpf client_name_db_name.tgz /var/lib/mysql/client_name_db_name

Here, there is no conversion of three files from mysql format to ASCII data with INSERT statements inside.

So there is no backup.

Thus, there is no restore.

One simply has do the following:

Create client_name_db_name from kloxo restore, if not exists.

Code: [Select]

if [[ ! -d  /var/lib/mysql/client_name_db_name]] ; then
   {
    mkdir /var/lib/mysql/client_name_db_name
    insert details in mysql about client_name_db_name
   }
   tar -zxf /tmp/backupTRgbvFGT/client_name_db_name.tgz /var/lib/mysql/client_name_db_name

Kloxo-MR does not export php files to ASCII but makes a tar from /home/dir. Use the same method for mysql data as well. This is possible now because the system of mysql has become very stable and backward compatible too.

Thats it.

[MRatWork]

If you follow discuse in old forum.lxcenter.org you will found my 'method' (I call as 'ALT' backup) which the same as your 'raw method'.

The problem with this method:
1. Not work in innodb (also possible in Aria) storage-engine
2. Need stop mysql server before zipped process and start again after that because to make sure integrity of data
3. No other panel use this method (including MySQL Inc and MariaDB Inc) as 'alternative' method

That it.

[Kloxo-DR]

Hi Mustafa,

1. Not work in innodb (also possible in Aria) storage-engine

Thats is true. But now, Kloxo-MR concentrates on MyISAM.

2. Need stop mysql server before zipped process and start again after that because to make sure integrity of data

We do not need to backup procedures and functions.

To make sure integrity of data:

Old Server:
...........There is no need to stop mysql server BEFORE THE TAR BEGINS to copy
...........and compress the data. The only negative situation may occur is when
...........the database tables are updated and very big.
...........This depends on the size of the database.
...........Here, one could issue a LOCK TABLE command.
...........This would be the same when one makes a dump or a a dir copy.
...........Time to lock until a directory is copied _IS_ FASTER to dump procedure.

Old Server:
...........There is no need to stop mysql server DURING THE COPY PROCESS is going on.

Old Server:
...........If you want a consistent dump and sure integrity of data of database
...........WHILE ITS BEING MODIFIED you need to use --single-transaction
...........(if you only backup innodb) or --lock-all-tables.
...........Stop mysql server is not necessary.

New Server:
...........There is no need to stop mysql server
...........WHILE KLOXO-MR CREATES A NEW ENTRY of database, if absent.

New Server:
...........There is no need to stop mysql server
...........BEFORE THE TAR BEGINS to copy
...........and UNCOMPRESS the data under /var/lib/mysql/db_name.

New Server: Last step
...........There is no need to stop mysql server
...........to RELOAD THE GRANT TABLES on new entry of database.
...........Thereafter, mysql will recognize the directory as a database.

In a nutshell, your ALT method is appropriate for recent condition of Kloxo-MR server installations everywhere. regardless of the kernel or bits, the ALT method SHALL FUNCTION efficiently without errors and fears.

Copy, tar and untar and simple linux functions. Now, if a directory appears under the /var/lib/mysql, then it does not disturb mysql at all until the directory is registered as a database. The only exception that would disturb mysql server would be if the name of this directory is mustafa. Then, mysql would crash.

3. No other panel use this method (including MySQL Inc and MariaDB Inc) as 'alternative' method

Big companies do not use this method because they have to handle with different mysql versions and environment.

In that case, I would also not suggest to do anything like this.

In case of Kloxo-Mr, this fundamental pre-requisite is not there. All Kloxo-MR installation will have a standarized procedure of installlation and maintanence of the servers. Here, one can use a different approach than used by different companies.

If you do not implement, than thats fine. But if you do implement, it will not help me.