Thanks have passed your details on to our expert in this space.
For the public record this was mainly down to the problem of client reliability and migrating data live when there are 8,000 people hammering it with reads and writes. We went for a read/write through system and background synchronisation. The latter we had real reliability problems with and the upload performance wasn't great.
Also ROI didn't stack up in the end versus our SAN so we canned it.
Really? I deal with this daily. Can you email [email protected] - if you're genuinely having or had issues moving 22TiB to S3 please LMK as that's abnormal for our customers and I want to fix it for you and others.