hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Support multiple backup roots #91

New Issue
Open
opened 2026-05-28 22:32:51 +02:00 by parkel · 0 comments
parkel commented 2026-05-28 22:32:51 +02:00
Owner
Copy Link

Track and schedule backups across more than one backup root/storage target.

Acceptance criteria:

  • Design data model changes for roots/storage pools.
  • Define migration path from single global backup root.
  • Identify UI and retention implications.
Track and schedule backups across more than one backup root/storage target. Acceptance criteria: - Design data model changes for roots/storage pools. - Define migration path from single global backup root. - Identify UI and retention implications.
parkel added this to the Future / 2.0 milestone 2026-05-28 22:32:51 +02:00
parkel added the area: futurefeature labels 2026-05-28 22:32:51 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label area: future feature
Milestone
No items
No Milestone Future / 2.0
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#91
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?