Use same folder for --backup-dir

imthenachoman · November 24, 2018, 12:59pm

Is it possible for rclone to use the same folder as the file to save the backups. For example, if remote:drive:/path/to/file.txt will be modified or deleted, rclone would rename it to remote:drive:/path/to/file.txt.20181124?

gelsas · November 24, 2018, 5:28pm

I have the same question

ncw · November 24, 2018, 5:51pm

What you are asking for is for –suffix to work on its own without --backup-dir.

rsync supports this so rclone should too. However it doesn’t at the moment.

Can you please make a new issue on github about this and I’ll add it to the todo list!

Maybe one of you would like to help implement it?

imthenachoman · November 29, 2018, 2:58am

Added. Thanks!

github.com/rclone/rclone

Use same or relative path for backups when files will be modified/deleted: --suffix without --backup-dir

opened 02:58AM - 29 Nov 18 UTC

closed 09:46AM - 01 Jul 19 UTC

imthenachoman

enhancement

I think it would be awesome if `rclone` could make backups in the same folder as… the original file and/or a folder relative to the same folder. For example: - backup `remote:drive:/path/to/file.txt` to `remote:drive:/path/to/file.txt.20181124` - backup `remote:drive:/path/to/file.txt` to `remote:drive:/path/to/backups/file.txt.20181124` I was hoping to add this enhancement to the code myself but I cannot figure out the code. I know, at minimum, lines 147-148 in `rclone/fs/config/configflags/configflags.go` would need to be modified to allow `--suffix` without `--backup-dir`. I can tell some other files need to be updated like `sync.go` but can't make sense of `rclone`'s code structure to know everywhere that would need to be updated. If someone is willing to point me in the right direction I would add and test the enhancement myself then submit a pull request.