No problem with a manual backup, stored on S3, but aklazy plugin is not triggering the expected backup, even in test mode. No third-party SEF used, documentation read, to no avail. J! 1.5.20.
Any idea ?
Any idea ?
#8599 Lazy Scheduling
Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a
Latest post by nicholas on Tuesday, 07 September 2010 02:11 CDT
Tuesday, 31 August 2010 06:30 CDT
dlb
The Lazy Backup plugin depends on traffic on your site to trigger the backup steps. If there are no page reads, there is nothing to trigger the backup steps. If your site has enough traffic to trigger the backup, then we need to look for another cause for the problem.
Dale L. Brackin
Support Specialist
English: nativePlease keep in mind my timezone and cultural differences when reading my replies. Thank you!
????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)
Sunday, 05 September 2010 21:59 CDT
rottenberg
The Lazy Backup plugin depends on traffic on your site to trigger the backup steps. If there are no page reads, there is nothing to trigger the backup steps. If your site has enough traffic to trigger the backup, then we need to look for another cause for the problem.
I installed AKLAZY yesterday on 2 sites. I tested the test mode on 1 site : it was backing up.
I tried the normal mode (at 00:00) I found no backpup (on the 2 sites)
What are you calling
If your site has enough traffic to trigger the backup.
Where can I find the documentation about AKLAZY (as in the plugin asked to read before using)
1 mot de passe d'origine
Sunday, 05 September 2010 22:30 CDT
yvesg
The Lazy Backup plugin depends on traffic on your site to trigger the backup steps. If there are no page reads, there is nothing to trigger the backup steps. If your site has enough traffic to trigger the backup, then we need to look for another cause for the problem.
There is traffic on the site, but the backup is not triggered, even in test mode.
Where can I find the documentation about AKLAZY (as in the plugin asked to read before using)
See here.
Sunday, 05 September 2010 22:42 CDT
nicholas
Akeeba Staff
Manager
Just to confirm, are you using the latest plg_aklazy published with Akeeba Backup 3.1.RC1?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Sunday, 05 September 2010 22:48 CDT
rottenberg
here a hard copy of the version of Akeeba Backup : Akeeba Backup Professional 3.1.rc1 (2010-08-30)
I downloaded the plugin yesterday from the address you gave me in another post.
On one site I used AKLAZY in test mode successfully at 15:30. I thought I get a new backup at 00:00 today.
I got nothing.
On another site (with the same config) I didn't do the test mode. I also got nothing.
PS : I'm using JOOMLA 1.5.20
On both sites updates have been done yesterday afternoon.
I downloaded the plugin yesterday from the address you gave me in another post.
On one site I used AKLAZY in test mode successfully at 15:30. I thought I get a new backup at 00:00 today.
I got nothing.
On another site (with the same config) I didn't do the test mode. I also got nothing.
PS : I'm using JOOMLA 1.5.20
On both sites updates have been done yesterday afternoon.
1 mot de passe d'origine
Sunday, 05 September 2010 22:55 CDT
nicholas
Akeeba Staff
Manager
I think there is a misconception about the time. The time you set in plg_aklazy is the server's time. Most servers are in a different timezone than their webmasters. For instance, let's say that a server is in GMT-7 and you are in GMT+2. When it's 00:00 in your server's timezone (GMT-7) it is 09:00 in your timezone (GMT+2), as the two timezones are 9 hours apart. If there is no backup by 16:00 today even though there is adequate traffic then it is a bug, otherwise it's a timezone difference. FYI, it is not technically possible to automatically or manually select the timezone used in the plugin's configuration, as the backup has to run no matter if and which user is currently logged in your site at the time the plugin runs (each Joomla! user carries his own timezone information and would confuse the time calculation).
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Sunday, 05 September 2010 23:22 CDT
yvesg
Just to confirm, are you using the latest plg_aklazy published with Akeeba Backup 3.1.RC1?
Sorry, I had the previous version. It's working now.
One little thing: the hour written in the name and in the description of the archive is 10:10 instead of 11.10 (my local time is UTC +01:00). [Edit: written before your last post]
Monday, 06 September 2010 07:27 CDT
nicholas
Akeeba Staff
Manager
OK, I'm glad that the new version works :)
Regarding the time displayed in the archive description, remember that I just said that we have to use the UTC timezone. As a result, everything be calculated using UTC, including the description. It is part of the known limitation when working across multiple timezones in PHP.
Regarding the time displayed in the archive description, remember that I just said that we have to use the UTC timezone. As a result, everything be calculated using UTC, including the description. It is part of the known limitation when working across multiple timezones in PHP.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Monday, 06 September 2010 07:49 CDT
rottenberg
I think also it's working
but 2 questions :
[ol]the server is in FRANCE (UTC +1) I asked the backup each day at 00:00. I found a backup done by AKLAZY at 09:57[/ol]. Does the systems need a user to be connected to begin the backup or (as with CRON) he begins at 00:00 UTC 0 ?
[ol]the save lasted more than 2 hours for 50Mo. With the manual save it lasts less than 5 minutes. Why a so great difference ? Is the backup only working when a user is connected in the site ?[/ol]
but 2 questions :
[ol]the server is in FRANCE (UTC +1) I asked the backup each day at 00:00. I found a backup done by AKLAZY at 09:57[/ol]. Does the systems need a user to be connected to begin the backup or (as with CRON) he begins at 00:00 UTC 0 ?
[ol]the save lasted more than 2 hours for 50Mo. With the manual save it lasts less than 5 minutes. Why a so great difference ? Is the backup only working when a user is connected in the site ?[/ol]
1 mot de passe d'origine
Tuesday, 07 September 2010 02:11 CDT
nicholas
Akeeba Staff
Manager
There are two different ways to automate the backup.
The first way is to have a machine trigger the backup. This is what CRON and Remote Control's scheduling option do. The downside is that either your server must support scheduling (CRON) or you have to leave your PC turned on (Remote Control).
The second way, AKLazy is using, triggers the backup on user activity. As long as someone visits your site after the scheduled backup time, the backup operation begins. However, backing up a site can't be performed in a single step without PHP timing out in mid-process (if that wasn't the case there would be no raison d'etre for Akeeba Backup). Akeeba Backup's top feature is that it can "chunk" the backup in multiple steps to ensure that a smooth, timeout-free backup can be achieved. This also means that you need adequate user activity so that all the backup steps can run.
This brings an interesting point in our discussion. How many steps are required to take a full site backup and how many users you have every night since 00:00? If there's not enough user activity, having the backup run at 09:57, together with the first European visitors to your site seems very rational. This also explains the 2 hours vs. 5 minutes you mention. If one user comes at 09:57, stays for 30 seconds and leaves, AKLazy will have to wait for the next visitor to continue backup. If you don't have thousands of visitors per day, again, this behaviour is absolutely expected.
The bottom line is, as you guessed: the plg_aklazy plugin runs the backup only when a visitor browses your site.
The first way is to have a machine trigger the backup. This is what CRON and Remote Control's scheduling option do. The downside is that either your server must support scheduling (CRON) or you have to leave your PC turned on (Remote Control).
The second way, AKLazy is using, triggers the backup on user activity. As long as someone visits your site after the scheduled backup time, the backup operation begins. However, backing up a site can't be performed in a single step without PHP timing out in mid-process (if that wasn't the case there would be no raison d'etre for Akeeba Backup). Akeeba Backup's top feature is that it can "chunk" the backup in multiple steps to ensure that a smooth, timeout-free backup can be achieved. This also means that you need adequate user activity so that all the backup steps can run.
This brings an interesting point in our discussion. How many steps are required to take a full site backup and how many users you have every night since 00:00? If there's not enough user activity, having the backup run at 09:57, together with the first European visitors to your site seems very rational. This also explains the 2 hours vs. 5 minutes you mention. If one user comes at 09:57, stays for 30 seconds and leaves, AKLazy will have to wait for the next visitor to continue backup. If you don't have thousands of visitors per day, again, this behaviour is absolutely expected.
The bottom line is, as you guessed: the plg_aklazy plugin runs the backup only when a visitor browses your site.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!