Support

Site Restoration

#15683 Restoring with jumpstart

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 Wednesday, 08 May 2013 18:00 CDT

Monday, 08 April 2013 15:55 CDT

wd5mush
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Some
Have I searched the tickets before posting? yes
Have I read the documentation before posting (which pages?)? some
Joomla! version: 2.5.9
PHP version: 5.3.23
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version which took the backup: (unknown)
Kickstart version used to extract the backup: (unknown)

Description of my issue:
Over the weekend my hosting company (UK2.net) moved my site to an upgraded server running php5.3.23. Following that I am unable to access my site (front end or back end), receiving just an error message.

Further investigation reveals my configuration.php file has been corrupted, there may be others as well, and I can only assume this is a result of the hosting company moving my site to a different server.

It looks as though I will need to use Jumpstart to reload the site. Although my last full backup is a few weeks old I have created a number of restore points since then.

Is there any way I can utilise these, or will I have to revert to the last backup and then manually update from there?

Sorry if the answers are in the documentation, but I can't find them and I am approaching panic mode!

Monday, 08 April 2013 16:30 CDT

nicholas
What is a "jumpstart"? Do you mean Kickstart? Kickstart can only be used to restore full site backups, not restore points. Restore points have a very limited scope: reverting a single component's state in case upgrading it somehow corrupts it. They are not intended to restore your site in a working state in a situation like the one you are describing. The best thing you can do, realistically, is restoring your full site backup even though it's over a month old.

Backups work great when you have backups. I'd recommend having automated backups running at least once every week (or more often, depending on how often your site changes), ideally stored in an off-site location like Dropbox, Amazon S3 etc. That's the only way you can rescue a site if it gets corrupt. Most likely you'll think that so many backups are an overkill. The one time you'll need them you'll realise why they are not an overkill... and end up taking more backups, more regularly ;)

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!

Wednesday, 08 May 2013 18:00 CDT

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!