Re: Un-attended Large Archives

> > 1) Create a named pipe. Say, $INFORMIXDIR/archpipe. > 2) Adjust your TBCONFIG file to write archives to the named pipe. > 3) Write a simple C program which reads from the named pipe > and begins writing to the first tape, then switches to the > second when the first is full. > Yup. We did the same thing, but for the purpose of dealing with the problem of the database being locked while the tape is rewind. Our archive program is called p2t (pipe to tape), and restore is t2p (tape to pipe). You may send p2t as many tape drive parameters as you have, and they will all be used. Speaking of which, on page 3-113 of the Online 5.0 System Administrators manual (my bible), there is a list of "THINGS to AVOID in the ONLINE ENVIRONMENT". Item #3 states: Do not define your archive tape devive (TAPEDEV) as a named pipe. Can anyone please tell me why not? We have been doing our archives thru a named pipe on many production systems, and have restored with no problems. Maybe i'm headed for trouble and dont know it yet. Naomi -- Naomi Walker (aka N7FSA) naomi@anasazi.com Phoenix, Arizona To get the full value of joy, you must have someone to divide it with. ---Mark Twain