John Gray wrote:A couple of points before I start!
Truecrypt vs. Veracrypt: I tried Veracrypt when it superseded Truecrypt in April 2015(?). I found that Veracrypt was slow when opening my data file. My understanding is that Veracrypt is more secure than Truecrypt, but I am not sure that the stuff on my data drive is that important. My main purpose in encryption is to render a large part of my hard drive inaccessible (and hence useless) to anyone who steals my cheap laptop from the library while/if my back is turned. AFAIK the FBI is not after me. I think that Veracrypt is a suitable choice for a major organizxation, on the servers and also on the corporate laptops.
RoboCopy (rktools.exe 06/06/2008 on my hard drive 12,049KB) I am using this version because that’s the first version I used. I wrote DOS BATch files to drive a variety of functions and those batch files still work for me. I have not found a reason to upgrade.
OK. The real reason is that I didn’t know that there was a later version. [sulk]Nobody ever tells me anything[/sulk].
Running Robocopy /? Produces text “ROBOCOPY :: Robust File Copy for Windows :: Version XP010”
Thanks for the parameter examples with Robocopy. I was feeling quite good about adding one more parameter (/MIR) to my belt, but now [sulk]I see that I shall have to bone-up on even more knowledge.[/sulk] So I shall explore /dcopy, /ndl, /np, /copyall in my outdated copy of Robocopy.doc, by which time you will have pointed out that I ought to just disable my Robocopy.exe by modifying my System Environment Variables
Code: Select all
“C:\Program Files (x86)\Windows Resource Kits\Tools\;T:\Batlap;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Codebox\BitMeterOS”
and I just know
that now you’ve seen that line I’ll be whipped even faster into the future (well, for me, the future)
Anyway, about /MIR ...
Thank you for the confirmation. I appreciate your cautions, and I know that my “/MIR” run (which deletes discarded folders and files from my daily backup drive) should be run only
after I have done the weekly run to backup the daily drive to the weekly drive.
Thanks too for the “/L” tip. I contemplated that, but quickly discarded the idea on the grounds that I was never going to read a volume of logging information before running the actual copy job.
Instead, I set up a few dummy folders and files and observed where they ended up (right where I expected) then deleted them from my data drive, re-ran the /MIR and observed that they had disappeared.