Support

Akeeba Backup for Joomla!

#8557 Akeeba converts # to jos in error

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 Monday, 09 August 2010 11:38 CDT

user12010
I am using com_akeeba-3.0.1-pro.zip

A problem solved...

I used Akeeba to back up my system and restore it to a live web environment from a local test situation. The table jos_comprofiler_fields has a large number of entries that have been converted to jos_ when they should be #_. The CB database checker gives errors to the effect that this is not working.

Error message is:

________________
Table akb_comprofiler_fields Column table DEFAULT is 'jos_comprofiler' instead of akb_comprofiler
Table akb_comprofiler_fields Rows fieldid = 41 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 26 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 25 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 27 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 28 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 29 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 42 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 45 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 46 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 47 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 48 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 49 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 50 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 51 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 52 : Field table = jos_users instead of 'akb_users'
Table akb_comprofiler_fields Rows fieldid = 24 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 23 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 22 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 21 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 20 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 19 : Field table = jos_comprofiler instead of 'akb_comprofiler'
Table akb_comprofiler_fields Rows fieldid = 18 : Field table = jos_comprofiler instead of 'akb_comprofiler'

_____________

The solution is to take a copy of the working local system and replace the table with the correct one by deleting the old one using PHPmyAdmin...

Checking everything seems to give a positive result with all of the errors having been fixed.

The reason that I created a local test system was because of this precise problem and I wanted to make a step by step clean install with no errors. The errors came back and luckily I have now tracked them down to Akeeba not functioning correctly.

I think this is a clear example of a bug in your system. My I suggest you urgently fix it for you users that have CB installations. Given that I fixed it for you already, it would be very nice for you to send me some freebies e.g., free software or support contract for free??? ;-)

Contact me for more data...

Andi

dlb
You are correct, this is a know bug in the restore routine. It is fixed in the Developer's Release.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user12010
If I install svn202 on top of my existing Akeeba environment will this be reliable? Are there any issues that you can think of that should prevent me from doing this?

user12010
Thanks for the information about the developer's release. Unfortunately....

IT DOESN'T WORK

The release svn202 does NOT fix the problem of errors in the jos # table creation errors. Luckily I executed the process very carefully and still have all of the original files. But the current state of play is that Akeeba does not create a realiable backup for a Joomla system that has a community builder database within it!!!

I look forward to getting notification of a working version sometime soon. If you would like me to test the configuration that I will try to find the time do help.

KR

user12010
SHORT TERM FIX:

The system wants to have the default value in the structure of the database to be:

akb_comprofiler for the table record...

Akeeba sets this to be jos_comprofiler

The fix is to change the default value using phpMyAdmin and re-run the database tests. This appears to have fixed the problem...

KR

Andi

dlb
Andi,

The backup process is, and always has been, fine with Community Builder installed. The problem you describe is in the restore procedure where the table prefixes are restored. It is my understanding that it is fixed in SVN202, according to the change log it was fixed in 169.

I flagged the thread for Nicholas yesterday, he can comment on the issue more definitively.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user12010
Hi Dale

I don't understand what value there is in a backup system that does not correctly restore.

Does what you say mean that the part that is fixed is the kickstart.php script? Can the backups that I made earlier be used with the SVN202 kickstart.php? If not then I really don't understand what point you make in your post.

I look forward to hearing from Nicolas because it definitely does not work in precisely the manner I describe in earlier posts.

Ciao

Andi

nicholas
Akeeba Staff
Manager
SVN202 (actually, all versions since 169 as Dale pointed) is known to work. All you need to do is run the "repair db" task in Community Builder after restoration, due to a conflict between Akeeba Backup and CB. This is a losless procedure and we've checked it with the CB folks. If we make Akeeba Backup fully compatible with CB we will have to break the restoration algorithm with MySQL VIEWs, stored procedures, stored functions and triggers, which is a more serious regression. As a result, we consider the backup to be accurate and fully restorable, as the extra procedure involved does no longer cause loss of data.

This last bit of information is present in the documentation on our SVN repository since 3 weeks, but it's not put on-line on this site yet. There's a reason to do that; the documentation in the SVN refers to features not available in official builds. You can check out the public SVN on Google Code if you'd like so.

If you have an old backup, all you have to do is to copy over the installation directory of a newer backup on top of it (sans the sql directory). Kickstart only extracts the archive, it does not perform the site restoration (incl. the database restoration). This is performed by the Akeeba Backup Installer script, automatically added to your archive at backup time.

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!

user12010
Hi Nick

Thanks for your clarification, I can accept that this is a solution that matches the needs of a production system and does not compromise technical integrity. I didn't try to use the fix database method because when I did it on a previous restoration the changes killed the system. So in future rather than manually edit the config I'll click the fix button...

Beyond the recent issues, I would like to say that your product is excellent and the results very reliable... Highly recommended.

Best

Andi

nicholas
Akeeba Staff
Manager
Indeed, on backups produced by the 3.0 release using the database fix would result in data loss. The SVN release solved that. It's just the documentation not on-line, yet :)

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!