The free forums are no longer in use. It remains available as read-only archive.
Log In
Home
Topic RSS
8:05 pm
February 26, 2013
Offline
I can't begin to explain how relieved i was to find Xcloner. I must have tried pretty much every other backup plugin for WP. My host does not allow WP-cron and is a general pain in the ... anyway, I seem to have automatic backups being generated ok and sent over to Amazon S3 (which is all new to me). However, can anyone explain why there is only ever one zipped bundle at any time. Each time I do a backup (by cron) it simply replaces the previous backup. So, the backup is made under Public, Admin, Backup and this is then sent to S3. At both the host FTP and the S3 end the same backup appears, replacing the older version. I need to keep 2 weeks work of backups. i have altered the settings in Xcloner but nothing seems to alter whether previous backups are included or not. I would have expected the button to include previous backups to have done something but it doesn't. Any thoughts or advice,
Thanks,
gareth
8:38 pm
September 26, 2010
Offline
That's probably because you've used a custom name for the backup, if you want to generare a unique name , simply leave the backup field name empty! Hope it helps...
11:54 pm
February 26, 2013
Offline
That did help. Thank you very much. Now each backup is seperate within the FTP admin backup folder. Unfortunately, it has thrown up another problem. The first new backup is created in the FTP admin backup folder and is transfered to S3. However, when a second backup is created in the FTP admin backup folder it is not transfered to S3. In order for the next backup to be transfered to S3 i need to manually delete the orginainal backup in my FTP folder. Again, I've tried altering different settings but can't find the solution. Can you help?
Thanks,
Gareth
6:28 am
September 26, 2010
Offline
Do you have a cron log output from when the second backup run? are there any errors?
11:46 am
February 26, 2013
Offline
I woke up this mornig to find that the automatic backup to S3 by cron had worked without any problem. The backup was created in the FTP and had been copied over to S3 ok. I can only think that the reason it did not work before is that I was using the test command function for the scheduled task rather than letting it fire at the right time naturally.
Oh!!!! i just tested the 'test command' function again to see if it did the same as last night and it did not. If simply ran the cron correctly and a backup was created in S3. For whatever reason last night it would not transfer over to S3 if another copy existed in FTP. Now it doesn't seem to matter. I swear the only thing different is i have left it alone to run a full natural cron in the mean time. Oh well, so long as it is working now.
The log of the failed cron was only generated by my cpanel and not emailed to me so i dont have a copy i'm afraid. I only have emailed copies of logs of successful backups.
May I ask, the 'delete old backups' function in the cron settings, does this just remove the old ackups from the FTP files or does it also instruct S3 to remove? I guess I can get S3 to remove older files using the Lifecycle function.
Thank you for such rapid help.
Best wishes,
Gareth
11:55 am
September 26, 2010
Offline
The delete option only deletes the backups from the local or ftp server if ftp transfer was enabled, it does not delete S3 backups!
And yes, the LifeCycle option from the S3 service is the best way to go! Ovidiu
1 Guest(s)
