Support

Salve,

una tabella con 1 milione di righe è effettivamente lunga da processare, tenga conto che Akeeba Backup utilizza impostazioni abbastanza conservative per evitare di raggiungere il timeout e, soprattutto, creare un archivio che possa essere ripristinato su quasi tutti i server.

Detto questo, potrebbe controllare il valore del campo "Number of rows per batch" all'interno della configurazione del profilo? Dovrebbe essere su 1000

Hello,

I'm sorry if previously I wrote in Italian, I saw your country from business information and I switched to Italian.

Using phpMyAdmin it will be faster, but you'll be more prone to errors and handling the resulting file will be more difficult. For example, Akeeba Backup will use abstract table names without the prefix (ie #__example instead of aaa_example) so you can change it during restoration. At the same time, we split the output in several different files so it will be easier to restore (and some hosting providers are blocking files too large).

On top of that, we're reading the database contents in batches, again to work around hosting limitations.

At the end of the day, it's just a tradeoff: you're exchanging some time vs a more reliable process. Since you're taking backups to be prepared if something wrong happens, it's way better to be safe than sorry and spend a little more time but be sure that the data inside it is not corrupted.