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:

For the last 3+ years akeeba backup has backed up and restires (to a test site) my site. On trying to update to Joomla 3.6.5. Backup stalls at initialisation. Akeeba backup tells me that "Your database table name prefix contains one or more uppercase letters" as it has since inception... what has changed. I have read "Q106 - Uppercase letters in table name prefix" and it has put the fear of god into me. There are six steps in the fix and the imntro says that on Linux skip the first six steps... does that mean there is no solution!!!!

It says "but restoring it on Linux will be impossible or cause errors" on 13 June this year I did such a restore as I have done many tiems before.. what has changed?

Nicolas

Thnaks for your prompt response -- I seem to have two probleme here.

1) Uppercase prefixes -- After panacking at reading that article I restored the site (from a Cron akeeba backup as I could not do a manual backup -- see later) and during the restore I changed the prefix to lower case and the restore worked just fine. Next is to try an in place restore to see if that works.. so my panick over that is over. I have a clone copy of the site with lower case prefix. Which comes on to my next issue.

2) Akeeba backup hangs at initialisation (Log attached) Alice says all is fine! I am at PHP7.0.13 and I updated Akeeba Backup to 5.2.5. I noticed this hang as I tried too update Joomla to 3.6.5. I guess I can disable the automatic akeeba backup before joomla core update or update joomla core manually. But I am very concerned that I cant take a backup up of the repaired cloned site.

Well I be ...I was reporting on the situation at 19:37 last night when the backup hung. Having written the previous reply to you I tried again and this time it worked... Ther ehas been no change whatsoever in those 12 hours.

Thank you ,and sorry for my ignorance.. will do my best to remember next time and not be one of the few dozy dozen!

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.