Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Status\s+code\s+24\s+on\s+scheduled\s+vault\s+policy\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Status\s+code\s+24\s+on\s+scheduled\s+vault\s+policy\s*$/: 2 ]

Total 2 documents matching your query.

1. [Veritas-bu] Status code 24 on scheduled vault policy (score: 1): Author: WebsterR AT mont.disa DOT mil (WebsterR AT mont.disa DOT mil); Date: Wed, 16 Mar 2005 11:02:37 -0600; This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --_=_NextPart_001_01C52A49.F475D2CE Content-Type: text/plain; c; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-03/msg00251.html (12,573 bytes)
2. [Veritas-bu] Status code 24 on scheduled vault policy (score: 1): Author: rob AT worman DOT org (Rob Worman (home)); Date: Wed, 16 Mar 2005 18:49:32 -0600; sounds like you might have a bad "bpbrmvlt" binary (that's one of the big differences between the execution of a scheduled vault policy and the manual execution of the vault profile. what happens if; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-03/msg00260.html (11,909 bytes)

Current List: 1 - 2
Page: [1]