Skip to content

STAC-24630: Add stackgraph-v2 backup/restore - #32

Open
craffit wants to merge 10 commits into
mainfrom
stac-24630
Open

STAC-24630: Add stackgraph-v2 backup/restore#32
craffit wants to merge 10 commits into
mainfrom
stac-24630

Conversation

@craffit

@craffit craffit commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Adds documentation for the new sstackgraph backup/restore v2. The interaction is documented in this docs PR: rancher/stackstate-product-docs#360

@craffit
craffit force-pushed the stac-24630 branch 3 times, most recently from 140322e to fbd2289 Compare July 16, 2026 14:34
Comment thread cmd/stackgraphv2/abort.go
Comment thread cmd/stackgraphv2/backfill.go
Comment thread cmd/stackgraphv2/check_and_finalize.go Outdated
Comment thread cmd/stackgraphv2/restore.go
Syncing a bucket restamps LastModified, so synced archives tie and `restore --latest` picked an arbitrary one.
@viliakov

Copy link
Copy Markdown
Contributor

Pushed eec5a85: stackgraph and stackgraph-v2 now order backups by object key instead of S3 LastModified.

Found while diagnosing why StackVista/verify-backup's topology validation fails — stackgraph-v2 restore --latest picked sts-backup-20260724-0642.graph.v2 over the newer -0701. Both archives had the same LastModified because verify-backup's S3 sync restamps every copy, so the sort had nothing to order on. Backup names embed a sortable timestamp, which survives copying.

Applied to restore --latest and list for both v1 and v2 so they agree. Other datastores use different naming schemes and are untouched.

@kkaempf kkaempf added this to the Wrapping up summer milestone Sep 1, 2026
@craffit craffit self-assigned this Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants