62
OS Backup - what should and what should not be backup'd?
(lemmy.kde.social)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Why? I have a hard time imagine a use case where restoring the OS itself would be appropriate.
I can imagine restoring data, obviously, and services running with their personalization ... but the OS is something generic that should be discarded at whim IMHO. You probably chance few basic configuration of some services and most likely that's stored in
/etc
but even then 99% is default.You can identify what you modified via shell history, e.g.
history | grep /etc
and potentially save them or you can also usefind /etc -type f -newerXY
with a date later than the OS installation and you should find what you modified. That's probably just a few files.If you do back up anything beyond
/home
(which should be on another partition or even disk than the OS anyway) you'll most likely save garbage like/dev
that might actually hinder your ability to restore.So... sure, image the OS if you actually have a good reason for it but unless you work on archiving and restoring legacy hardware for a museum then I doubt you do need that.