Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been needing to automate the moving of quite large amounts of data (possibly around 1TB/day+ in average. 60TB so far, and counting) to a separate, remote storage system.

I have so far been doing this by writing custom python code, because of some special challenges related to packing data in suitable chunks for network transfer, and for the protocols available (GridFTP in our case).

I was wondering if there are any material (articles, blog posts, or books - if they are really good) providing best practices and/or hints on how to write data management scripts in a robust and fault-tolerant way?

UPDATE/CLARIFICATION: I should add that we have more or less solved the file uploading problem (with comparing remote and local checksums). We need to handle a lot more than this though, since we are providing a "dropbox" like solution for all the projects at the HPC Center, so we basically manage everything from this dropbox interface, until a user wants a special file back from storage.

So, we need to handle projects, archiving events, meta data for all files, including creating checksums and the like, and all this in a fully automated manner, where one archiving event can consist of 5TB spread out on thousands of medium to small-size files.

This calls for writing our automation software in a robust and fault-tolerant manner, since we cannot really manually keep track of every single file that is stored.

Thus I'm looking more for general hints/best practices for writing software (and in particular for data handling/doing system calls), rather than just how to verify uploads.

Things for which I'd like to see best practices and hints on, are e.g: Exception handling, Logging, Verification, Automated tests etc ... and how to combine all this to get a solution that you can rely on without continually watching it (you should get a mail when you need to, etc).

share|improve this question
Use existing software. man rsync could help. And the sources... – mailq Sep 7 '11 at 23:00
Yeah, I guess that is generally true, but due to the GridFTP protocol restriction, we haven't been able to use rsync in this project ... – Samuel Lampa Sep 7 '11 at 23:03

I would use a classic checksum method, with tar archives.

  1. Create a tar
  2. calculate a SHA-1 checksum
  3. Transfert
  4. Compare the checksum

Easy enough to script, protocol independent and definitely the most reliable method.

share|improve this answer
Thanks! Yes, that is actually what we do for the actual uploading (although we unfortunately needed to resort to adler32 sums since this is what the remote storage system provides). Basically the file upload is only one of the things we need to handle though. We also need to manage different projects, archiving events, and metadata, in an automated way. Forgot to mention that in the main question. Will update. – Samuel Lampa Sep 8 '11 at 9:21

For the record, I think I found at least something myself now (but looking for more, if there is!):

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.