Geoff,

I would agree I don't think there is a tie to the Archive but perhaps some
insight to possible Journaling issues if you still have them?? We have
similar pipe messages along with a message ==> NpPeek: Nodata logged in the
dsmerror file daily. Unfortunately no message number so nothing to look up
to even get a clue as to what it means. The timestamp is during our
production backup window so I'm assuming that it's tied to the pipe messages
and that they are tied to the Journal. Getting ready to start client
upgrades. After that if we continue to see the same messages its Support
Center time.

Of course none of this has anything to do with helping your problem!

Curt Magura
Lockheed Martin EIS
Orlando, Fla.
321-235-1203


-----Original Message-----
From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL AT SAIC DOT COM]
Sent: Tuesday, February 04, 2003 10:07 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Archive errors


Curt,

I thought it odd to see these messages too. I can see these messages further
up the log and I have also seen the error messages on another server with
Journaling. It just so happens this computer does have Journaling on it, but
I am logged on via Timbuktu running the archive command I created from a
command prompt. So why then would these messages show up since it's an
archive? Why would Journaling be invoked and why the Named Pipe errors? For
that matter why the Named Pipe errors during a regular incremental backup?