Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+bpexpdate\s+not\s+working\s+properly\s*$/: 4 ]

Total 4 documents matching your query.

1. [Veritas-bu] bpexpdate not working properly (score: 1)
Author: egml5 egml5 AT hotmail DOT com
Date: Fri, 1 Dec 2000 11:28:34 -0500
This particular environment is Veritas DataCenter 3.4 for NT. I am using bpexpdate.exe on an NT Master/Media server. The command appears to run properly, but when you look at the tape in the media ma
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2000-12/msg00008.html (10,844 bytes)

2. [Veritas-bu] bpexpdate not working properly (score: 1)
Author: David A. Chapa david AT datastaff DOT com
Date: Fri, 1 Dec 2000 10:50:17 -0600
Two different processes. bpexpdate affects the mediaDB while the GUI will affect the volume manager DB, they are two separate processes. What is the end result you are attempting to achieve? David Da
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2000-12/msg00013.html (12,210 bytes)

3. [Veritas-bu] bpexpdate not working properly (score: 1)
Author: Bob Bakh bbakh AT veritas DOT com
Date: Fri, 1 Dec 2000 09:01:36 -0800
The media manager GUI expiration date has nothing to do with image expirations. This is a date you set when creating the media entry saying that I want the tape used for X months. To check the new ex
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2000-12/msg00016.html (11,709 bytes)

4. [Veritas-bu] bpexpdate not working properly (score: 1)
Author: egml5 egml5 AT hotmail DOT com
Date: Fri, 1 Dec 2000 15:14:11 -0500
I think we wrongly assumed that performing a bpexpdate on the tape should show up in the media manager as an expiration date for the media id. I believe by performing a bpexpdate -ev "mediaid" that w
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2000-12/msg00021.html (13,878 bytes)


This search system is powered by Namazu