Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to only transfer new snapshots during instance/volume refresh #745

Open
stgraber opened this issue Apr 10, 2024 · 2 comments
Open
Assignees
Labels
API Changes to the REST API Documentation Documentation needs updating Feature New feature, not a bug
Milestone

Comments

@stgraber
Copy link
Member

Currently using incus copy --refresh or incus storage volume copy --refresh will have Incus compare the snapshot list on the source and destination and transfer any snapshots that the destination is currently missing.

But sometimes the destination server is purposefully dealing with less snapshots as some have been manually removed by the user. To handle that, the API should be extended so the user can specify that only the new snapshots should be copied.

In this instance, new should be treated as any snapshot that was taken after the most recent existing snapshot on the target.

This should be possible with a new migration field, matching API field and CLI argument and by the migration layer looking at the snapshot creation time during negotiation.

@stgraber stgraber added Documentation Documentation needs updating Feature New feature, not a bug API Changes to the REST API labels Apr 10, 2024
@stgraber stgraber added this to the soon milestone Apr 10, 2024
@ps-gill
Copy link
Contributor

ps-gill commented Apr 23, 2024

If available, I would like to work on this issue.

@stgraber
Copy link
Member Author

Sure, got it assigned to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Changes to the REST API Documentation Documentation needs updating Feature New feature, not a bug
Development

No branches or pull requests

2 participants