The free forums are no longer in use. It remains available as read-only archive.
Log In
Home
Topic RSS
9:53 pm
Hi, first of all, great idea for this plugin! I just made a mistake while deleting some users on my wordpress blog and my last backup was from march… So now I'm setting up autobackup 🙂
But to my problems:
1.
When I start the backup of the files, without tar-compression, the backup takes ages and at some point (around 20%) the current-state pages does not reload itself automatically. I can then reload it manually ("Continue link: click here >>") but this takes very long and sooner or later I get a wordpress admin page with no trace of the xcloner-frame except a "An internal server error occurred. Please try again later".
When I then hit the "view backup", I can see properly named .tgz and .tgz.tmp files which are far too small to be complete.
2.
When using tar-compression, I do not get the above mentioned problem and everything goes very fast, but I can't open the file with 7zip after downloading it to my pc.
Anyone got an idea what could be the reasons for the problems? Solving either would make solving the other obsolete…
10:08 pm
September 26, 2010
Offline
Hi there! Have you checked if you have TAR support on your server?(XCloner Config -> Info tab)
If so, try and set the TAR Active checkox checked, and also set the Manual Backup option to No and see how it goes.
If you still get timeout issues, and you can access to a cron manager, I would advise using that one to get a complete cronlog output
Hope it helps! As a note, try and exclude the larger parts from your site like large files and see if it helps also.
Ovidiu
6:05 pm
Hi, thanks for the quick answer and excuse my late reaction 🙂
And reenabled tar and disabled manual backup and excluded the biggest part of my website (photo gallery). I want the backup to be sent to me via email, as I do not have another ftp-server and do not use amazon s3 (any chance of dropbox support coming? webdav?).
The Backup then runs, when triggered through http://www.my_url/wp.....r.cron.php and I get a working tgz-file in my backup directory now.
But sending the email is what doesn't work: I got an out of memory error, although the backup (and the in the error message mentioned allocated amount) is not bigger than my memory limit (64M).
Here is the error message:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 28521027 bytes) in /home/www/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php on line 432
Another error I get, which is not really a problem and doesn't break anything, is the following:
Warning: date() [function.date]:
It is not safe to rely on the system's timezone settings. You are
*required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those
methods and you are still getting this warning, you most likely
misspelled the timezone identifier. We selected 'Europe/Berlin' for
'CET/1.0/no DST' instead in /home/www/wp-content/plugins/xcloner-backup-and-restore/cloner.functions.php on line 1881
6:13 pm
September 26, 2010
Offline
The email feature could fail for large files as email attachments are usually size limited by your email service provider. However that error you are receiving is related to the memory_limit which needs to be increased, so try setting that to 128M and see if it helps.
Thanks for reporting the date error, i will look into it.
Ovidiu
6:36 pm
Thanks for your quick help. I set the memory-limit higher, but as I can't restart my apache server (shared hosting, surprised I could edit my php.ini...) I'll have to wait to see the effect.
But for now, I set up a backup that only backs up my databases and saved it as a seperate cron job. Problem is: the file I get (both via email and in the backup folder of my server) does only include one .sql file and thus only one database of my two.
I selected the second database in the cron-config tab and both the cloner.cron.php as well as the log-email I get show the names of both dbs to be succesfully backed up.
8:23 pm
September 26, 2010
Offline
OK, i will have a look to see if the cron code is working properly when multiple databases are selected for database only backups, they might get excluded for some reason along with the other files
Ovidiu
9:51 pm
Thanks! Great support!
I don't need premium support - is there some alternative way to support you? Donations or something?
9:22 am
September 26, 2010
Offline
Thank you Klaus, we have put a donation page here /support/make-a-donation/
Regards, Ovidiu
9:30 am
September 26, 2010
Offline
I've re-tested the multiple databases cron only backup and it works correctly, make sure your cron config was re-saved after adding the extra databases to it
Ovidiu
4:12 pm
I checked and rechecked and reconfigured – the second DB just is not in the tgz file… Also, the manual backup now doesn't include the second DB either – but also says it does…
Here is the log from the cron:
Archive Name: backup_2010-12-10_17-02_www.my_url.de-sql-nodrop.tgz
Number of Files: 0
Size of Original File: 0 bytes
Size of Archive: 360.36 KB
Database Backup: xxxxx_db1: Backup Completed ( 1.86 MB )
xxxxx_db2: Backup Completed ( 294.36 KB )
### END REPORT
Backup Done
Backup file: /home/backup/backup_2010-12-10_17-02_www.my_url.de-sql-nodrop.tgz
Sending mail with backup
/edit: found the cause: when I deactivate "tar" I get both DBs in the backup file. Strange enough, but a working work around for now.
1 Guest(s)
