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

Backup S3-compatible bucket using Rustic #1278

Open
Wouter0100 opened this issue Oct 1, 2024 · 6 comments
Open

Backup S3-compatible bucket using Rustic #1278

Wouter0100 opened this issue Oct 1, 2024 · 6 comments
Labels
A-backends Area: Related to backends in `rustic-core` A-meta Area: Project wide C-enhancement Category: New feature or request

Comments

@Wouter0100
Copy link

It would be really nice to, instead of a filesystem or stdin, backup a S3-compatible bucket using rustic.

I've tried various techniques (rclone mount for example) and then read that mount by rustic, but it's very inefficient in deciding what files are changed and results in a lot of API calls to S3. I think it should be able to do it more efficient.

@github-actions github-actions bot added the S-triage Status: Waiting for a maintainer to triage this issue/PR label Oct 1, 2024
@bebehei
Copy link

bebehei commented Oct 1, 2024

hey @Wouter0100 I'm having the same issue, I'm currently testing it with Hetzner S3 storeage and rustic 0.7.

You might want to look at #1044 and #1045.

Apparently the s3:... endpoint is canceled and opendal:s3 should be used. I'm currently testing this while writing this comment.

The docs right now are confusing, because there is no separate section in the docs, but "Other services using rclone" pointing into the direction of rclone, but not opendal.

@simonsan
Copy link
Contributor

simonsan commented Oct 1, 2024

The docs right now are confusing, because there is no separate section in the docs, but "Other services using rclone" pointing into the direction of rclone, but not opendal.

That's right, I think that is missing, and I started to work on it in: rustic-rs/docs#90

@simonsan simonsan added C-enhancement Category: New feature or request A-backends Area: Related to backends in `rustic-core` A-meta Area: Project wide and removed S-triage Status: Waiting for a maintainer to triage this issue/PR labels Oct 1, 2024
@aawsome
Copy link
Member

aawsome commented Oct 1, 2024

Note that we are talking about two things here: opendal providing access to the repository and opendal as a source to run backups on (which will then be stored in a repository, independent from how to access this).

For the first, most is implemented but docu and edge case handling needs improvement.
For the second, we don't have an implementation yet.

@Wouter0100
Copy link
Author

Yes, my feature request was for the second part. Being able to backup a S3 bucket (for example, using opendal) towards a rustic repository somewhere.

aawsome added a commit to rustic-rs/docs that referenced this issue Oct 1, 2024
Add basic service documentation for using opendal.

Ref.: rustic-rs/rustic#1278

---------

Signed-off-by: simonsan <[email protected]>
Co-authored-by: Alexander Weiss <[email protected]>
@simonsan
Copy link
Contributor

simonsan commented Oct 1, 2024

@bebehei the documentation is now live: https://rustic.cli.rs/docs/commands/init/services.html

Is that sufficient for you? If not, we would welcome a pull request against the docs. Cheers!

@bebehei
Copy link

bebehei commented Oct 1, 2024

I just had been successful adding a S3 repo into my storage. Thanks for fixing this so fast!

Docs seem to be very fine. There is a copy-pastable example and link to the reference. Thats everything you need, when you start fresh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backends Area: Related to backends in `rustic-core` A-meta Area: Project wide C-enhancement Category: New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants