Do you get the same issue with 1.3?
Do the files exist in ‘wp-content/backups’?
Thread Starter
joni1
(@joni1)
No they don’t. Only the old backups (from when it used to work) are there.
Can you delete those files and see if new ones are created?
Also, how big are the files?
Thread Starter
joni1
(@joni1)
I’m sorry, I just realized I have version 1.2.2 installed. So, I upgraded and ran the backup and this is what I’m getting:
Backup Log
03:45:21 : A fatal error occured: Error creating sql dump file.
03:45:21 : Creating SQL backup of your WordPress core.
03:45:20 : This php installation is running in safe mode so the time limit cannot be set. Click here for more information.
03:45:04 : Backup started on Friday October 5, 2012.
also, deleted the 2 old backup files which where 2.5MB combined.
We are getting somewhere.
That error is probably because the ‘wp-content/backups’ is not writeable. What are the file permissions of it?
Thread Starter
joni1
(@joni1)
It was 775, I changed it to 777 now the backup seems to be running (still hasn’t completed):
03:51:52 : Approximately 0% complete.
03:51:46 : Approximately 0% complete.
03:51:40 : Approximately 0% complete.
03:51:34 : Backing up WordPress path at (/home/joniamir/domains/jonitest.drp.co.il/public_html/).
03:51:34 : Creating SQL backup of your WordPress plugins.
03:51:33 : Creating SQL backup of your WordPress core.
03:51:32 : This php installation is running in safe mode so the time limit cannot be set. Click here for more information.
03:51:19 : Backup started on Friday October 5, 2012.
I do ponder whether permitting 777 doesn’t compromise the privacy of my backup data?
777 is not very secure because it allows the unix guest user to execute scripts inside that directory, 766 is a little bit safer.
The backup plugin creates an empty ‘Silence is golden’ file to stop the contents of the directory being served via apache.
Do any files make it to Dropbox?
10-4 on the permissions. Yes, files are making it to Dropbox, but not sure if all of them are making it. This morning’s error message is a bit different:
00:01:36 : A fatal error occured: Forbidden. Your app is making too many requests and is being rate limited. 503s can trigger on a per-app or per-user basis.
00:00:20 : Backup started on Thursday October 25, 2012.
FYI… when I initiate the WPB2D backup manually (Start Backup). The backup logs report success up to 99% and then this error message:
14:31:21 : A fatal error occured: Error writing to sql dump file.
14:23:15 : Creating SQL backup of your WordPress plugins.
14:22:48 : Creating SQL backup of your WordPress core.
14:22:45 : Backup started on Thursday October 25, 2012.
Michael… any more takes on this thread? What processes could be executing during that last 1% of the backup? Looking for closure.
The problem is writing to the SQL file. I am not sure why its not allowed.
What host are you using?
Media Temple. The phpmyadmin dump of the database is 71MB. Could the size of this WP database be the issue with server’s PHP?
This thread has been resolved. Our WordPress site is with Media Temple. This code was added to our .htaccess file:
<Files “wp-cron.php”>
Allow from All
Satisfy Any
</Files>
This allowed WPB2D plugin to backup to 100% completion. Sorry about the double post. Glad to be able to stick with this nice backup plugin. Donation coming.
