- 1. Expiration Question on 5.1.6.4 (score: 1)
- Author: Mahesh Tailor <MTailor AT CARILION DOT COM>
- Date: Mon, 28 Jul 2003 08:43:18 -0400
- Hello, TSM: 5.1.6.4 w/DRM enabled AIX: 4.3.3.10 I having been looking at the completion of my expiration processes for the last 15 days and I see, for example, the following: 07/27/03 15:15:01 ANR201
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00789.html (12,219 bytes)
- 2. Re: Expiration Question on 5.1.6.4 (score: 1)
- Author: Richard Sims <rbs AT BU DOT EDU>
- Date: Mon, 28 Jul 2003 09:04:57 -0400
- ... You're meddling with DRM. DRM is a regimen of its own. Let it be. See Admin Ref manual, doc. of the DELete VOLHistory command, Note 5.
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00790.html (10,889 bytes)
- 3. Re: Expiration Question on 5.1.6.4 (score: 1)
- Author: Mike Cantrell <Mike_Cantrell AT SAKSINC DOT COM>
- Date: Mon, 28 Jul 2003 10:47:19 -0500
- Hello You need to use SET DRMDBBACKUPEXPIREDAYS, instead of del volhist t=dbb. This is an excert from help del volhist. 5. For users of DRM, the database backup expiration should be controlled with t
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00794.html (13,151 bytes)
- 4. Re: Expiration Question on 5.1.6.4 (score: 1)
- Author: Mahesh Tailor <MTailor AT CARILION DOT COM>
- Date: Mon, 28 Jul 2003 12:51:07 -0400
- Thanks for the responses, Mike and Richard. As I mentioned DRMDBBACKUPEXPIREDAYS is set to 5-days. [From my previous email] DRM expiration is set as follows: DB Backup Series Expiration Days: 5 Day(s
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00795.html (13,512 bytes)
This search system is powered by
Namazu