The question of how much DASD you need strikes me as a can of worms. I doubt that we are unique in being legally required to keep 'some data' for the life of the corporation. Even if it's not a substantial percentage of the total, it's non-trivial and means that forever you will need to add more and more acreage to the DASD farm even if your 'live data' needs remain static--an unoptimistic forecast at best.
I understand the short-term appeal of eliminating an entire peripheral component. I also understand the long-term agony of being required by a judge to cough up data that you can no longer retrieve. The rosy take is that your head will plop in the guillotine basket alongside your CEO's. ;-) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Tuesday, May 30, 2017 11:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: HSM Backup to Disk Note: We have found using a VTS (Virtual Tape System) - any hardware vendor - works very well. The device is a little DASD farm on the inside and our BACKUPs and MIGRATION datasets are super-fast to retrieve Expansion on point 2: You may need more DASD than you did TAPE. I think with TAPE the BACKUP datasets are stacked. When you write to DASD - I think they become individual dataset and may require more room Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Tuesday, May 30, 2017 11:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM Backup to Disk > > So my thoughts are > > 1) Yes you can do this > 2) You may need more dasd that tape > 3) You will be tying up DASD for a long time for backups. > 4) You will need to determine how long your longest Backup dataset > is held for. > > An HSM Backup is used to recover files. So if this is part of a DR > process, then you need to account for that policy as well. > > Also determine how is your HSM BACKUP datasets sent to a DR site (if > they are > sent) and identify that as part of the DASD requirements. > > Lizette > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Robert Heffner > > Sent: Tuesday, May 30, 2017 10:03 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: HSM Backup to Disk > > > > First off, I would like to say I am not an HSM expert, I am > > supporting HSM while a coworker is on medical leave. The company is > > looking to eliminate tape from the environment and I would like to > > know the best (or perhaps only) way to move HSM automatic backup from tape > > to disk. > > My feeling is we need to obtain the disk space needed well ahead of > > the elimination of tape, then set backups to go to disk instead of > > tape, and just let the tape backups drop off through attrition. > > There are some backups that we keep up to 200 days. Any other > > ideas? This is > z/OS 2.2. > > Thanks -- Bob Heffner ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
