Store of Hash Data from Verify Option for later Checks

[Stefan]

Dear  Shirouzu-san,

I'm using your fastcopy tool to generate long term backup on external drives (currently around 8 TB). 

I use the verify option to make sure that the copy works correct.

Due to the nature of backups I have to verify from time to time that there is no degeneration for backuped date. Therefore, I generate with a separate tool a hash file of the whole backup (file wise) and check the backup based on the hash file. 

Correct me if I’m wrong, but I think your tool is already generating this hash file internally to make the verify at the end of the copy process. Wouldn’t it be much more efficient for my use case to simply get the option to store the information to a separate file (and optional to extend an existing)?

In addition to this it would be great if a later verification could be proceeded as well.

What do you think about this?

Kind Regards

Stefan

[steve.v...@gmail.com]

Hi Stefan,

I am currently doing something very similar to what you described - I have a script which executes fastcopy via cmd, and specify the log file for outputting the details of the copy. If 'verify' is selected (I explicitly set MD5 as the hash), the log file contains the hash for each file.

I hope that helps!

Cheers,

Steve

[Stefan]

Hi Steve,

this sounds very similar to what I'm looking for. As I'm a real Fast Copy beginner. May it be possible for you to share a script example. This could help me.

Kind Regards

Stefan

[Stefan]

Hi Steve,

I found the right option to generate the logfile including the md5 hash codes.

Which tool do you  use to perform a later check of the copies files with this logfile?

My preferd tool (MD5 File Hasher) does not accept the generated logfile from fastcopy.

Tx for a hint.

KR

Stefan

[steve.v...@gmail.com]

Hi Stefan,

sorry for the delay in getting back to you, I don't check this forum too often. Glad to hear you have figured it out. For information,

I've set the following field in fastcopy2.ini:

'hash_mode2="0"

to ensure it generates MD5 hashes.

The command I run to execute fastcopy looks like this:

c:\fastcopy\fastcopy.exe /filelog=fclog.txt /cmd=diff /force_start /utf8 /verify=TRUE /balloon=FALSE /no_ui /srcfile=c:\manifests\copylist.txt /to="some destination"

The copylist.txt file just contains the list of files I want to copy in this particular run.

I have all this scripted up in an application I have written in python, which is also what I use to perform the verification of the MD5 hashes, but it is a bit buried/messy to pull out any useful snippets.

Cheers,

Steve