This is extremely tricky, but perfectly possible with Akeeba Backup. You simply have to exclude everything you don't want to backup. This means excluding non-core components, modules, plugins and template directories and their database tables, as well as the contents of all database tables except what you want to keep.
If I may ask, why are you willing to subject yourself to such great pain to end up with a site which you have to rebuild anyway? The premise of taking daily backups is that if you screw the brains out of your site one day, you can roll back to its backup. Even better, before trying something on the live site, do this:
- Take a backup
- Restore on a local server
- Test it locally and keep notes of what you did
- If it works, take another backup
- Perform the change on the live site based on your notes
- If it doesn't work, restore the backup, repeat from start
- If it works, delete the previous two backups and take a new backup
This method has served as perfectly for three years :)
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!