I want to suggest adding MD5 checksums to the log file in IFL. Maybe it's already in the log file, in which case apologies - I have never used the log file and when I tried to find it I couldn't.
Now I see from another post here where the log file is and I'd have to mount a partition then write the file. So as another suggestion, it would be much simpler if the log file were to be just added to the folder that the .tbi file was being created in.
My reason for this request is that I copy .tbi files from a Windows machine to my home Linux machine for back up using a USB stick. A while ago I experienced file corruption due to a faulty stick which wasn't found until a restore was attempted, which was sadly too late. So until recently I have used MD5 checksums on the Windows machine to generate a small text file of checksums which I then re-check in the Linux machine to make sure the backed up copy is not corrupted. This worked fine in Windows 7 using the certutil program. However now using Windows 10, I have not been able to get any file checksum program to read the .tbi file. Windows 10 refuses to give permission. I have tried various googled solutions including a Terabyte article without success. Windows 10 is such a pain with file permissions, I thought it would be much easier to get the checksum from IFL while the archive is being created, if it is possible. Linux already has a md5sum utility so I would think this ought not to be too difficult to add.