Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.17
MySQL version: 5.5.27-cll
Host: westhost.com
Akeeba Backup version: 3.6.5
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:
I must premise this by saying that I suspect that this is not a strictly Akeeba Backup related issue, but I am hoping you may still be willing to help me..........
I have been using your product for a long time now with great pleasure and success! I recently upgraded my VPS server from MySQL 5.0 to 5.5 (while having a full backup and SQL dumps if things went wrong). After the upgrade all my sites worked just as before and everything seemed to have gone without a hitch. Akeeba Backups continued to be produced daily via CRON. I decided to test a site replication from a recent backup (after MySQL upgrade) only to find that the site content had been corrupted. After some digging I found the root of the problem.
My site contains many special characters, such as accents, etc from various different languages (German, French, Spanish, etc.).
In the database of the replicated site the content of any field that contains a special character breaks off at the first appearance of any such character, leaving my content crippled. I also did a simple SQL dump of the original working copy of the database. Here is an example of what I found:
example: category field name
original database: Rosé Wines
SQL dump: Rosé Wine
After replication with Akeeba Backup Pro: Ros
I googled the internet high and low and added the following lines to my.cnf
the complete file now reads:
this effectively changed my default collation and character set from Latin_Swedish to UTF8, but did not resolve my issue.
I don't know what to do anymore, because this issue renders any backup solution useless for me as it breaks the site content upon restore/recreation. I hope that you can help me figure this out. I just don't know who else to ask and you have been most helpful in the past.
Kind Regards, Bjorn
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.17
MySQL version: 5.5.27-cll
Host: westhost.com
Akeeba Backup version: 3.6.5
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:
I must premise this by saying that I suspect that this is not a strictly Akeeba Backup related issue, but I am hoping you may still be willing to help me..........
I have been using your product for a long time now with great pleasure and success! I recently upgraded my VPS server from MySQL 5.0 to 5.5 (while having a full backup and SQL dumps if things went wrong). After the upgrade all my sites worked just as before and everything seemed to have gone without a hitch. Akeeba Backups continued to be produced daily via CRON. I decided to test a site replication from a recent backup (after MySQL upgrade) only to find that the site content had been corrupted. After some digging I found the root of the problem.
My site contains many special characters, such as accents, etc from various different languages (German, French, Spanish, etc.).
In the database of the replicated site the content of any field that contains a special character breaks off at the first appearance of any such character, leaving my content crippled. I also did a simple SQL dump of the original working copy of the database. Here is an example of what I found:
example: category field name
original database: Rosé Wines
SQL dump: Rosé Wine
After replication with Akeeba Backup Pro: Ros
I googled the internet high and low and added the following lines to my.cnf
collation_server=utf8_unicode_ci
character_set_server=utf8
the complete file now reads:
[mysqld]
default-storage-engine=MyISAM
innodb_file_per_table=1
collation_server=utf8_unicode_ci
character_set_server=utf8
this effectively changed my default collation and character set from Latin_Swedish to UTF8, but did not resolve my issue.
I don't know what to do anymore, because this issue renders any backup solution useless for me as it breaks the site content upon restore/recreation. I hope that you can help me figure this out. I just don't know who else to ask and you have been most helpful in the past.
Kind Regards, Bjorn
