Restore Failed

[pakgalaxy]

i have 3.9 GB admin backup and now restored after reinstallation of Kloxo MR, but after restoration process disk sizes in accounts shown accurate but there are no files in clients accounts .

[Kloxo-DR]

Hi,

i have 3.9 GB admin backup and now restored after reinstallation of Kloxo MR, but after restoration process disk sizes in accounts shown accurate but there are no files in clients accounts .

Yes, if there are no files in the respective home directory, then they remained in the /tmp/backup*** dir.

Check if they are there. If yes, then your restore is broken and Kloxo-MR shall not restore the backup.

[pakgalaxy]

What should i do now? Again start the restore process?

[Kloxo-DR]

Hi,

What should i do now? Again start the restore process?

The retsore function does not repair anything at the time of restore, the same as making backup does not repaire anything. If it failed once, then Kloxo-MR shall - without emotions for ou - fail again and again.

If you changed your server and restore fails then do the following:

1) Make backup of existing clients of the new server, if any.

Delete all clients on the new server. This will delete all domains, databases and emails of clients.

2) Create clients with the same name on the new server. Create domains of those clients the same as in the earlier installation.

3) Start the restore function. Select the database and domain names you want to restore.

See if this step goes further and does not break it. If there iis no change, then you have a problem.

Now, if you do not have enough space or RAM, this is anathor problem while restoring large tart file. Check this first before following above steps.

[MRatWork]

Investigate /usr/local/lxlabs/kloxo/log/restore. You can see something in restore process

[Kloxo-DR]

Hi Mustafa,

Investigate /usr/local/lxlabs/kloxo/log/restore. You can see something in restore process

This file does not speak much about the troubles except that it says where it has stopped. It does not give more information on why it has broken or captures the debug information at that point.

Although this could be an important hint if it, for e.g., stopped working on a domain or a mail account, then you know that that domain or a mail account gave a problem.

[MRatWork]

Restore process in Kloxo-MR try restore with different compare to Kloxo official.

If KLoxo-MR found error in certain step (let mysql data problem), Kloxo-MR will be jump to next process. It's work in my experience when restore for VPS of this forum.

So, you didn't found any information in 'restore' log that mean no process to restore process. One possible is limiting temp directory (remember, in certain OpenVZ VPS, using memory for /tmp).

[Kloxo-DR]

Hi Mustafa,

As this thread says "Re: Restore Failed", restore fails many times. This is a problem right from the begining of lxadmin. Further, a restore process must also update certain parameters like web ip address, etc. This is currently not the case.

Is it possible to develop a function to check if a backup will also restore everything, like some kind of integretiy check? For e.g. if it could go through a pseudo restore immediately after a backup is made, then it could be known if this file is safe.

A modification of restore process and an addition of some more enhancements is required.

[MRatWork]

Many reasons why restoring is fail because Old version of Kloxo:

1. possible with more then 16 chars of database name and database username --> mysql only permit username no more than 16 chars
2. possible directory with 'space' or another 'strange' chars --> because no validate for it
3. Database using innodb as storage-engine but new server using 'skip-innodb'
4. and many more