Add FSArchiver to Backup Category (supplemental fix to the pull_request_template as well)

[vorwd]

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

• Your additions are Free software
• Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Format your submission as follows, where Demo and Clients are optional.
  Do not add a duplicate Source code link if it is the same as the main link.
  Keep the short description under 80 characters and use sentence case
  for it, even if the project's webpage or readme uses another capitalisation.
  Demo links should only be used for interactive demos, i.e. not video demonstrations.
  - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
• Additions are inserted preserving alphabetical order.
• Additions are not already listed at awesome-selfhosted
• The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any category you are creating has the minimum requirement of 3 items.
• Any software project you are adding to the list is actively maintained.
• The pull request title is informative, unlike "Update README.md".
  Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
  "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

---

Please take some time to answer the following questions as best you can:

• Why is it awesome?

Easily archive an entire filesystem (or multiple at once to a single archive) with a single command. Likewise, restore with a single command, even to a partition that is differing in size or even to one with a different file-system type. Differing from a single tar bkup, FSArchiver also creates the file-system when it extracts the data to partitions. Everything is checksummed in the archive in order to protect the data. If the archive is corrupt, you just loose the current file, not the whole archive.

• Have you used it? For how long?

I have, several times over the last couple years. I even wrote a overly worded how-to to help others. https://github.com/vorwd/supreme-palm-notes/blob/main/FSArchiver_Walkthrough.txt

• Is this in a personal or professional setup?

My use was personal, but could certainly be used in a professional setting and with scripted automation

• How many devices/users/services/... do you manage with it?

Have created and restored backups on all my devices with a disk, so 10+

• Biggest pros/cons compared to other solutions?

Manages the filesystem creation upon restore, prevents full data lose in the event of corruption of the archive, can backup all partions on a disk at the same time, and then restore only 1 or 2 of them to another disk if you wanted. Can backup a file-system from a 120GB partition, that contains on 20GB of data, and then restore it to a 64GB partition with ease and the OS will boot perfectly (ymmv).

Cons, figuring out how to make it do a specific restore function was a bit cumbersome, with minimal explanation for the use case I had, but reading the websiste a few times over, I came to figure it out.

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

As outlined above; I don't want to fanboy too much and seem biased. I believe I have outlined well above.

[vorwd]

The pull request guidelines do state "submit 1 item per pull request", and I have submitted 2 changed files. The reason for this is that I have "submitted 1 item" to be added to the list... however, whilst adding that item, I noticed a discrepancy between the guidelines and the sample provided. The guidelines stated "...under 80 characters, sentence case." but the sample stated "250 characters" and I felt should be updated for future submissions from others.