Support

Hello!

The Lazy Scheduling plugin was deprecated in Akeeba Backup 3.2.5 and completely removed since Akeeba Backup 3.3.a1. It is no longer supported. Please use a CRON job as per [ur=https://www.akeebabackup.com/documentation/akeeba-backup-documentation/automating-your-backup.html#frontend-backup]these instructions[/url].

Regarding the backup issues, please try the following settings:
- Temporary directory: [DEFAULT_OUTPUT] (all caps, include the brackets)
- Minimum execution time: 1 second
- Maximum execution time: 10 seconds
- Runtime bias: 75%

If this still fails, please note that you have a directory (ebay/pictures) which seems to have several thousands of files. There is an objective issue here. Producing a list of each directory's files has to happen in one go. Having thousands of files means that it takes a lot of time and a lot of memory. While you have plenty of memory for this operation, you don't have a lot of available time as the PHP timeout limit is 30 seconds and the process seems to be taking around 43-44 seconds, which is probably why you get the "The process was aborted on user's request" error message in the log file. The only two ways to work around that are:
1. Use Files and Directories Exclusion to exclude this directory, therefore not backing it up.
2. Ask your host to raise the PHP max_execution_time to 60 seconds so that you can successfully backup this directory.

Please let me know which of those recommendations worked in your case.

Hello Paul,

No log file was attached. Can you please try placing your log file in a ZIP archive and attaching the ZIP file here? There is an upload limit of 2Mb per attachment.

Regarding the Lazy Scheduling plugin, it was discontinued for various reasons. For starters, it made use of AJAX and IFRAMEs which made your site appear to load much slower than usual. THis was killing your sites' SEO ranking. Sometimes -especially if your file permissions were a bit off- it would cause error messages to be printed out in the top of each front-end page. Sometimes it crashed the Javascript on the page. Some other times it went berserk and was continuously taking backups, filling up your hard disk and bringing down your site. Some people reported broken backups. And the list goes on and on. The root cause of all of those problems was the unreliability of several hosts. The only workaround was to use a better host, but this kinda beats the purpose as the better hosts allow CRON jobs which are more reliable.

My suggestion is to use a proper host which allows CRON jobs, like Rochen, CloudAccess.net or iRedHost.

The log is also missing from your second post :)

Transferring the archive file by FTP takes a lot of time, so you get a timeout error. What you have to do is to go to Akeeba Backup, click the Configure button next to the Archiver Engine and set the Part Size for Split Archives to 15Mb (you have to use the Custom option to set that). This will split your archive to two files, one .zip and one .z01. Since each one of them is being transferred in less than 30 seconds, you don't have a timeout error and your backup works.

PS: Rochen backs up your site's files twice per day on a secondary disk on the same server and every second day on a remote NAS. Moreover, they offer a web interface to the last month's backups on the NAS, so if you screw up on a single file you can easily restore it. It works like Time Machine, only it's on the web. Having that protection as well as Akeeba Backup Pro is unbeatable. You have to really try very hard to lose data. Trust me, I know (I am hosted on Rochen and I have screwed up files on my sites many times) :)

You're welcome!

Regarding Rochen, they have two datacentres. One of them is in US (Dallas), the other in UK (London). This site is on the US datacentre. My personal blog is on the UK datacentre. If you want more info about the UK offering, you can check out Rochen's UK site.

Merci!