Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Closing\s+windows\s+$status\s+196$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Closing\s+windows\s+$status\s+196$\s*$/: 3 ]

Total 3 documents matching your query.

1. [Veritas-bu] Closing windows (status 196) (score: 1): Author: AhrensJ AT psi DOT ca (AhrensJ AT psi DOT ca); Date: Mon, 19 Mar 2001 09:30:58 -0500; This weekend, I had a very large number of clients fail with status 196 (Closing window) I know what this means (the job was in the queue but not running yet when the backup window closed) but my que; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-03/msg00287.html (11,428 bytes)
2. [Veritas-bu] Closing windows (status 196) (score: 1): Author: luis AT bellglobal DOT com (Lou Costabile); Date: Mon, 19 Mar 2001 09:53:16 -0500 (EST); There's probably an easier way, with a utility that automates what I'm about to tell you, but... /usr/openv/netbackup/logs/bptm view log.mmddyy You'll see the events, eg. 00:33:27 [10243] <2> bptm: I; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-03/msg00289.html (12,448 bytes)
3. [Veritas-bu] Closing windows (status 196) (score: 1): Author: dfdwyer AT tecoenergy DOT com (Dennis Dwyer); Date: Mon, 19 Mar 2001 09:55:57 -0500; Been there and done that for 196 servers using the activity monitor. It is a hassle to use the activity monitor to do all that so I would be interested in the answer as well. To answer your question; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-03/msg00290.html (12,901 bytes)

Current List: 1 - 3
Page: [1]