Akeeba Backup for Joomla!

#39019 Field 'id' doesn't have a default value SQL=INSERT INTO `soft_akeebabackup_backups`

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
PHP version
Akeeba Backup version
9.6.0 (2023-05-

Latest post by nicholas on Friday, 26 May 2023 01:50 CDT


Dear team

Error returned by system:-

Field 'id' doesn't have a default value SQL=INSERT INTO `soft_akeebabackup_backups` (`description`,`comment`,`backupstart`,`status`,`origin`,`type`,`profile_id`,`archivename`,`absolute_path`,`multipart`,`filesexist`,`tag`,`backupid`) VALUES ('Backup taken on Friday, 26 May 2023 13:31 AWST','','2023-05-26 05:31:03','run','backend','full','1','','/home/customer/www/','0','1','backend','id-20230526-053103-163901')

The site was created using a quickstart package, unsure if that could be the origin of the issue.

Trust a simple fix,


Akeeba Staff

The site was created using a quickstart package, unsure if that could be the origin of the issue.

It definitely sounds like it.

The id column is an auto–number column, i.e. it's a monotonically increasing database table row counter. You don't give them an explicit value, they get a value automatically when a row is created and it's always the value of the last row created on that table plus one.

I am afraid that your site may be fully broken.

Try creating a new category, article, and module. If you get an error your site is broken. Did you or your host restore a copy of it lately? Did you do any work on the database? This problem happens when someone exports and reimports a database without dumping the schema DDL, i.e. how the tables are created, which was such a common problem back in 2005 that I created the predecessor to our backup software — and the rest, as they say, is history.

If you didn't get an error then only Akeeba Backup is broken. The only simple fix is to lose all your backups and start over. Uninstall Akeeba Backup. Delete all tables with _akeebabackup_ in their name (if any are left behind). Install Akeeba Backup again.

The hard fix without losing data is to create a new table with the correct schema of the #__akeebabackup_backups table as we ship it, copy over the data (sans the id value) from the old table to the new, delete the old table, rename the new table to the old name. However, you asked me for a simple fix and this is not it.

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!