Support

 Hi Guys,

We have been using Akeeba to backup/restore sites on our Rackspace Cloud Server for a good number of years now, and have never had a problem until recently.

We are trying to backup our current site and restore it to a development directory for a template update, but are getting the 'not a jpa archive' error message when using Kickstart 5.0. Backup/restore has been successfully completed on this very same site on numerous occasions in the past using the exact same methodology as is producing the error now.

We are operating in a Linux environment and the backup is reporting a successful completion, but the JPA archive will not open via either Kickstart on the live server or locally using your very cool Akeeba eXtract Wizard.

File permissions on the target directory are set up correctly, with the web user having full RWX perms and ownership of all files in the target directory are correct.

The JPA archive is not being FTP'd. It is being copied from the source directory to the target directory via SSH, so a corruption caused from faulty FTP transfer settings is not the issue.

It appears to be something with the backup itself, although we cannot absolutely verify this ourselves.

Akeeba Backup Debug log attached and we have no problem giving you guys SU access to the site itself, just didn't want to do so in the public forums. :)

Any help you could lend would be greatly appreciated.

Kind regards,

Todd

Todd,

Your backup log did not post. Please try again. If you still can't get it to post, just throw it up on Dropbox or another file sharing site and give me the link.

Let's try something. In Configuration, in the Advanced Settings section, check the Archive integrity check box. That does a test extract at the end of the backup to make sure the archive is good. That will tell us if the archive is good before it is moved. It takes a little time, but I think it is worth it.

Thank you very much for your speedy response.

This issue has now been resolved, the reason for the error being PEBCAK (Problem Exists Between Chair And Keyboard). :-D

This site has become large enough that the backup was split into two parts. Since this is the first time this has happened, we simply neglected to copy the secondary .j01 file over to the target directory. Once that was done, backup/restore is working perfectly again.

Sorry about that!

Thanks again for your help, and you can mark this ticket as Closed now.

Todd

Todd,

Thank you for starting my week off with a chuckle. I'm glad you got the problem figured out.