ChrJFri
Forum Replies Created
-
Hello, did another 1.6.4. manual backup this morning. All OK except still no copy of ‘wp-includes’ in the archive. And still have to press cancel at the end of process (no big deal – but I can see how this could lead to corruption if one was to quick on the cancel button). Does anyone have any suggestion??? Thanks!
Ran 1.6.4 manually this am. Although “Manage Backups” says backup complete. Page still shows “creating zip archive”. Filezilla confirms that backup is still being created. Now I can press “Cancel” button and process stops as evidenced by Filezilla. Checking download archive, I notice that there is still no ‘wp-includes’ folder. If I do FTP download of ‘wp-includes’ it is 6.3Mb. According to 1.6.4 my site size is 97Mb. The archive manually created today is 8.6Mb (without the ‘wp-includes’ which does not get backed up).
I also notice I have two sql files. I will check with Hosting Control to see why this is. In case there is good reason to have two sql’s, is Backup WordPress limited to one only ? Could this be causing the partial backup and the hanging of the plugin ? Thanks for all your input.V 1.6.4 resulted in a backup that is 3x smaller than the first backup completed under 1.5.1.(14Mb vs 41Mb). The site is new and I am adding posts not taking anything out so I don’t understand why the archive might be so much smaller with 1.6.4. Again, there is no ‘wp-includes’ folder in the archive. I find that concerning. Has everyone else checked the contents of the archive and can someone verify that the ‘wp-includes’ folder is indeed part of a regular backup and needed for a normal restore ? Additional info: if I set 1.6.4 to “Auto Backup” it immediately launches into a backup routine although the normal set time is nowhere near. If I set to “Manual Backup this doesn’t happen. Instead 1.6.4 sizes the database and reports back. It is currently reporting a size of 97Mb. I’m no expert in compression but it seems to me that the last archive size of 14Mb is a little light for a dB of 97Mb. Can anyone tell me if this is normal (keeping in mind that the ‘wp-includes’ folder does not get backed up for the moment. Thank you all for the help.
My last backup with 1.5.1 failed as well. It seemed to be running for several hours from what I could see in Filezilla and even started creating the .sql file, said backup is running etc.. When I checked back in to Filezilla this morning it did not show a new entry for 1/10. The last entry is for 1/9 but that was done with 1.6.3 and is less than 1Kb in size. I managed to do a manual backup of the .sql through the GoDaddy host and that one completed well and is 1.3MB in size. Hope you can fix this, manual backups with GoDaddy are a pain. Thanks…
@myblog. Process has been running for an hour now and seems to just hang there. This is 1.5.1 as suggested. I can email a screenshot if you like.
Thanks myblog ! Will try it and report back.
@myblog, for those of us who never d’loaded 1.5.1, where can we find a copy to try ? Thx.
Thanks for the quick reply Tom ! Just wrote as requested.
To Tom, I also get the error message that myblog reported 4 days ago.At the end of the routine I get a report in Manage Backups that a backup was done but the backup file is 618B only. Backup runs for several minutes. At first I thought everything was fine until I tried your Restore instructions and realized I had nothing in case of disaster. The sql file seems to be created (1.4MB) but disappears once the process ends. Any thoughts on what might be wrong on my side and steps to correct. Thank You.