The function tree would need to intelligently check the first directory on the source drive, then it would query if the same directory is found on the destination drive, if the folder has been found on both, then C++ will scan the contents of the nest level.
All I can write for you is the pseudo code. I researched what it would take for a program to recursively scan all directories and sub directories and compare the files that are on another drive. 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.TeraCopy verify would be the easiest solution, but all of the data has been copied and hashes have been created.įor your use a program has not been invented for what you are looking for.
Once the main drive is duly backed up and verified, then the extraneous copies of files can be deleted from the various devices. So it's a process of pulling all the various locations together onto the "main" drive. Pulling things together onto one drive then makes backing that drive up easier. Not to mention it's impossible to tell what the main versions are. 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). 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. In fact, that's part of why I'm wondering this. 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.Īctually, I do understand and agree with the multiple backups. 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! 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? Let's say you copy your files from Drive 1 to Drive 2, verify, then delete them from Drive 1. 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 and then you go through the time and trouble to verify all the files copied correctly. The bottom line is this: "Always keep multiple copies (backups!) of all our important files!" But even then, you still have the source file. About the only way to mess it up is to kill the power during the write. The file copy process is extremely reliable. 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. I personally think you are overcomplicating this.
0 kommentar(er)
