Backup and restore errors
Permalink
Hi Everyone,
I seem to be experiencing major issues when it comes to backing up and restoring C5. I recently updated to 5.6.2.1, and (while it wasn't perfect before) using the backup and restore features seem to be bordering on non-functional at this stage.
I prefer to make encrypted backups, but often the backup process would fail and give out HTTP 500 errors. I tried everything from increasing the PHP max_execution_time, to changing permissions for the backup files, to turning off tracking and truncating the pagestatistics table (which from viewing the forums, seems to cause an epic amount of grief to anyone who uses it).
When I finally got the backups to happen (after massively reducing the database size) it then transpired restoring them didn't work either and also gave out HTTP 500 errors! Even after abandoning encrypted backups and using the plain text files instead, I get the same result.
The PHP error log points to a PHP Fatal error: Call to a member function submit() on a non-object in [C5 webroot]/updates/concrete5.6.2.1_updater/concrete/single_pages/dashboard/system/backup_restore/backup.php on line 66. I looked at line 66, and it just seems to be the submit on modal asking you to confirm that you actually want to do a restore.
I don't want to (nor do I see the point of) doing backups and restorations via PHPMyAdmin when this is supposed to be built in to the system - and to be honest, if I wanted to do it that way, I wouldn't use that functionality in the first place.
Is it just me being dense or am I just missing something, because I've spent hours trying to sort this out and it's P*****g me off something fierce. Any help or ideas on what could be going on would be greatly appreciated.
Thanks
I seem to be experiencing major issues when it comes to backing up and restoring C5. I recently updated to 5.6.2.1, and (while it wasn't perfect before) using the backup and restore features seem to be bordering on non-functional at this stage.
I prefer to make encrypted backups, but often the backup process would fail and give out HTTP 500 errors. I tried everything from increasing the PHP max_execution_time, to changing permissions for the backup files, to turning off tracking and truncating the pagestatistics table (which from viewing the forums, seems to cause an epic amount of grief to anyone who uses it).
When I finally got the backups to happen (after massively reducing the database size) it then transpired restoring them didn't work either and also gave out HTTP 500 errors! Even after abandoning encrypted backups and using the plain text files instead, I get the same result.
The PHP error log points to a PHP Fatal error: Call to a member function submit() on a non-object in [C5 webroot]/updates/concrete5.6.2.1_updater/concrete/single_pages/dashboard/system/backup_restore/backup.php on line 66. I looked at line 66, and it just seems to be the submit on modal asking you to confirm that you actually want to do a restore.
I don't want to (nor do I see the point of) doing backups and restorations via PHPMyAdmin when this is supposed to be built in to the system - and to be honest, if I wanted to do it that way, I wouldn't use that functionality in the first place.
Is it just me being dense or am I just missing something, because I've spent hours trying to sort this out and it's P*****g me off something fierce. Any help or ideas on what could be going on would be greatly appreciated.
Thanks
So JohntheFish does the Voodoo actually work? Like for example I did a complete wipe of a website and made backups of the database and all files. When I did a fresh install I could not get the backup to take at all nor could I get it to use the database backup file that came from C5. Either directly into the database, (it gave me an error) and it would not even see the backup file that was in there. So I had to redo each and everypage from scratch. Lucky for me there is cached pages of it in google search so I just view source and copied the code. Saved me hours of time.
Zero I hear your frustration brother. One of my big major issues now, is that while using Concrete 5 and doing multiple updates via the back end, something almost always breaks. Not all the time but most times and then its hours of searching for fixes. Do not get me wrong when C5 works its fantastic but when it breaks its a nightmare.
I am now having an issue with one of my sites that I updated from 5.5.2 or around there to the newest and while editing the site and saving it the layout function works and looks great. When I look at it outside of the editing function it was completely broken and all over the place. Needless to say I figured out a work around for it but now I am thinking I will have to do the exact same thing all over again.
I am gonna watch this post cause if I can learn how to make what your trying to do work, I will simply do a wipe and then do a fresh reinstall. To be honest I can not find out how to get the site to actually see the backup database file from before. I can create a new one and it will see it but not the old one.
Zero I hear your frustration brother. One of my big major issues now, is that while using Concrete 5 and doing multiple updates via the back end, something almost always breaks. Not all the time but most times and then its hours of searching for fixes. Do not get me wrong when C5 works its fantastic but when it breaks its a nightmare.
I am now having an issue with one of my sites that I updated from 5.5.2 or around there to the newest and while editing the site and saving it the layout function works and looks great. When I look at it outside of the editing function it was completely broken and all over the place. Needless to say I figured out a work around for it but now I am thinking I will have to do the exact same thing all over again.
I am gonna watch this post cause if I can learn how to make what your trying to do work, I will simply do a wipe and then do a fresh reinstall. To be honest I can not find out how to get the site to actually see the backup database file from before. I can create a new one and it will see it but not the old one.
Yes, Backup Voodoo works. Please have a look at the reviews.
http://www.concrete5.org/marketplace/addons/backup-voodoo/reviews...
As for managing the upgrade process without risk of breaking a site, see:
http://www.concrete5.org/documentation/how-tos/developers/organise-...
http://www.concrete5.org/marketplace/addons/backup-voodoo/reviews...
As for managing the upgrade process without risk of breaking a site, see:
http://www.concrete5.org/documentation/how-tos/developers/organise-...
Thanks John and one of the reviews speaks directly to what I am looking to do very soon here with another website of mine so I very much appreciate your feedback.
I also appreciated the idea and thought behind doing sub domains for testing and roll out. Honestly I do not know why I never thought of that as well lol. Thanks for info I very much appreciate it!
I also appreciated the idea and thought behind doing sub domains for testing and roll out. Honestly I do not know why I never thought of that as well lol. Thanks for info I very much appreciate it!
Ok I went ahead and bought a copy of it to help support your work. I will do some of the methods you suggested and see how it all goes. If all goes well I will be making this a priority add on for any websites that I build. Have a great day and thanks for your help. Ill let you know how it goes.
I actually see it that it's not really the job of a CMS to handle the backups and restores (even though features have been put in the Dashboard), as they are really operations that should be performed at the hosting level.
Systems like cPanel have been designed to handle the export of large databases and don't have issues of memory or timeouts.
With most sites it takes me seconds to log into cPanel and click two links to get a full database backup and a full file backup. I really don't use concrete5's backup tools as I see it as too risky, but also it only does the database, not all the files - so if I'm going to log into something I feel I might as well log into cPanel and grab everything.
A restore in particular is something I'd never want to do via the dashboard and we are talking about performing possibly thousands of database inserts and operations through a channel that isn't _really_ designed or configured for that.
I agree that you'd think that if a feature was in the dashboard it would 'just work', but I'm suggesting here that you might be better of pretending it's not there!
Systems like cPanel have been designed to handle the export of large databases and don't have issues of memory or timeouts.
With most sites it takes me seconds to log into cPanel and click two links to get a full database backup and a full file backup. I really don't use concrete5's backup tools as I see it as too risky, but also it only does the database, not all the files - so if I'm going to log into something I feel I might as well log into cPanel and grab everything.
A restore in particular is something I'd never want to do via the dashboard and we are talking about performing possibly thousands of database inserts and operations through a channel that isn't _really_ designed or configured for that.
I agree that you'd think that if a feature was in the dashboard it would 'just work', but I'm suggesting here that you might be better of pretending it's not there!
http://www.concrete5.org/documentation/how-tos/developers/backup-a-...
Restoring a database from the dashboard may use more resources than making the backup, so even if a backup just about fist into server resource allocation, restore may not!
A backup does not end with the database, you also need to backup files. See:
http://www.concrete5.org/marketplace/addons/backup-voodoo/...
(I regard what little hair I have as worth a few $)