Akeeba Backup for Joomla!

Tuesday, 14 February 2017 17:22 CST

joomleb

Hi guys,

- I installed a standard joomla site on my server with all the extensions configured as I need.
- This is the one I "clone" when I need to install a new site project.
- Logically, each time I change somenthing I manually do a Backup with Akeeba Backup
- Logically on my "Manage Backups" I have the list of all the Backups I done on "Clone" site in its life.
- To "clone" I simply take the last Akeeba Backup and install it thorugh Kickstart.

Now, when I install the "cloned" backup as a new site, I don't want have all the "Manage Backups" history, but I want a blank virgin "Manage History".
So, as I put online the new site I want make a Backup and will be the first backup in the "Manage Backups"...

Please, How to have a blank "Manage History" on the new site ?
(And don't install the backup and then erase all the old "clone" site backups. The first backup will have ID 1 and not the last+1 of the "clone" site)

Many Thanks for help

Wednesday, 15 February 2017 03:10 CST

nicholas

There is no user accessible control for this operation because it's massively dangerous. If you really DO want to do this you can do so through the database management you are using, e.g. phpMyAdmin. Assuming that your table name prefix is foo_ you need to run TRUNCATE TABLE foo_ak_stats to delete all backup records AND reset the internal MySQL counter.

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!

Wednesday, 15 February 2017 23:44 CST

joomleb

Hi Nicholas,

many thanks for explanation. So, the only table I have to take care is ..._ak_stats, right ?

And, please, to reset the internal MySQL counter in phpMyAdmin I have to right click the table in the tree or in the list view, click "Alter table ..." and edit the auto increment value. As far as I know it's always safe to set it to 0 (also for tables with rows in it because MySQL will correct the value as needed), Am I right ?

Thanks for help and support :)

Thursday, 16 February 2017 02:26 CST

nicholas

many thanks for explanation. So, the only table I have to take care is ..._ak_stats, right ?

Correct. This is where all the backup records are stored.

And, please, to reset the internal MySQL counter in phpMyAdmin I have to right click the table in the tree or in the list view, click "Alter table ..." and edit the auto increment value.

That's not necessary. The command I gave you does two things: delete all records and reset the internal counter.

There's also another way to reset both the backup profiles and the backup records: exclude all the _ak_ tables from the backup. After restoration login to the backend of the site, ignore the big, fat error page and append ?option=com_akeeba to the URL on your browser. After hitting that URL a couple of times you should see Akeeba Backup's page and the tables should be created. Please note that this an untested theory, your mileage may vary, things may blow up etc ;)

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, 20 February 2017 16:20 CST

joomleb

Hi Nicholas,
really many thanks for support, I run with success the TRUNCATE TABLE foo_ak_stats to delete all backup records AND reset the internal MySQL counter

Tuesday, 21 February 2017 01:20 CST

nicholas

I'm glad I could help you :)

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, 23 March 2017 18:17 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.

Support