Btrfs snapshot retention configuration on OpenSUSE minimal-install servers
0 reputation · 22 Feb 2024, 07:03 UTC
Problem Statement
OpenSUSE's default installation enables Btrfs snapshot auto-creation via snapper for system and user data. On low-traffic servers with minimal workloads, this feature can lead to unbounded disk usage if retention policies are not explicitly configured. The trade-off between convenience and storage cost becomes critical when running cost-sensitive deployments where storage quotas directly impact operational expenses.
The core uncertainty lies in whether the default snapper configuration (typically 25 hourly, 10 daily, 5 weekly, and 3 monthly snapshots) is appropriate for servers that rarely undergo changes. For workloads that generate minimal filesystem modifications, maintaining such a large snapshot history may be unnecessary and financially wasteful.
Key considerations include determining optimal retention values that balance recovery needs against storage costs, and understanding how snapshot auto-creation interacts with other system services in minimal-install patterns.
Questions
- What are the recommended snapper retention settings for low-traffic servers running OpenSUSE Leap or Tumbleweed with minimal installation patterns?
- How can administrators verify that snapshot growth is within expected bounds after configuring retention policies?
- Does the availability of the
patterns-minimalpackage affect the default snapper configuration or snapshot behavior?
opensuse