this has been requested a few times on the forum, e.g. for a special
sync job for the most important groups, or seeding of a new datastore
with a partial view of an existing one.
while it's possible to achieve similar results with hacky workarounds
based on group ownership and reduced "visibility", implementing it
properly is not that complex.
possible future additions in a similar fashion:
- exclude filters
- filtering in other API calls (tape, listing groups/snapshots)
- only sync/pull encrypted snapshots (less trusted off-site
location)
- only sync/pull latest snapshot in each group (fast seeding of new
datastore)
changed since v1:
- reworked filter to support different types, rebased
- dropped last patch
- add docs patch
Fabian Grünbichler (10):
api-types: add schema for backup group
api: add GroupFilter(List) type
BackupGroup: add filter helper
pull: use BackupGroup consistently
pull: allow pulling groups selectively
sync: add group filtering
remote: add backup group scanning
manager: extend sync/pull completion
manager: render group filter properly
docs: mention group filter in sync docs
docs/managing-remotes.rst | 6 ++
pbs-api-types/src/datastore.rs | 5 ++
pbs-api-types/src/jobs.rs | 96 +++++++++++++++++++++
pbs-datastore/src/backup_info.rs | 10 +++
src/api2/config/remote.rs | 73 +++++++++++++++-
src/api2/config/sync.rs | 5 ++
src/api2/pull.rs | 15 +++-
src/bin/proxmox-backup-manager.rs | 113 ++++++++++++++++++++++---
src/bin/proxmox_backup_manager/sync.rs | 21 +++++
src/server/pull.rs | 57 ++++++++++---
www/config/SyncView.js | 13 ++-
www/window/SyncJobEdit.js | 12 +++
12 files changed, 394 insertions(+), 32 deletions(-)
--
2.30.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
