Backup/Restore not working

[lupetalo]

Moving all data from KloxoMR@Centos5.9 to KloxoMR@Centos6.4.
I have done this at least 4 times, but never with different OS so i guess that is problem. These are steps:

1. backup reseller account on old server
2. make same acount on new server
3. transfer backup file to correct place (/home/kloxo/client/USERNAME/__backup)
4. start restore on new server: step 1 and 2 (selecting and confirming) are ok, but when final step run it just extract all to /temp and stops

Like i seed this is done correctly in past so there is something wrong with backup/restore in new KloxoMR or something about OS.
New:

Code: [Select]

A. Kloxo-MR: 6.5.0.f-2013031822

B. OS: CentOS release 6.4 (Final) x86_64

C. Apps:
   1. MySQL: mariadb-5.5.31-1.el6.x86_64
   2. PHP: php-5.3.26-1.el6.x86_64
   3. Httpd: httpd-2.2.24-1.el6.x86_64
   4. Lighttpd: --uninstalled--
   5. Nginx: nginx-1.5.1-1.el6.x86_64
   6. Qmail: qmail-toaster-1.03-1.3.24.mr.el6.x86_64
      - with: courier-imap-toaster-4.1.2-1.3.12.mr.el6.x86_64
   7. Dns: bind-9.9.2-3.P2.el6.x86_64

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2006       1251        755          0        143        726
   -/+ buffers/cache:        380       1625
   Swap:         2047          0       2047Old:

Code: [Select]

A. Kloxo-MR: 6.5.0.f-2013031822

B. OS: CentOS 5.9 x86_64

C. Apps:
   1. MySQL: mysql-5.0.95-5.el5_9
   2. PHP: php53u-5.3.26-1.ius.el5
   3. Httpd: httpd-2.2.24-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: nginx-1.5.1-1.el5
   6. Qmail: qmail-toaster-1.03-1.3.24.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.12.mr.el5
   7. Dns: bind-9.9.2-3.P2.el5

D. Php-type (for Httpd/proxy): suphp_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2006       1952         54          0         14        513
   -/+ buffers/cache:       1424        582
   Swap:         3999       1208       2791

[MRatWork]

Don't make an 'wrong' opionion. Nothing change code related to backup-restore between 2 version. Also you can compare what's different code between version to https://github.com/mustafaramadhan/kloxo.

For example (for rpms branch): https://github.com/mustafaramadhan/klox ... 8576e4d0e3 with message 'update to 2013031823 (based on until 6.5.1.a.2013062301);...' (for .23) and https://github.com/mustafaramadhan/klox ... 8e5f4afef3 (for .22). And then you check to dev branch to compare code.

BTW, You can check backup/restore log inside /usr/local/lxlabs/kloxo/log to know what wrong with your restore process.

[lupetalo]

What file, there are a lot of them? One is named restore but empty... My opinion is based on pure logic, when something not working then is not working... Fresh system, only difference is 6.4 CentOS... No errors during operations, what could someone think other than something not working....

[mhzare]

i think this problem ralated to permision(file & director) or volume

if backup file more than 1 GB  (when extract in /tmp dir)?
i have this problem at last and solved with increase volume of /tmp dir

[lupetalo]

tmp is not partition it is part of "/" so it can be as much as it needs to. Funny thing, third try worked, but many of clients did not have any files od databases but were created... That is not new, same thing happening before. just needs to do one by one...

[mhzare]

do you have any backup file bigger than 1 GB (in extract ) or 400 mb (in zip format)?

for emample , if /tmp dir  mounted as a filesystem in /etc/fstab or /dev/shm with normal or public settings , volume of /tmp dir considered  1 Gig
when backup script will extract data and put into corect place face to small volume in /tmp and  restore script stop working

if possible , please check and put log file in this topic

log for restote at   /usr/local/lxlabs/kloxo/log/restore  
log for backup  at   /usr/local/lxlabs/kloxo/log/bakup  

-----emample backup log----------------
[root@vps log]# tail /usr/local/lxlabs/kloxo/log/backup
04:29 Jun/24/2013: *** Backup from '*****' user - BEGIN ***
04:29 Jun/24/2013: Taking backup of 'client:*****'
04:30 Jun/24/2013: Taking backup of 'mysqldb:*****'
04:40 Jun/24/2013: Taking backup of 'mysqldb:*****'
04:40 Jun/24/2013: Taking backup of 'mmail:*****'
04:40 Jun/24/2013: Taking backup of 'mmail:*****'
04:43 Jun/24/2013: * Kloxo Backup on 2013-Jun-24 at 04 Hours - Kloxo Backup Succeeded for '*****' to '123.123.123.123'
04:43 Jun/24/2013: *** Backup from '*****' user - END ***
[root@vps log]#
----------

after check log file you can find problem then go to solve

[lupetalo]

there is no /tmp in fstab, but there is /dev/shm ?

Code: [Select]

none             /dev/shm      tmpfs   defaults                    0 0

[mhzare]

i ask you  , plase answer it
do you have any backup file bigger than 1 GB ( in extarct) or 400 mb (in zip format) ?

[lupetalo]

i ask you  , plase answer it
do you have any backup file bigger than 1 GB ( in extarct) or 400 mb (in zip format) ?

i do, both

[mhzare]

if you have a smal backup file (100 mb in zip format),  please restore  it  and check for  sucessfull restore
(before ,try to empty /tmp dir )
after this you can Confidence for Health of kloxo-mr code and system

please doing this and write this result here

[lupetalo]

if you have a smal backup file (100 mb in zip format),  please restore  it  and check for  sucessfull restore
(before ,try to empty /tmp dir )
after this you can Confidence for Health of kloxo-mr code and system

please doing this and write this result here

I dont have problem with small backups.
what this means:

Code: [Select]

none             /dev/shm      tmpfs   defaults                    0 0

[mhzare]

plase noticed

in backup prosess in old server , if you have problem in volume of /tmp dir ,  
you havent corect backup client for transfer
in fact , you try to restore Incomplete backup in new server
 
i hope you understand my notice

[lupetalo]

plase noticed

in backup prosess in old server , if you have problem in volume of /tmp dir ,  
you havent corect backup client for transfer
in fact , you try to restore Incomplete backup in new server
 
i hope you understand my notice

How can i know if i have problem with /tmp?
And why, if i have, kloxo dont give error message?

[mhzare]

if you have a smal backup file (100 mb in zip format),  please restore  it  and check for  sucessfull restore
(before ,try to empty /tmp dir )
after this you can Confidence for Health of kloxo-mr code and system

please doing this and write this result here

I dont have problem with small backups.
what this means:

Code: [Select]

none             /dev/shm      tmpfs   defaults                    0 0

if you can restore clinet with small volume of file , then your kloxo-mr work normally in new server  and all things is ok
for solve your problem with client with larg volume  , plase read my last post and check /etc/fstab in old server for  get a correct backup and then transfer it and restore

[lupetalo]

if you have a smal backup file (100 mb in zip format),  please restore  it  and check for  sucessfull restore
(before ,try to empty /tmp dir )
after this you can Confidence for Health of kloxo-mr code and system

please doing this and write this result here

I dont have problem with small backups.
what this means:

Code: [Select]

none             /dev/shm      tmpfs   defaults                    0 0

if you can restore clinet with small volume of file , then your kloxo-mr work normally in new server  and all things is ok
for solve your problem with client with larg volume  , plase read my last post and check /etc/fstab in old server for  get a correct backup and then transfer it and restore

thanks for help,but i just dont understand what are you saying, and you dont reply to what i am asking. Will try google for answers regarding my question.