Skip to content

Add bzfs to Backups section#671

Open
whoschek wants to merge 1 commit intoawesome-foss:masterfrom
whoschek:wip/bzfs
Open

Add bzfs to Backups section#671
whoschek wants to merge 1 commit intoawesome-foss:masterfrom
whoschek:wip/bzfs

Conversation

@whoschek
Copy link

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 you 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?

bzfs replicates snapshots from many local or remote source ZFS datasets (and their descendants) to local or remote destination datasets, using zfs send/receive and ssh, and can operate at sub-second intervals across large fleets of hosts for DR/HA.

  • Have you used it? For how long?

Yes, for more than 2 years.

  • Is this in a personal or professional setup?

This is engineered for reliability at high scale in professional setups. Can also easily be used in personal setups.

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

Dozens of hosts.

  • Biggest pros/cons compared to other solutions?

Some scripting skills are helpful to get the most out of this software.

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

Strong support for disaster recovery and high availability (DR/HA), scale-out deployments, and protection against data loss or ransomware.

@Technetium1
Copy link
Collaborator

This will require some users to vouch for it in my opinion, but I appreciate the active development and think it's a cool project. https://github.com/whoschek/bzfs/graphs/contributors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants