Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Bpend_notify\s+running\s+twice\,\s+multiply\s+streams\s+NOT\s+allowed\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Bpend_notify\s+running\s+twice\,\s+multiply\s+streams\s+NOT\s+allowed\s*$/: 2 ]

Total 2 documents matching your query.

1. [Veritas-bu] Bpend_notify running twice, multiply streams NOT allowed (score: 1): Author: Lynne.Seamans AT millersville DOT edu (Lynne Seamans); Date: Tue, 9 Dec 2003 09:26:50 -0500; We have a policy where bpend_notify sometimes (well, almost all the time, but not quite) runs twice. And the first time is sometimes before the backup is done, which creates havoc with database start; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2003-12/msg00149.html (11,329 bytes)
2. [Veritas-bu] Bpend_notify running twice, multiply streams NOT allowed (score: 1): Author: Mark.Donaldson AT experianems DOT com (Donaldson, Mark); Date: Tue, 9 Dec 2003 10:19:52 -0700; The bpend_notify will run for every stream of a multi-stream backup, this is by design and not a bug (but, boy, is it annoying). You have to write some logic to see if the stream is the *last* stream; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2003-12/msg00159.html (12,217 bytes)

Current List: 1 - 2
Page: [1]