Development Blog

Good to hear that but its also bad.

I have though you are releasing the Leadwerks3D Homepage + option to preorder the Upgrade

It seems the backup still failed a bit, since not all new posts were restored.

I wonder why you need to even touch or restore the database, as the PHP code should be completely seperate from the SQLite3 database.

Also a professional restore should be never done per whole database, but rather write a PHP script which checks for individual records in the actual and backup and only fixes the differences.

It probably wasn't necessary to use the backup, since the problem was caused by the automatic CPanel upgrade, but that was just the first thing they tried. The backup is from yesterday morning around 2 A.M.

All's well that ends well ... I can cope with losing a few hours worth of posts. These things happen from time to time.

Why didn't they try on a test server first? You should never do anything in production, before you know what the problem is.

Good to Hear Josh, that's pretty scary!

This actually makes me feel safer now because it proves our backup procedures work, which wasn't the case with our old host.

Except when the guys restore a backup over a newer version which has not been backed up yet

Before I would restore a backup, I would take a backup of the current version first.

That's a good idea.

I have to agree with Metatron - Whilst it was a good news story in the end, thats a pretty bad way of troubleshooting and recovering from the issue.

I would be worried as to why the backup wasn't made before the cPanel upgrade - Everyone knows you do a backup before any update or upgrade.

Shocked to see the PHP Config screen, as I was here with the recent data loss after the migration to the new site. I'm glad everything is resolved! Yaay for backups!