Support

Site Restoration

#31896 Database only partially restored

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 on Saturday, 23 November 2019 17:17 CST

cletocq
When restoring, the restoration script only creates 108 of the 130 tables that were archived. I checked the archive log and all the tables were included in the archive.

I removed the STOP ON CREATE and STOP ON ERROR check boxes and increased the throttle time to 1000. Same error.
I created a different MySQL database and tried restoring again. Same error
I checked my database quota in CPanel, I'm at 0 of 8.09GB (0%) my disk usage is 1.91 of 10GB (19%)

Any suggestions?

Thanks

Chris

nicholas
Akeeba Staff
Manager
What is the exact error message you receive during restoration?

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!

cletocq
No error message on database restoration, however the next screen generates a red error message with a SQL string that owfru_users is not found. Then when I check with PMA I see that the tables are missing.

I worked around this by restoring the database directly and I cannot now reproduce the error. It is possible that this was caused by the site defaulting to PHP 5.6.4 as opposed to 7.3.1 because of my overwriting htaccess. I have since solved this error, I am now using Kickstart 6.0.2 and everything works

I would close this ticket

Thanks

Chris

nicholas
Akeeba Staff
Manager
It sounds like there is a MySQL error preventing a few tables from being created. I infer from your second post that one of the tables is Joomla's users table. I know for a fact that this table doesn't have anything weird which could cause a MySQL error. So I am really wondering why this happened.

Of course you don't see any errors now :) You unchecked the Stop on CREATE and Stop on Error checkboxes, therefore telling ANGIE to suppress all error reporting. Let me remind you that ANGIE is the script that is actually restoring your database. ANGIE is part of the backup archive. Kickstart has nothing to do with restoring the database. Kickstart only extract the backup archive (writes the files). This information is presented to you every time you run Kickstart, please take a couple of minutes to read it next time you use Kickstart. It's not idle pedantry or passive aggressiveness, I swear! Understanding there are two different scripts running during the full restoration process is important to realizing that, for example, using a different version of Kickstart will not affect how your database is restored. It sets your expectations and reduces your confusion over what is going on.

If this happens to you again run the restoration checking both Stop on CREATE and Stop on Error checkboxes. Do not increase the time; doing so will most likely cause the restoration to fail (if the request takes too long Apache or PHP will kill it; that's why we chop down the restoration in small bits). You will get a more descriptive MySQL error message about what is going on. In this case I'd also like to know which version of Akeeba Backup was used to take the 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!

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 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!