Akeeba Backup for Joomla!

Friday, 23 March 2012 09:30 CDT

user60822

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
Have I read the documentation before posting (which pages?)? yes
Joomla! version: (2.5.3)
PHP version: (5.3.1 server, 5.3.1 localhost)
MySQL version: (unknown)
Host: (midPhase server, xampp 1.7.3 localhost)
Akeeba Backup version: (Akeeba 3.4.3, kickstart 3.4.1)

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

log file
www.jokabsafetyna.com/_temp/akeeba.backend.log

Description of my issue:

Goal is to duplicate live site on localhost to develop new features and content locally before placing them live. Have done this many times before with no difficulty.

Backing up my live site from a sub-directory seems to be fine. Restoring to my localhost also seems to be fine.

However, going into the localhost site reveals an old state of the website. A variety of new features, template setting changes, content, and users from live site aren't in the localhost site.

I don't understand how this could happen.

Thanks

Friday, 23 March 2012 10:30 CDT

nicholas

The only explanation is that you are either restoring an old backup of your site, or you are restoring it, let's say, to directory B, you have the old copy in directory A and you end up accessing directory A. I'm pretty sure there is a rational explanation like the one I gave, as I'm pretty darn sure that Akeeba Backup won't travel back in time, backup an old version of your site and allow you to download that backup :)

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!

Friday, 23 March 2012 10:47 CDT

user60822

The internet server and localhost sites use different database names, usernames, and table prefix. In looking through the log file i noticed Akeeba backup added two versions of every table to the database. One for each of the two table prefixes.

So on my localhost site i went to Global Configuration / Server / Database Tables Prefix and changed it to that of my internet server. I DID NOT change any of the other database settings.

Went back into the localhost website and everything works and looks as expected.

I still don't understand how this happened.

Any recommendations on how to prevent it from happening again and how to clean up the database would be appreciated.

Thanks

Edit - I'm reading up on phpMyAdmin so i can remove all the wrong table prefix entries from it.

Edited by user60822 on 2012-03-23 10:50 CDT

Friday, 23 March 2012 10:57 CDT

nicholas

Akeeba Backup always backs up all tables in the database. That's why the Database Tables Exclusion feature is for, as per the documentation. The only way you can have a mix up is the following:

Let's say that your live site's prefix is abc_ and your local site's prefix is xyz_. At some point, your live site uses abc_ and keeps it up to date, but has the xyz_ tables left over there. When you restore a backup which has BOTH sets of tables locally and set the database prefix to xyz_ here's what happens. All of the abc_ tables are restored with the xyz_ prefix. Then, the already backed up xyz_ tables OVERWRITE the existing ones. Therefore, the old data overwrites the new one.

Be careful of what you back up and what you restore. Akeeba Backup will only do what you tell it to do, not what you intended it to do.

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