Hi
This is not a forensic question really, but we have a problem trying to transfer a large file (15GB) down a flaky comms line (2,000 miles from host to target) which tends to result in a corrupted transfer. Flaky, as in up and down like the proverbial.
File is a compressed backup of an SQL database. Assume that we can do nothing about the comms line.
Was wondering if any folks out there have encountered this and if so any suggestionss for building in fault recovery?
I wondered if using FTK Imager, creating a compressed custom AD1 image (with the option of encryption) in manageable chunks (say 100MB for arguments sake) would be a sensible option?
And then open and export from FTK Imager on the target system.
Any thoughts?
Cheers
Sorry to be so low tech
Is there any reason why not cannot create an encrypted area on a thumb drive, copy your data into it and then courier /post it.?
Ludlowboy - it may yet come to hand-carrying, but this is from Canada to US and we've had bad experience in the past of people/data/computers/disks/CDs/software being turned back by Homeland Security (
BTW - did you know that Ludlow is one of only for racecourses in UK which don't contain any of the characters "r a c e" in their name? )
Cheers
I think your concept of using FTK to "chunk" your data is the right solution.
mbt
Could you use robocopy? (http//
If acceptable encrypt it and put it on a P2P network such as bit torrent these networks are designed to deal with just that sort of issue.
Terra copy is pretty good too, confirms all copies.
Also, if you are using FTK, could you not in the same premise split it into RAR files of XX chunks in size and they can then be unzipped into the one file at the other end?
Thanks all for your suggestions.
PaulS - hadn't considered this so thanks
4Rensics - don't know Terra copy, will go have a look-see. Apparently we've tried 7Zip before and it works 99%, which clearly is a pain when the 1% makes you start over (
Thanks again everyone
This is a job for rsync. You can run rsync on both endpoints and kick off the copy. They will verify, via hashing, that the data received is the data that was sent. Rsync supports transport compression, and tunnels over ssh. If it gets aborted, just rereun–it will calculate hashes over what exists on the destination to be sure it's consistent with the source, and then transfer the needed data.
Also, rsync can work on a single file or on a directory of files recursively.
Jon
If you are going down the "split files" road, you can use .par files allright
http//
http//
that's what has been used on usenet to lessen the problems with wrong data transfer.
jaclaz