How to deal with version control of large amounts of (binary) data
What I am ending up using is a sort of hybrid solution:


backup of the raw data
git of the workflow
manual snapshots of workflow + processed data, that are of relevance, e.g.:


standard preprocessing
really time-consuming
for publication



I believe it is seldom sensible to have a full revision history of large amount of binary data, because the time required to review the changes will eventually be so overwhelming that it will not pay off in the long run.
Maybe a semi-automatic snapshot procedure (eventually to save some disk-space, by not replicating the unchanged data across different snapshots) would be of help.