Verification

All transfers in OffShoot are always verified, so you can be sure your files are copied safely. By default, this is done using the Transfer Verification method. If you need more thorough verification and protection, you can set a different mode in OffShoot > Settings > Transfers > Verification

Checksums

XXH64BE Checksums are always generated from reading source files and stored in Transfer Logs and MHLs. It's also possible to generate one or all legacy checksums (MD5, SHA1, C4).

Generating legacy checksum can affect overall transfer speed.

Verification modes

Transfer

To enjoy maximum transfer speed, the file sizes of both sources and destinations are checked against each other. Note: do not use this mode if you plan to erase your sources.

Source

To rule out read errors, an independent source checksum verification is done. On destinations, the file size is verified. Use this mode if you’re erasing your sources while creating multiple backups.

When a source verification issue is found, the transfer stops. If a Destination verification issue is found, the transfer will continue and be completed with warnings.

In this mode, OffShoot first performs a pre-read of the file to verify its integrity, then reads it again to perform the actual copy operation.

Source & Destination

All sources and destinations are independently verified for maximum protection by reading back everything and comparing the resulting checksums and file metadata. Typically, it takes twice as long as Transfer Verification.

  • Choose this mode when creating ASC MHLs.

  • When a source or destination verification issue is found, the transfer will continue and complete with warnings.

These modes got a makeover in OffShoot 24.3. For older OffShoot versions, the following legend can be used:

  • Checkpoint OFF -> Transfer

  • Checkpoint ON (Backup) -> Source

  • Checkpoint ON (Archive) -> Source & Destination

MHL awareness

In Source and Source & Destination verification modes, OffShoot will automatically detect (ASC) MHLs on the source, and uses the listed checksums instead of rereading the source file.

OffShoot will only use the (ASC) MHL checksum when the file size and modification date match the referenced file.

Automatic MHL verification

In Transfer and Source verification modes, when transfers are successful and the Destination is idle, OffShoot will automatically reverify the newly created (ASC) MHL on the destination. When an issue is found, OffShoot will try to copy the file again using the Source or another Destination.

Manual MHL verification

It's possible to verify data without doing a transfer. Just double-click an (ASC) MHL file and then click Verify.

Available in OffShoot 24.3 and newer

  • Detects missing files and files with a hash issue.

  • The verification results will be recorded in a log (hint: click the status underneath the progress bar to open the verification log).

  • All ASC MHL files referenced in the ASC MHL chain.xml will be verified.

Batch Verify MHLs

Batch verify all (ASC)MHLs in a drive or folder via the context menu of a Disk.

Available in OffShoot for Windows 25.2 and newer

Source Verification issue event

Fires when a source verification issue is detected.

Broken Media Detection

OffShoot displays an alert when 0-byte media files are detected on the source. This issue typically occurs with ExFAT-formatted cards that have not been ejected properly.

If Broken Media Detection somehow blocks your workflow, you can configure OffShoot to dismiss the alert automatically after 20 seconds. Use the following command in Terminal/PowerShell ( 1 = enabled, 0 = disabled).

defaults write nl.syncfactory.Hedge.Mac SFIDefaultsZeroByteFilesDetectedAutoContinue 1

Missing files detection

At the end of a transfer, OffShoot checks if all files are present on the destination. If any are missing, an alert is shown and a warning is logged.

Last updated