Talking about backups will loosen an avalanche of advice, do’s, don’ts, etc. So be prepared.
And, while I did not read that old thread< I do not think it is out of date, because making backups is the same subject since the start of electronic mass-storage.
To begin with, you should think about what “disasters” are threatening you. Then you should develop a backup policy that takes care of those threats. Already with the first step here you will notice that different advice depends on what threads are taken for serious. Let us take your own post, where in the end you talk about a list of installed packages (well you call them by the fashion word app
). Surprise for me. but valid. Others will already take a user that deletes/ a file by incident as something the system manager should take precautions against. So there are different approaches, different wishes and thus different solutions.
BTW you whish to have a list of installed packages is an easy one
rpm -qa
will give all RPMs installed (not only by using YaST/zypper, but all)
Look into
man rpm
on how to put more information in that list. I use e.g.
rpm -qa --qf '%{NAME}:%{VERSION}:%{RELEASE}:%{INSTALLTID}:%{SUMMARY}
' | sort
Note that software installed not by RPM (e.g. a builds out of a tarball) is not included of course, you should take note yourself about them.
Some random remarks. When designing your backup policy, you should think about details like: where do I store the backups? On the same system :(, in the same building. Out of the house/office :). And when out of the house, how quick am I able to restore a lost file?
And that brings us to the next, very important aspect. There should be a disaster recovery plan. And that should be tested.
Many go for what they call “cloning”. Probably because they like the word. (BTW, when “cloning” means, making a byte for byte copy of something, that is not always done by these gaudy tools.) And when cloning file systems, or even whole mass-storage devices, that will include copying of UUIDs, which from that moment on are not only not so Unique, but those not Uniques will even be dangerous near to each other. And of course, retrieving a lost user file from such a “clone” may not be something done quickly.
Just a few remarks about an endless subject. And no, they are not specific about LEAP 15.4, because they are at least Unix/Linux general, when not valid for all operating systems.