Support

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:

Hi Nicholas,

Today I updated multiple sites with the new version of Akeeba Backup 4.0.1. About 5 sites online (2 different hosts: Siteground + PCextreme), and 4 sites on my localhost which is running XAMPP v 1.8.2 with php 5.4.22 and MySQL 5.5.34 on Windows 7 Ultimate.

Backing up on online sites where I updated AB works flawless. (Great new features BTW)
But alas on my Localhost all backups with AB 4.01 fails. (All J3.3.3 sites). @ about 75% I get the error: "Could not rename last JPA part to .JPA extension."

On all other sites on my local box, running J3.3.3 with A.B. 3.11.4 (not yet updated) all backups are running succesfully. Before with earlier versions I never had any trouble running AB on localhost.

So the problems are introduced with AB 4.0.1

For testing I took a backup of one of my online sites created with AB 4.0.1, installed this one with Kickstart on my localhost and tried to backup this site locally. But also here again the same error.

So I think there might be a problem with correct platform detection...?

Attached log-file of one of the failing backups and a screen-capture of the error.

In other tickets this error was associated with access rights of the file, but why then I don't get this error with AB 3.11.4?

Hope you can point me to a solution for this. And when it's a bug you can fix it.

Best regards,
Klipper

BTW I already tested with virusscanner, firewall and malwarescanner disabled but still same error.

Hi Davide,

Thanks for suggestion,
1.)
No, this problem is not created by a backup program, because I don't use one at all. (I create my backups for windows by creating images of my drives using external backup program from CD or USB-stick). And if this was the reason, AB 3.11.4 should be affected too!

2.)
All php-settings are conform the requirements of Joomla! 3.3.3. (I.E: when I restore a site with Kickstart running the installation script ALL settings are green)

3.)
php memory_limit = 256M, max_execution_time = 120 and 150 GB free hard-disk space and 1.5GB free system memory available (should be enough)

4.)
I did re-run the configuration-wizzard. No positive result. Played around with the settings as suggested by "Alice": No luck...

5.)
As I wrote before: Tried a backup with Eset Smartsecurity and Malwarebytes completely disabled. No luck. AB 3.11.4 run perfect when these programs are enabled.

6.)
Today I tested a Joomla! 2.5.24 site. First I updated the older AB to version 3.11.4. I created a backup and restorepoints successful.
Then I updated AB to version 4.0.1 and BANG same error again, so no backup :(
Then I updated the NL-language file for AB 4.0.1. A restore point was created and the upload was successful.
Then I tried to reinstall the latest ACLmanger (which was already installed and updated before) and BANG same error again.

So also restore point creation creates same error: "Could not rename last JPA part to .JPA extension."

So for now I don't have any idea how to go on... There has been changes in AB 4.0.1 compared to AB 3.11.4 what is triggering this error. I don't think this has something to do with my Windowsbox, or Xampp installation, because AB 3.11.4 is(was) running OK.

Attached two logfiles of backups created of the same J2.5.24 site: One with AB 3.11.4 and one with AB 4.0.1

Hope you find the issue...

Oh and I also investigated the php_error_log: I cleared the log started a backup, the error again in backupprocess, but no entry's in php_error_log after this backuptry...

Best Regards,
Klipper

Hi Davide,

1.) I tried backup with settings you suggested, but still same error.
2.) The author of the other ticket about this issue wrote that he changed jpa to zip.
So I tried that one too... And yes choosing zip created succesfully the backup.

So definitely there is something going wrong with the .jpa format.

Regards,
Klipper

Hi Nicholas and Davide,

I asked a friend of me to test the issue also on her local computer (Windows 7 Home Premium) with same Xampp version installed. (Actually I installed it on her computer). So environments are comparable.

She installed a fresh Joomla! 3.3.3.and installed only Akeeba Backup 3.11.4 + NL language file.
She runned the configurationwizzard. Then she started a backup which succeeded perfectly.

Next step: she updated AB via Live Update to AB 4.0.1. After finishing the post-installation messages, a new backup was started and yes, just as I expected: BANG our error: "Could not rename last JPA part to .JPA extension." Backup failed.

So in my opinion this proves that this is a Akeeba Backup issue introduced with AB 4.0.1

Hope you can fix this soon!

Best regards,
Klipper

Hi Davide and Nicolas,

I just installed latest dev release and created new backup. And YUPPY it is fixed!!!!

The backup finished perfectly!

Thanks for fixing. Hope you will release an update as soon as possible!

Have a nice weekend!

Best regards,
Klipper