Track rename - Only on server side copy?

Feature
1

Am I right in thinking that track renames only works on server side copies?

I sync two gdrives, and want to rename the format of my movies on bucket 1, and dont really want to download and upload them all at 750gb a day.

Any hints or tips?

2

Are you using crypt remotes? If so, that would not work.

The way track rename works is by comparing file hashes so it's fine to work between remotes but if they are encrypted, the hashes will not match so it would not work.

3

No crypt.... just filenames.

So I can use track rename without server side copy?

4

Test it out and validate. The method of copy doesn't matter.

It compares a hash from source to dest and if they match, they are considered the same.

5

Actually in the the latest beta we have

  --track-renames-strategy string   Strategies to use when synchronizing using track-renames hash|modtime (default "hash")

So you could use --track-renames-stragegy modtime if they have the same modification times

6

How does that work functionally? If you use modtime but the hash is different, how would that be a rename? I'm missing something.

7

I'll find a folder thats just bigger than the 750gb and have a play and see what happens....

I'll report back!

8

That is for when you are using a remote which doesn't support hashes (eg anything wrapped in crypt).

Using hashes is best - you have 128 bits of check that they are the same file. Modtime checking works pretty well though (remember the size has to match too).

9

Just wanted to say THANK YOU!! This is working beautifully.

I had ~2000 files all over 10Gb that got renamed. Was looking at taking almost a month to re-upload to GDrive. This renamed them within 15 minutes and now my nightly sync works as always.

1 Like
10

Great - glad it worked :slight_smile:

11

Hello ncw,

I try to use --track-renames-strategy modtime but seen like it's doesn't work:

rclone sync --track-renames --track-renames-strategy modtime --dry-run -v "F:\Cache\Test" "Google Drive:Test"
2020/06/08 10:08:52 INFO  : Google drive root 'Test': Making map for --track-renames
2020/06/08 10:08:52 INFO  : Google drive root 'Test': Finished making map for --track-renames
2020/06/08 10:08:52 NOTICE: newName.mkv: Not copying as --dry-run
2020/06/08 10:08:52 NOTICE: oldName.mkv: Not deleting as --dry-run
2020/06/08 10:08:52 INFO  :
Transferred:             0 / 0 Bytes, -, 0 Bytes/s, ETA -
Checks:                29 / 29, 100%
Deleted:                1
Transferred:            1 / 1, 100%
Elapsed time:         0.0s

It's still work normal with --track-renames-strategy hash:

rclone sync --track-renames --track-renames-strategy hash --dry-run -v "F:\Cache\Test" "Google Drive:Test"
2020/06/08 10:08:03 INFO  : Google drive root 'Test': Making map for --track-renames
2020/06/08 10:08:03 INFO  : Google drive root 'Test': Finished making map for --track-renames
2020/06/08 10:08:04 NOTICE: oldName.mkv: Not moving as --dry-run
2020/06/08 10:08:04 INFO  : newName.mkv: Renamed from "oldName.mkv"
2020/06/08 10:08:04 INFO  : There was nothing to transfer
2020/06/08 10:08:04 INFO  :
Transferred:             0 / 0 Bytes, -, 0 Bytes/s, ETA -
Checks:                29 / 29, 100%
Renamed:                1
Elapsed time:         0.0s

I'm using rclone-v1.52.0-031-gc4110780-beta-windows-amd64

12

Please make a new post and use the Help and Support template so you include all the right info.

13

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.