Modtimes issues on dropbox

Help and Support
1

I’m moving my backup solution from dropbox to Wasabi, due to dropbox problems with check sum / hashes.

I used a cloud VM to execute a copy from dropbox to Wasabi, which occurred without any problems. Here is the output of one of the jobs:

Transferred:   26.633 GBytes (12.645 MBits/s)
Errors:                 0
Checks:                 0
Transferred:        44928

So I ran a check between dropbox and Wasabi, and confirmed that everything was ok:

Transferred:      0 Bytes (0 Bits/s)
Errors:                 0
Checks:             44928
Transferred:            0

However, when I run a sync from the local folder (which was previously synced to dropbox) to Wasabi it is sending again about half of the files.

Some are ok:

2018/04/25 11:03:07 DEBUG : [file]: Size and modification time the same (differ by 0s, within tolerance 100ns)
2018/04/25 11:03:07 DEBUG :  [file]: Unchanged skipping

And some are sent due to the small modtime difference:

2018/04/25 11:02:58 DEBUG : [file]: Modification times differ by -149.2003ms: 2017-08-23 20:31:05.1492003 -0300 -03, 2017-08-23 20:31:05 -0300 -03
2018/04/25 11:03:02 INFO  : [file]: Copied (server side copy)
2018/04/25 11:03:03 INFO  : [file]: Deleted
2018/04/25 11:03:06 INFO  : [file]: Copied (new)

(the “server side copy” is due to the backup-dir parameter).

Is there any way / parameter to “force” that modtime be copied identically from dropbox to Wasabi? I would make a new copy, which would be much faster than re-uploading half of the files (this above is just one of the jobs).

2

Unfortunately the modification times on dropbox are held only accurate to the second, whereas the ones on Wasabi are held accurate to the nS.

So the transfer local disk -> dropbox -> wasabi caused the modtimes to become truncated to the nearest second.

What I suggest you do is do a sync without --backup-dir and that will just correct all the modtimes without filling up your backup dir.

Or alternatively use --modify-window 1s to say that your modtimes are only accurate to 1s.

3

Thanks Nick.

After a few years using dropbox, and after the various recent issues, I’ve come to the conclusion that it s#$%&# … :angry:

1 Like