- 1. [ADSM-L] DB backup expiration (score: 1)
- Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
- Date: Mon, 1 Aug 2011 16:01:16 -0400
- We have two TSM 6.2.2.0 servers running under mainframe Linux. Both report 'DB Backup Series Expiration Days: 3 Day(s)' when I execute 'query drmstat' commands. One of the systems is configured as a
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-08/msg00009.html (11,625 bytes)
- 2. Re: [ADSM-L] DB backup expiration (score: 1)
- Author: Erwann SIMON <erwann.simon AT FREE DOT FR>
- Date: Mon, 1 Aug 2011 20:17:50 +0000
- Hi Thomas, Virtual volumes are considered "remote" by DRM as soon as they're created, so the expiration of "DB backup series expiration days" is immediatly taken into account whereas "real" volumes (
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-08/msg00010.html (12,631 bytes)
- 3. Re: [ADSM-L] DB backup expiration (score: 1)
- Author: Paul Fielding <paul AT FIELDING DOT CA>
- Date: Mon, 1 Aug 2011 18:46:18 -0600
- Most places I know simply script the del volhost todate=-3 t=dbb and/or t=dbs as appropriate, into their regular daily processing. Indeed as mentioned above, regular database media is not considered
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-08/msg00011.html (13,703 bytes)
This search system is powered by
Namazu