Whats your average write speed for imaging drives?

I normally reckon on about 60GB/hour (including MD5 and SHA-256 hashing). This is with USB 2.0.

Your figure is similar.

Greetings,

I use eSATA for my destination drive whenever possible. I tested some acquisition tools awhile ago and the results are here

http//integriography.wordpress.com/2010/11/18/testing-acquisition-tools/

In several tests, I imaged a 160GB drive in about 35 minutes. The gating factor here isn't the destination drive interface.

I'm looking forward to trying Thunderbolt for my destination drives. The gating factor at that point will be the source drive.

-David

Keep in mind that no matter how fast you get your connection to your source/destination drives, you still have the read/write limitations of the drives themselves.

Anyone using the T35es with Esata? What speeds are you getting off of it?

90 MB/sec overall average for SATA source over eSata (T35es WB) to NFS share. Using both source and destination SATA drives about 90 - 100 MB/sec.

Greetings,

I use eSATA for my destination drive whenever possible. I tested some acquisition tools awhile ago and the results are here

http//integriography.wordpress.com/2010/11/18/testing-acquisition-tools/

In several tests, I imaged a 160GB drive in about 35 minutes. The gating factor here isn't the destination drive interface.

I'm looking forward to trying Thunderbolt for my destination drives. The gating factor at that point will be the source drive.

-David

David, I'm shopping for a bridge and like the pricing on that model, but a review on Amazon of all places has kept me from biting. Have you found it to be a slower bridge than the Tableaus?

Greetings,

I've not done a head to head between the UltraDock and the Tableau, but I am very happy with the UltraDock. Also, the UD packs a bit smaller. They're both excellent kit.

-David

In several tests, I imaged a 160GB drive in about 35 minutes. The gating factor here isn't the destination drive interface.
-David

Interesting results. Any reason why you didn't incorporate image verification?

Greetings,

In retrospect, I should have. I was really just focused on imaging speeds at the time. I should redo that report, and add in my TD1 and anything else I can get my hands on.

-David

It's definitely interesting that even with a powerful box like that, the compression still over doubles the acquisition time.
Something i'd like to then test is processing time on the resulting images. Uncompressed versus fully compressed. Have to make a note to remind myself to test that if I ever get a chance. Be interesting to see how long a hash/sig/keyword search on the uncompressed image takes versus the compressed one.