{"id":9603,"date":"2022-08-27T17:09:22","date_gmt":"2022-08-28T00:09:22","guid":{"rendered":"https:\/\/www.lee.org\/blog\/?p=9603"},"modified":"2022-09-03T11:01:48","modified_gmt":"2022-09-03T18:01:48","slug":"rclone-is-a-great-way-to-move-files","status":"publish","type":"post","link":"https:\/\/www.lee.org\/blog\/2022\/08\/27\/rclone-is-a-great-way-to-move-files\/","title":{"rendered":"Rclone is a Great Way to Move Files"},"content":{"rendered":"<p><a href=\"https:\/\/rclone.org\/\">Rclone<\/a> <a href=\"https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright wp-image-9608\" src=\"https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone-600x166.jpg\" alt=\"\" width=\"369\" height=\"102\" srcset=\"https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone-600x166.jpg 600w, https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone-300x83.jpg 300w, https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone-120x33.jpg 120w, https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone-50x14.jpg 50w, https:\/\/www.lee.org\/blog\/wp-content\/uploads\/2022\/08\/rclone.jpg 710w\" sizes=\"auto, (max-width: 369px) 100vw, 369px\" \/><\/a>is the right software to copy multi-terabyte file repositories from one place to another! It&#8217;s also very capable at rearranging files in lots of other different ways. Check it out. It&#8217;s something of a sister program to rsync on unix.<\/p>\n<p>I had to fiddle with rclone a bit. Here is the command I ended up using:<\/p>\n<blockquote><p>c:\\aaa\\rclone\\rclone sync &#8211;modify-window=2s -v &#8211;exclude=&#8221;System Volume Information\/**&#8221; d:\/ f:\/[my new repository]<\/p><\/blockquote>\n<p>It was so simple (after a two weeks of fiddling and yelling at my computer). Just run that command, wait 3 days (yipe, I&#8217;ve got some bandwidth\/scale problems) and profit!<\/p>\n<p>(If you copy-paste that text, make sure you don&#8217;t use smartquotes, use regular quotes)<\/p>\n<p>Let&#8217;s look at that command one argument at a time:<\/p>\n<blockquote><p>c:\\aaa\\rclone\\rclone<\/p><\/blockquote>\n<p>rclone isn&#8217;t installed, perse, on a windows computer. You just unzip it and go! That means it doesn&#8217;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!<\/p>\n<blockquote><p>sync<\/p><\/blockquote>\n<p>It&#8217;s so magically simple. Sync is better than copying because it will delete extra files on the target side.<\/p>\n<blockquote><p>&#8211;modify-window=2s<\/p><\/blockquote>\n<p>The FAT file system doesn&#8217;t accurately capture file modification times. So every time you run rclone, it&#8217;ll compare file modification times and get it wrong. If you turn on very verbose mode with &#8220;-vv&#8221; you&#8217;ll see errors like &#8220;Modification times differ by 1.490000000s&#8221;, and it&#8217;ll copy files over and over and over :-(. This &#8220;modify-window&#8221; setting says &#8220;if the files were modified within 2 seconds of each other, don&#8217;t sweat the difference.<\/p>\n<blockquote><p>-v<\/p><\/blockquote>\n<p>&#8220;-v&#8221; is &#8220;verbose&#8221; mode, &#8220;-vv&#8221; 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.<\/p>\n<p>&nbsp;<\/p>\n<blockquote><p>&#8211;exclude=&#8221;System Volume Information\/**&#8221;<\/p><\/blockquote>\n<p>I&#8217;m copying from the root (d:\\) If I don&#8217;t specify this, rclone will try (and fail) to grab files from the system volume information folder.<\/p>\n<blockquote><p>d:\/ f:\/[my new repository]<\/p><\/blockquote>\n<p>Note that I&#8217;m using slashes instead of Window&#8217;s backslashes. It might not be essential but rclone (and I) prefers slashes.<\/p>\n<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<\/p>\n<p>What doesn&#8217;t work:<\/p>\n<p><strong>Windows File Explorer<\/strong> drag-and-drop copy doesn&#8217;t have enough checking, the ability to recover a failed copy, or the ability to &#8220;sync&#8221;.<\/p>\n<p><strong>Teracopy<\/strong> 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.<\/p>\n<p><strong>Robocopy<\/strong> not enough checking, mediocre recovery from failed copies, not enough feedback.<\/p>\n<p><strong><a href=\"https:\/\/support.microsoft.com\/en-us\/windows\/file-history-in-windows-5de0e203-ebae-05ab-db85-d5aa0a199255\">Windows File History<\/a><\/strong> 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&#8217;t connected (yes, I know, I turned the other computer off an hour ago). Though I&#8217;ll likely stick with rclone and Backblaze instead of learning 2 tools.<\/p>\n<p><strong><a href=\"https:\/\/min.io\/\">Minio<\/a><\/strong> on a server with some fancy buy-once Amazon AWS compatible backup software for the client like <a href=\"https:\/\/www.arqbackup.com\/\">Arqbackup<\/a> was a good idea until I found that Minio needed to be manually updated every couple weeks or it would refuse to start up.<\/p>\n<p>keywords: backup<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Rclone is the right software to copy multi-terabyte file repositories from one place to another! It&#8217;s also very capable at rearranging files in lots of other different ways. Check it out. It&#8217;s something of a sister program to rsync on unix. I had to fiddle with rclone a bit. Here is the command I ended [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,14],"tags":[],"class_list":["post-9603","post","type-post","status-publish","format-standard","hentry","category-geekery","category-product-recommendations"],"_links":{"self":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/9603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/comments?post=9603"}],"version-history":[{"count":10,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/9603\/revisions"}],"predecessor-version":[{"id":9621,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/posts\/9603\/revisions\/9621"}],"wp:attachment":[{"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/media?parent=9603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/categories?post=9603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lee.org\/blog\/wp-json\/wp\/v2\/tags?post=9603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}