Rclone is the right software to copy multi-terabyte file repositories from one place to another! It’s also very capable at rearranging files in lots of other different ways. Check it out. It’s something of a sister program to rsync on unix.
I had to fiddle with rclone a bit. Here is the command I ended up using:
c:\aaa\rclone\rclone sync –modify-window=2s -v –exclude=”System Volume Information/**” d:/ f:/[my new repository]
It was so simple (after a two weeks of fiddling and yelling at my computer). Just run that command, wait 3 days (yipe, I’ve got some bandwidth/scale problems) and profit!
(If you copy-paste that text, make sure you don’t use smartquotes, use regular quotes)
Let’s look at that command one argument at a time:
rclone isn’t installed, perse, on a windows computer. You just unzip it and go! That means it doesn’t set PATH variables (unless you do it yourself. So I open up a Windows Powershell with Admin rights, specify the folder to run in (c:\aaa\rclone in my example) and go!
It’s so magically simple. Sync is better than copying because it will delete extra files on the target side.
The FAT file system doesn’t accurately capture file modification times. So every time you run rclone, it’ll compare file modification times and get it wrong. If you turn on very verbose mode with “-vv” you’ll see errors like “Modification times differ by 1.490000000s”, and it’ll copy files over and over and over :-(. This “modify-window” setting says “if the files were modified within 2 seconds of each other, don’t sweat the difference.
“-v” is “verbose” mode, “-vv” is very verbose mode, for when you want to figure out why your rclone session is failing. You can eliminate it when you are sure of your sessions.
–exclude=”System Volume Information/**”
I’m copying from the root (d:\) If I don’t specify this, rclone will try (and fail) to grab files from the system volume information folder.
d:/ f:/[my new repository]
Note that I’m using slashes instead of Window’s backslashes. It might not be essential but rclone (and I) prefers slashes.
What doesn’t work:
Windows File Explorer drag-and-drop copy doesn’t have enough checking, the ability to recover a failed copy, or the ability to “sync”.
Teracopy can copy but not sync. It recovers a bit better from failed copies but not well enough for my 2TB file moves. I think it created system instability, crashing a few times at inopportune times.
Robocopy not enough checking, mediocre recovery from failed copies, not enough feedback.
Windows File History might actually be useful as a local backup tool. I played with it a bit and seemed to work well on a local network. Though it kept nagging me when a computer wasn’t connected (yes, I know, I turned the other computer off an hour ago). Though I’ll likely stick with rclone and Backblaze instead of learning 2 tools.
Minio on a server with some fancy buy-once Amazon AWS compatible backup software for the client like Arqbackup was a good idea until I found that Minio needed to be manually updated every couple weeks or it would refuse to start up.