The simplest soln has to be NFS share the big disk.
Anything else is going to be less stable/reliable. Doesn't mean it won't be good enough, just not as good and def more complex.
If individual files are small enough (ie fit into small machine RAM easily), I'd consider multi-thread, 1 to listen to incoming stream, then Thread::Queue to output thread that sends file to big box.
This may seem a bit daunting if you haven't done threading, but it's not that bad.
Do you have some time in between each incoming file? If so, you may be able to do same thing (ie mem buff) without threads.
In theory, even without sufficient mem to swallow 1 file, you could still use the threading method.
Cheers
Chris

In reply to Re: recording a stream of data remotely, and reliably by chrism01
in thread recording a stream of data remotely, and reliably by qbxk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.