Support

Site Restoration

#16085 Request: Drop all tables before restore

Posted in ‘Site restoration’
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

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Wednesday, 15 May 2013 11:28 CDT

tabletguy
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes (a little)
Have I read the documentation before posting (which pages?)? Yup
Joomla! version: (unknown) 2.5.9, etc.
PHP version: (unknown) 5.3 something
MySQL version: (unknown) 5.1 something
Host: (optional, but it helps us help you) CPanel
Akeeba Backup version which took the backup: (unknown)
Kickstart version used to extract the backup: (unknown)

Description of my issue:

I have one installation with an optional component called "CiviCRM". That component installs tables with a different prefix. It's not possible to get them to change their code, and I've never found something that can replace their functionality, so I have to use it.

The restore scripts used to have an option to drop all tables before restoring, but the current script seems to say that it will only drop tables for the given prefix.

I'm requesting an option to drop all tables. In most cases, I have access to phpMyAdmin and can do this myself, but that's not always the case, and it's certainly not an option if I (or another support tech) do the restore from within Joomla.

I thought about asking for another option, where I could put in a comma delimited list of extensions to drop. For me, at this time, just a single prefix and/or "all" options would suffice. I could see it being helpful if someone is running multiple Joomla sites from the same database, but I don't do that myself.

Thanks.

nicholas
Akeeba Staff
Manager
This option is way too dangerous. One small mistake can cause a huge disaster. If you don't always have access to phpMyAdmin I recommend using Adminer. I'm using it when doing support and I totally love 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!

tabletguy
I don't see how it's any more dangerous than the fact that you're going to completely wipe out a website with a backup. I'm not advocating that it be the default, and perhaps it's only in the documentation on how to do it. (That would make it "unavailable to 9-% of the users - haha).

Thanks for the link to Adminer. I'll see if I can get it installed on my host and do some testing.

nicholas
Akeeba Staff
Manager
Restoring the backup doesn't wipe out the site (entirely). Only what was backed up gets overwritten. Not in the backup? Not overwritten :)

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!