Conference decwet::networker

    How about Option C:  All of the above.  Let's generate the bootstrap
    information, in a way that is accessible and useable if a disaster
    occurs, but let's move into the 1990s, and not use a printer and piece
    of paper to provide that record.
    
    My site has a reciprocal arrangement with another Digital facility, to
    store each other's critical NetWorker data, to be used in the event of a
    disaster to get us up and running quickly.  It seems to me this
    bootstrap information is the stuff I need to save,right?
    
    So, how can I replace this line printer specification with something
    that will move the files over the network to another site?  And yes, I
    know that expecting this to work is more subject to problems than a
    locally connected printer.  But a piece of paper, that can be used in
    only the place where it exists, will not cut it.
    
    Thoughts?
    
    Thanks!
    tl

Well, the notification page lets you put pretty much any command 
in it.  Some of the notifications already do email, maybe you can 
use that to mail the bootstrap info to anothe system.

Wes

    Hi Wes
    
    Wow, great idea.  The huge advantage of using mail for this is the
    already-in-place mail infrastructure that, being store-and-forward by
    nature, seems to be tailor-made for handling the cases where links
    along the way between source and destination might be temporarily down.
    
    Well now, in the Administrator interface, I see Customize ...
    Notifications ... Bootstrap.  If I edit that notification, I see
    "/bin/lpr -Tbootstrap -P%PRINTER" in the Action field.  I'll fiddle
    with a mail notification instead, and will report back with results.
    
    Thanks again!
    tl
    

    I see you're talking UNIX here, but as I was just hunting for this info
    for NT, I thought I'd add a pointer to topic 2376 in the old conference, 
    DECWET::DECNSR, which tells how to use CLMAIL for mailing the bootstrap 
    info. 
    
    Hans