Just returned to fedora after a long time of arch. Finally feel the need of a backup so I won’t lose all that I have customized and set through laborious work.
I am not sure what to use, but I roughly know I want something like the service they provide in vps cloud. Some sort of file made out of the system that can be applied to a fresh install with identical contents.
Finally feel the need of a backup so I won’t lose all that I have customized and set through laborious work.
Hi, I would love to give my thoughts without comprehensive experiences on each and every backup tool. Some of them are alternative approaches rather than complete system backup.
Backup /etc directory using rdiff-backup (CLI) or Deja-Dup (GUI)
Deciding factor: Workstation or Server/ which cloud service
Workstation: The simplest/lightest way will be to backup /etc directory. This way consumes the least amount of storage and backup time. This assumes all of your post-install configurations are stored in /etc. The command-line-based app I tested and use is rdiff-backup. Deja-Dup (Called backup in software repo) is another tool I use. The back-end of Deja-Dup is duplicity or restic - you can choose in GUI settings.
Cloud service as backup destination: Which cloud services you are going to use for remote backup? The choice of cloud services affect the compatibility of backup standards.
Snapshot: I haven’t tried it.
Immutable OS: Silverblue or KInoite.
I can reboot/rollback to the previous working one just like git workflow. So it is kind of achieving what I expect. /etc directory still needs to be backed up separately.
Installation script: if you expect provisioning for many different devices and you wish to share the configuration with others, this will be handy. Probably it will only make sense if you have a workgroup/friends to share your configuration steps.
Perform a Kickstart Installation: an alternative to the installation script. You can save the Kickstart config file in USB and run it as boot media.