Akeeba Backup for Joomla!

Monday, 30 August 2010 02:30 CDT

pjdevries

Using Akeeba Remote Control version 2.5.0.36 on Windows Vista 64 bit in combination with Remote Control Plugin version 2.5, I'm experiencing the following error in/after the post-processing stage:
[indent]Access violation at address 005361C2 in module 'AkeebaRemoteControl.exe'. Read of address 00000000[/indent]

Is this a known issue and can it be solved?

Monday, 30 August 2010 08:26 CDT

nicholas

This looks like an FTP initialization error. If you disable downloading the backup archive does it work? If so, please try modifying your FTP options, especially unchecking the "Active mode" and "Keep alive" boxes. You can test the new options without running a new backup: right click on a site, select manage backups, select a backup from the list and click on Download.

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!

Friday, 10 September 2010 01:48 CDT

GVerheij

I experience the same error. I've just upgraded Akeeba backup (Component and plugin) on a site from 3.0.b2 to 3.1.rc1 on a Jooma 1.5.20 site. Akeeba Remote Control was working just fine with the old version. Also it works just fine now with sites with 3.0b2 installed.
I've upgraded Akeeba Remote Control (exe) on Windows 7
The FTP-connections to the site tests OK in Akeeba Remote Control on Windows 7.
Unchecking Active mode and Keep Alive: same problem, no improvement.

However, it is possible to make a backup with the Akeeba component on the Joomla backend.
Right click (manage backups) on the site in Akeeba Remote control worked ok: Downloaded the file to my computer.

Please solve this issue, because making a backup of all my sites in one run with Akeeba Remote Control is not possible as long as this error occurs... Thanks!

Friday, 10 September 2010 02:44 CDT

nicholas

If there is no backup made whatsoever using the Remote Control after you upgraded you have a different problem, it's already solved and all you have to do is install the updated plg_jpremote on your site. If the backup completes but can not be downloaded, please post your Remote Control log file so that I can see what's going on.

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!

Friday, 10 September 2010 02:58 CDT

pjdevries

I appologize for not responding to your previous reply Nicholas. I have been very busy and haven't been able to spent time on this issue and get back to you.

Do I understand correctly that a plg_jpremote update might solve the problem?

Maybe a bit off topic, but do you advice to stick to official releases for production sites or are betas and/or release candidates stable enough for day to day use?

Friday, 10 September 2010 03:05 CDT

nicholas

The plg_jpremote plugin is a "bridge" between the backup engine and the XML-RPC service. As the engine undergoes changes from one version to the other, the plugin has to be updated as well. This is why the plg_jpremote published with Akeeba Backup 3.0 won't work with Akeeba Backup 3.1 and vice versa. As a result, you must upgrade the component together and the plugin at the same time.

Alphas are not generally stable for production use. However, the betas are generally stable enough for production use and have undergone testing by our team. However, since they have not been tested with any possible server setup, they might have some bugs. As we always suggest in the event of an upgrade, take a backup with the new release and test it by restoring it on a local PHP 5.2 server (i.e. Zend Server CE for PHP 5.2). If you bump into any issues, post them here and we'll fix them a.s.a.p. Release Candidate (RC) versions are considered very stable, but we would like our users' feedback to make sure they are stable enough. After 1-2 weeks of widespread use we promote them to stable releases, usually fixing cosmetic bugs, adding improved language files and doing other minor changes.

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!

Friday, 10 September 2010 03:10 CDT

pjdevries

Thank you for the comprehensive (as usaual) reply. I'll try to upgrade to the latest versions soon, give everything another try and get back to you with the results.

Monday, 13 September 2010 04:19 CDT

GVerheij

Hi Nicholas, thanks for the answer. I was very sure I upgraded the plugin as well as the component, but apparently I did not. After upgrading the plugin, it worked.

Thanks for your fast support, it is very much appreciated, Gerard

Monday, 13 September 2010 11:34 CDT

nicholas

You're welcome :)

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!

Thursday, 11 November 2010 00:37 CST

user7458

I just got caught with this one. In my situation the error occurs as I have post processing set up to pack the archives off to Amazon and had checked "delete archive after processing". I'm guessing that as remote control starts to download the backups, the amazon post processing finishes and deletes the archive, leaving this ungraceful error.

From a personal point of view, I'd love to have cron or lazy cron backing up to amazon as a standard usage, with remote control being used for ad-hoc backups to my laptop. So currently I have to unset the "delete archive after processing", but this isn't ideal for security to have to leave backups on the server.

It might be a good idea to insert a note about this scenario on the config tooltip for "delete archive after processing" and if it is possible, some changes to the post processing on the server to detect whether a remotecontrol download may still be in progress - but I'm not bitching as this is so damn useful as is, and it can be worked around easily.

Thursday, 11 November 2010 01:40 CST

nicholas

I think you are confusing some things, because the default behaviour is exactly as you imagine it should be :)

The default setting in post-processing options is to remove the backup archive from the server upon processing it. As soon as the backup archive is created and before the backup process ends we have the "Finalization" domain. One of the actions performed is post-processing the backup archives. In Akeeba Backup jargon this means uploading the backup archive parts to Amazon S3 (as this is the post-processing engine you chose). After each archive part is uploaded, it is automatically deleted from the server. When all of this is over, quota settings are checked and the backup process finishes.

To the eyes of Akeeba Remote Control, the post-processing (upload + delete) is part of the backup process. When it says that the backup is now complete, the uploading and deletion has already run. This is why the next process (downloading the archive) fails. It can't find the backup archive as it has been deleted from the server.

So, all you need to do is to tell Remote Control not to download the file. It's as simple as that. All the uploading and deletion of the backup archives is handled by the Akeeba Backup component transparently. I like simple and secure solutions, just like you ;)

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!

Thursday, 11 November 2010 02:22 CST

user7458

Thats good news on the logic. So, I just d/l from amazon in these one-off remotecontrol cases. OK, simple and secure.

Can I ask if the remotecontrol error be a little more graceful?

And kudos for the products guys!

Friday, 12 November 2010 02:36 CST

nicholas

The Remote Control software is going to be rewritten, so I guess, yes, we will make the error messages a little more graceful :)

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