On Tue, 26 Aug 2014 00:18:21 -0700, Ron Hawkins <[email protected]> wrote:
>A three tier strategy using HDD or SSD for Tier 1, Nearline SAS >for ML2, and virtualized Brand-X midrange storage for Tier 3 presents a new >paradigm for archiving inactive and dormant data sets, including back-ups, >that I believe over time can displace DFSMShsm altogether. > How does that present the location of the data to z/OS? You just have one giant pool of VOLSERs, and once a dataset is written to a DASD volser, it's z/OS percived location never changes, but the hardware is busy moving virtual tracks around amongst T1, T2 and T3 as it sees fit? That's an intriguing idea, I'd be all for getting rid of HSM. What could you use for managing retention and retrieval of application backups and archives? Dana ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
