Copying files/folders with CRC checking

I see various backup software which employs CRC checking, but is there a way to utilize CRC to copy files (and files within) directly?

There are times I'd like to have that extra measure of security, but not with any kind of convoluted automated archival routine - rather, just manual copying of files and folders. Back in the old days, there was a file copy utility by Norton where you could copy in just this manner, but with CRC redundancy to ensure your files copied in tact.

I don't know of any way to invoke CRC in the normal Explorer shell, but would like to know if there is such a thing.

 

What do you mean by copying files "directly"?

If you copy files with a Cmd Prompt, you can use the switch /v to verify files are copied correctly. In the Cmd Prompt window, enter copy /? to see the syntax.

 

By "directy," I simply mean using an interface, such as Explorer, to copy the files in the usual manner (such as copy/paste, drag/drop,etc). In other words, without using a scheduled backup program which imposes its own formatting, etc.

CMD isn't too bad an idea, but a bit cumbersome. Seems there would be some routine which could provide a simple copying interface, or a context feature, which incorporates some form of checking, such as CRC.

 

I personally think you are overcomplicating this. Years ago, CRC checking was included in the copy command but all it really did was slow down the copy process - which can already be agonizingly slow. The file copy process is extremely reliable. About the only way to mess it up is to kill the power during the write. But even then, you still have the source file.

The bottom line is this: "Always keep multiple copies (backups!) of all our important files!"

Let's say you copy your files from Drive 1 to Drive 2 and then you go through the time and trouble to verify all the files copied correctly. Then what? Are you going to erase the files from Drive 1? If so, why didn't you just move them ("cut and paste" instead of "copy and paste")? And then, is that your only copy of those important files? That would not be wise.

Let's say you copy your files from Drive 1 to Drive 2, verify, then delete them from Drive 1. What happens if Drive 2 fails? Your house burns down, is flooded or is blown away by a tornado? What if your computer takes a huge power surge from a lightning strike? Or a bad guy breaks into your home and steals your computer? Or your computer and all your files are compromised by malware?

What you really need to be doing is backing up all your files - with multiple copies and preferably with at least one copy "off-site", either out in "the cloud", on a backup drive stored at a friends or relative's house, or what I do and keep a copy on a drive in my safe deposit box at my bank!

See How do I confirm that a file has been copied correctly? But I do recommend you heed his comments in that light blue text box.

 

Thanks for the tips.

Actually, I do understand and agree with the multiple backups. In fact, that's part of why I'm wondering this. Because of all the copying.

Maybe I'm just being a little paranoid, and it's not the most essential thing in the world, but I'm just wondering if there's a way of copying with that extra layer of security. It's not in lieu of backups.

What I'm currently looking to do is pull a lot of my scattered files onto one drive, now large enough to hold them all, instead of having a number of locations, each of which requiring backups (which gets to be convoluted). Not to mention it's impossible to tell what the main versions are. Pulling things together onto one drive then makes backing that drive up easier. So it's a process of pulling all the various locations together onto the "main" drive. Once the main drive is duly backed up and verified, then the extraneous copies of files can be deleted from the various devices. Then it's just a matter of keeping the essential folders on the main drive backed up, and ensuring any other devices have their files copied or moved to the main, regularly.

 

Main versions? You mean original? You will have to look at time stamps of the source files. But those will change but should still show last modified date if you right click on the file and select properties. In any case, they will be identical.

Since this will be a one-time process, it still seems the command line method will work. You might also look at https://www.howtogeek.com/206123/how-to-use-fc-file-compare-from-the-windows-command-prompt/