Backup CB Files & It's Database Question Please?

Hi,

I'm having issues with my site's Joomla Menu Manager and some Joomla theme elements, so it seems I'm going to have to use a backup to restore to a previous fully working state.

However, the backups I have aren't quite the right date and therefore I'm seeking the correct dated one from my web host.

My question is I've made a lot of great changes to my overall CB installation in the past week or two and really would find it soul destroying to lose these upon the restore of my site and database from the above mentioned backup.

I can't find anything via CB's Forum Search and I'm not currently aware of any but is there any way at all that I can find out exactly what directories, files and database files that would be / could be / should be backed up and then restored on their own.

This is once I've restored the main web hosts version of my sites overall backup of files and database and hopefully that way I get what I need back working from my main site and get to keep all the changes I've made within CB in the past week or two, especially I've added many new fields in field manager and so forth.

I look forward to your thoughts on the above and keep my fingers crossed.

Regards,
Rob

Your backup solution is entirely in your hosts hands. We can't help with this. CB has no built in backup features. You may want to look into Akeeba Backup for future usage as it's able to create "restore points" to easily restore specific changes made, etc..

Best I can suggest is reviewing your install with FTP and see what the modify date is for your various folders/files to see what has changed, but that won't help with database changes. If you're confident CB isn't broken and you don't need to restore CB then just don't restore any of the _comprofiler database tables.

Hi Kyle,

Thanks for the reply. I have Akeeba Backup installed and a short while ago paid for the Professional version but have never got around to implementing the fail safe of CRON / Scheduled backup and now wish I had but I kind of worry about trying things in case it breaks the web host server and end up with a bollocking :S

As for normal Akeeba, I'm on a lot of very strong medication for various illnesses and believe it or not they give me a chronic memory, so often I forget to hit Akeeba Backup in my Joomla backend before starting even the smallest tweak to settings, modules, plugins etc.

I'm 100% sure CB isn't broken in anyway, so I will try as you mention by not restoring any of the _comprofiler database tables.

However, if my web-host back up contains ALL my sites database in one .sql text file, how can I make it that it only restores everything BUT the _comprofiler tables?

Thanks once again for your input as always Kyle, it's much appreciated.

Regards,
Rob

krileon wrote: Your backup solution is entirely in your hosts hands. We can't help with this. CB has no built in backup features. You may want to look into Akeeba Backup for future usage as it's able to create "restore points" to easily restore specific changes made, etc..

Best I can suggest is reviewing your install with FTP and see what the modify date is for your various folders/files to see what has changed, but that won't help with database changes. If you're confident CB isn't broken and you don't need to restore CB then just don't restore any of the _comprofiler database tables.

However, if my web-host back up contains ALL my sites database in one .sql text file, how can I make it that it only restores everything BUT the _comprofiler tables?

You'd need to edit the sql file and remove the changes to _comprofiler. I also suggest making a new backup before you restore your backup just encase someone goes wrong with restoring the old backup.

Kyle,

Thanks as always for the reply and your thoughts / knowledge, it's much appreciated.

Regards,
Rob

krileon wrote:

However, if my web-host back up contains ALL my sites database in one .sql text file, how can I make it that it only restores everything BUT the _comprofiler tables?

You'd need to edit the sql file and remove the changes to _comprofiler. I also suggest making a new backup before you restore your backup just encase someone goes wrong with restoring the old backup.