jimsalterjrs/sanoid

These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 18th, 2026
Created on November 17th, 2014
Open Issues & Pull Requests: 157 (+0)
GitHub issues: Enabled
Number of forks: 346
Total Stargazers: 3,861 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.1 hours
Mean response time: 74.3 days
90th percentile: 206.9 days
Tracked items: 114

Most active contributors

Sign in to see contributor activity.

How this project is maintained

98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 58
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 779 days
Stale 30+ days: 54
Stale 90+ days: 49

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (6)
  • question (4)
  • help wanted (2)
  • duplicate (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Sanoid is a policy-driven snapshot management and replication tool for OpenZFS filesystems. It automates the creation, retention, and replication of ZFS snapshots according to configurable policies, eliminating manual intervention in backup and disaster recovery workflows. The tool uses OpenZFS's native snapshot capabilities as its foundation, allowing administrators to define retention schedules and replication targets through policy configuration rather than custom scripting.

Sanoid suits environments where ZFS is already deployed and where consistent, automated snapshot management across multiple systems is required. It works well for backup strategies that depend on frequent snapshots with tiered retention, and for replication scenarios where data must be synchronized across local or remote storage pools. The tool is particularly valuable in setups where policy-driven automation can replace ad-hoc snapshot management, reducing the risk of missed backups or inconsistent retention practices.

The project maintains active development with regular commits addressing bug fixes and feature improvements. Contributions from multiple developers indicate ongoing community engagement with the codebase. Issue tracking shows responsiveness to reported problems, with maintainers addressing user-reported concerns and edge cases. The project demonstrates sustained attention to reliability and correctness in snapshot and replication operations, which are critical functions where failures directly impact data safety.