Support

Akeeba Backup for Joomla!

#38087 Backup and Restore DB Tables for Migration purposes

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
4.
PHP version
8
Akeeba Backup version
4.2.5

Latest post by dunwin on Monday, 28 November 2022 08:17 CST

dunwin

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 10MiB, please upload it on your server and post a link to it.

We are currently migrating our site to Joomla 4. For various reasons we creating a new Joomla Site for Joomla 4.

This is all working fine. However there are a couple of things we want to do.

1) We would like to back up a just one Joomla component (our membership system) and only the DB Tables and move them to the new site. We could do this with PHYAdmin, but I a not confident using it. I know in Akeeba Back you can backup Site Tables only and even select certain tables via Exclude option.

What I can't see is how to import these tables into the new site and change the DB Prefix to the new site's DB prefix.

Could anybody help me with this?

Thanks

 David Unwin - London UK

tampe125
Akeeba Staff

Hello,

technically what you're asking is doable, but it really depends on how the component has been created. First of all, you should check if it has any link with the #__assets table of your site. Since the internal IDs will be different, you can not simply "copy and paste" the content, otherwise the you will have corrupted data. After this check, you can try to move the data from one site to another.

My suggestion would be to install the component from scratch in the Joomla 4 website, so Joomla will be notified of the new component and it will include it inside the environment (automatic updates, administrator menu etc etc), then you can start thinking about moving the data.

The quickest way would be to use the same database prefix, export the tables for that component and import them into the new website using PhpMyAdmin. Of course you can use Akeeba Backup, but you should create a new backup profile with the type "All site databases", exclude all the tables expect the ones you're interested into, upload the archive to the new site and start the restoration. Since it's a database type, it means that the only step in the restoration is the database one.
Honestly I think it will be quicker to do everything with PhpMyAdmin.

Then... you have to experiment and check if anything breaks. I can only give you some general guidance, but the best thing to do is to get in touch with the developers and ask them if what you're doing is actually possible.

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!

dunwin

Hi Davide,

Thank you for that explanation and advice. I will I think do as you suggest and contact the developer for further advice.

Kind regards

David

 David Unwin - London UK

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!