PP-286 earlier hands-on check record, October 3, 2026

Historical record. This small check was run on October 3, 2026, before Practical Picks adopted its research-only method later that day. It is kept as a dated observation and did not decide the recommendation in the current article, which rests on public documentation, release records and security advisories (reviewed October 20, 2026). Practical Picks no longer runs product checks. FreeFileSync, added to the comparison on October 20, 2026, was not part of this check. The versions below were current on October 3; on October 20, 2026 rclone 1.75.2 had replaced 1.75.1, which is affected by advisories that need --links or rclone selfupdate, neither of which this check used. The record shows what happened once with ordinary folders standing in for a drive, not how the tools behave with a real removable drive or large folders.

October 3, 2026. The portable Python 3 test harness creates only synthetic task-local folders. Captured original commands, stdout, stderr, exits and folder states are retained. No real user files, physical drive or network destination were used.

Tool binaries

Run in a disposable directory

Place the three binaries where you choose. Set their absolute paths and a fresh task directory before running the Python harness:

PP286_WORKDIR="$PWD/pp286-work" \
PP286_RSYNC=/absolute/path/to/rsync \
PP286_RCLONE=/absolute/path/to/rclone \
PP286_COPYCAT=/absolute/path/to/copycat \
python3 challenge.py

The harness creates a fresh source and target for each command. First it tests preview/apply with one unchanged file, one changed file, one new file and two target-only files. It copies any saved displaced files into a separate recovery folder. It then tests changed content with equal size and mtime, missing source, and missing target. It captures outcomes as JSON in PP286_WORKDIR/challenge.json. It deletes and rebuilds only its own challenge subdirectory, so use an empty dedicated workdir. Original JSON absolute paths are capture locations; replay paths differ.

A missing target is intentionally created by all three tools on apply in this simulation. For a real removable drive, confirm the mountpoint separately before any destructive command. A mirror is not a versioned backup. Use a different recovery directory per run; our repeated-run test overwrote the prior saved file of the same name in the reused directory.