We do basically the same thing, except we are using rsync over
ssh so we don't have to allocate the extra disk space on the client.

Rodney

Jim Ruskowsky wrote:

Mark -

We solved this issue by having a filesystem on the client (in the DMZ) to
which we locally
backed up server (we generate a ufsdump for each filesystem).

At some fixed point in time after the ufsdumps are kicked off, the
networker server scp's
the files from the dmz client onto a local disk.

With this setup, the only hole you open up is for scp - which is initiated
from inside the firewall.
You don't even need any networker software on the dmz client machine, but
you do need extra
disk space on both client and server for the transfers.

Hope this give you another idea how to solve this.

Jim

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER