Backup corrupted by restore process (admittedly, with user error)
I had lost the ability to log in to my system with my usual desktop environment due to what I suspected to be user profile corruption, so I logged in with an alternate desktop environment tried restoring my home folder from a BIT backup. I did not initially realize that I needed to explicitly tell BIT to delete existing files in order to restore the old state of files already on the drive, so this initial restore did nothing and did not resolve my problem. I then tried restoring / instead of ~/, and ran into the same issue. It was after this second restore that I realized I needed to explicitly tell BIT to restore existing files. I then did another restore of / (of course, at this point I *should* have tried restoring ~/ again), and, in a flash of idiocy, did it from the running system instead of from a LiveCD.
I had set up BIT to exclude /media, so that the backup itself would not be recursively backed up. When I ran this final restore, BIT saw that /media was empty on the backup, and "deleted" everything on the running system that was under /media (meaning that it renamed everything from "*" to "*.backup.
So I've managed to render my OS unbootable and to make every backup on my backup drive not immediately usable (all the data is there, but the filenames have been changed).
Before I screw myself over worse, what's the best way to get my backup back to a consistent state so that I can perform a restore the right way from a Live CD?
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Jon Brase
- Solved:
- Last query:
- Last reply: