Support

Akeeba Backup for Joomla!

#13099 Problem with Automating Backup

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, 31 July 2012 10:52 CDT

Tuesday, 31 July 2012 10:18 CDT

user45774
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
https://www.akeebabackup.com/documentation/troubleshooter/abautomation.html
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.2.17
MySQL version: (unknown)
Host: Site5
Akeeba Backup version: 3.5.1

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
I am trying to automate my backup with a cron job. It seems to be trying to run from looking at the log earlier, I saw the following error message, but I am now not seeing this in the log at all, which is weird. zip of log file attached.

[120730 21:19:12] Kettenrad :: Attempting to load from database (backend)
[120730 21:19:12] -- Stored Akeeba Factory (backend) not found - hard reset
[120730 21:19:13]
[120730 21:19:28] Kettenrad :: Attempting to load from database (backend)
[120730 21:19:28] -- Stored Akeeba Factory (backend) not found - hard reset
[120730 21:19:28]
[120731 04:59:55] Kettenrad :: Attempting to load from database (backend)
[120731 04:59:55] -- Stored Akeeba Factory (backend) not found - hard reset
[120731 04:59:55]

Tuesday, 31 July 2012 10:24 CDT

nicholas
You are looking at the "Backend" origin. This is where back-end backups, taken through the component's interface, are shown. Please go to Akeeba Backup, View Log and select the "Command line" or "Front end" origin, depending on how your CRON job is supposed to run. If you are using the akeeba-backup.php script it's the "Command line" origin. In any other case it's the "Front-end" origin.

If you see neither of these origins then your CRON job is not executing at all. This means that you have a setup issue of the CRON job itself and none of my code has executed yet. In this case, please consult your host. I can't help you because I can't possibly know how your host has configure their server or have any control upon your CRON job setup.

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!

Tuesday, 31 July 2012 10:31 CDT

user45774
OK, the "Command line" option is not there. Does this mean that a) I have neglected to set something up; or b) the cron job just isn't happening and I have to go to my hosting company?

I confirmed this command:

wget --max-redirect=10000 "http://www.yoursite.com/index.php?option=com_akeeba&view=backup&key=YourSecretKey"

(obviously with the necessary changes)

They said this is alright. Is my next step to them?

Thanks,
Andy

Tuesday, 31 July 2012 10:34 CDT

nicholas
No, Andy. Read my post above, carefully :) You are definitely not using the cli/akeeba-backup.php script, you are using wget in your CRON job. This means that you should be looking for the "Front-end" origin. Is it there?

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!

Tuesday, 31 July 2012 10:37 CDT

user45774
The only thing that is there is backend.

Tuesday, 31 July 2012 10:44 CDT

nicholas
This means that the CRON job is not running, you have the wrong secret key or you have not enabled front-end backups in your Akeeba Backup Component Parameters. Does the CRON daemon of your host's server send you an email telling you if the CRON job has run?

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!

Tuesday, 31 July 2012 10:48 CDT

user45774
It's looking like it wasn't turned on. I find the whole concept of front-end vs. back-end confusing backup confusing. You are essentially backing up the whole site, what does front and back refer to in this case?

Thanks for your time,
Andy

Tuesday, 31 July 2012 10:52 CDT

nicholas
It's the backup origin. The concept is explained in the documentation, albeit it's also in the meaning of the word itself. The origin of something indicates where it came from. That's what it means in Akeeba Backup, too. Where did this backup come from? Did it come from the back-end of the site? The front-end? A command line application? The JSON API used by Remote CLI and other tools? This is extremely important information. After all, the same Akeeba Backup profile can be executed through any of those origins which behave completely differently. We must know where the backup came from to provide support, hence the different origins in the Log View page.

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!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!