Support

Akeeba Backup for Joomla!

#20709 Magento backup (extends ticket #20179)

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 on Monday, 15 September 2014 01:20 CDT

Tuesday, 12 August 2014 03:34 CDT

trendup
Extends this ticket: #20179: Add specific wrapper to mysql backup dump

Using "No dependency tracking" option making a backup, I get a full Magento backup and I can restore it with ANGIE, but I still have problems. I don’t get errors on restore, but I get a 404 error accessing to Magento backend, so, after restoring I have to run the attached SQL script as described here.

Other related infos are here.

Do you think there is a solution using Akeeba Backup without having to run the SQL command?

Tuesday, 12 August 2014 04:49 CDT

tampe125
Salve Matteo,

grazie per la segnalazione.
Al momento Nicholas è fuori ufficio e tornerà fra qualche giorno, non appena sarà di nuovo operativo vedremo di affrontare il problema.

Grazie ancora.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 12 August 2014 10:34 CDT

tampe125
Controllando il Changelog, questo problema è stato risolto nella versione 3.11.1 di Akeeba Backup.
Il backup che sta cercando di ripristinare con quale versione è stato creato?
Può creare un backup con l'ultima versione di AB e ripristinarlo? Non dovrebbe più avere il problema da lei riportato.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 12 August 2014 11:15 CDT

trendup
Grazie per l’aggiornamento. Sto utilizzando la versione 3.11.3 incorporando l’ANGIE for Miscellaneous PHP Application da cui effettuo il ripristino. Il problema però si presenta ancora.

Thursday, 14 August 2014 01:58 CDT

tampe125
Giusto per sicurezza, durante il restore, nella pagina relativa al database, la voce No auto value on zero era spuntata?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 14 August 2014 02:00 CDT

trendup
Sì, era spuntata e se non sbaglio è spuntata di default.

Thursday, 14 August 2014 12:03 CDT

nicholas
When restoring you MUST check the "No auto value on zero" checkbox in the Database Restoration page.

Moreover, please note that ANGIE will restore Magento but will NOT reconfigure it! If you are restoring to a different server / domain / subdomain / subdirectory and/or a different database and/or a different database prefix you MUST reconfigure Magento manually.

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!

Thursday, 14 August 2014 18:00 CDT

trendup
"No auto value on zero" was checked.
If you mean that the attached sql.png file is "reconfigure Magento manually" (because I running this commands Magento works), what about adding the option to configure the ANGIE restore script with custom SQL commands? It could save time for repetitive tasks…

Friday, 15 August 2014 17:48 CDT

nicholas
The SQL commands you used are only necessary when the "No auto value on zero" is not checked or not supported on your server. This option only works on MySQL servers and as far as I can understand from MySQL's documentation it will only work on MySQL 5.5 or later. If you are restoring to a non-MySQL database or an old version of MySQL you will have to run your custom SQL commands.

Two very important things to note.

1. Magento (and Drupal) do it wrong. It's not my assessment, it's according to the MySQL documentation. Magento and Drupal use the numerical value 0 on an auto_increment column. This is discouraged by the MySQL documentation because it will cause problems when exporting and reimporting that database contents. We can try to coerce MySQL into restoring 0 values in auto_increment columns but it's up to the database server to decide if it wants to honour this instructions.

2. Magento and Drupal are not officially supported for use with Akeeba Backup and Akeeba Solo. What you are asking is having an official support. This won't happen any time soon since an officially supported script must also be reconfigured by the specialised ANGIE installer. Due to the way Magento and Drupal are written this is impossible to do automatically when you are restoring your site(s) on a different server, domain, subdomain or subdirectory.

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!

Monday, 15 September 2014 01:20 CDT

System Task
system
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.
Edited by on 2014-09-15 01:20 CDT

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!