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 to Rclone without creating tmp files #161

Open
Lexxior opened this issue Mar 26, 2023 · 3 comments
Open

Backup to Rclone without creating tmp files #161

Lexxior opened this issue Mar 26, 2023 · 3 comments

Comments

@Lexxior
Copy link

Lexxior commented Mar 26, 2023

I have a NAS that I have mounted in the docker container on my server
If I run the container restic creates tmp files until the storage on the server is full and then cancels the backup, leaving the tmp files

If I run restic bare metal on the server with restic -r rclone:Onedrive:/Backup/NAS backup /volumes/NAS --verbose it backs up directly to my Onedrive, not creating any tmp files and filling up the storage

Is it possible to achieve this behavior in the docker container too?

@pquerner
Copy link

pquerner commented Apr 2, 2023

How is the NAS mounted in the docker container? As a volume? Does mounting it as read-only help?

@Lexxior
Copy link
Author

Lexxior commented Apr 2, 2023

Yes as a volume via NFS - read only makes no difference and the temp files get created on the docker host, not on the NAS

@djmaze
Copy link
Owner

djmaze commented Apr 9, 2023

AFAIK restic always creates temp files during backup and recovery. You can only change the path.

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

No branches or pull requests

3 participants