Re: Backing up CDS's to DASD
Gil, That was probably written 20 years ago when a volume meant a SLED and it would have been prudent to protect yourself against a disk failure. With RAID the need for separate volumes for these backups is debatable. To get the same hardware separation with RAID you need a map of Device Number and Array Group to figure out which volumes share common disk drives. With parity and dynamic sparing protection you would probably be making your life way more complex than it needs to be. I would not blindly follow every recommendation like this from IBM. Ron > -Original Message- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > Gilbert Cardenas > Sent: Wednesday, August 12, 2009 8:27 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] Backing up CDS's to DASD > > Thanks for the info Dave. The section I was reading was in the z/OS > 1.9 Admin Guide Chapter 12 page 474 that says: > > If you decide to back up the control data sets and journal data set to > DASD, you must preallocate the data sets. Also, allocate the different > versions of the backup data sets on different volumes. This better > ensures that you can recover your backup versions. > > What you say makes more sense than the above when using SMS. > > Thanks again, > Gil. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Backing up CDS's to DASD
Thanks for the info Dave. The section I was reading was in the z/OS 1.9 Admin Guide Chapter 12 page 474 that says: If you decide to back up the control data sets and journal data set to DASD, you must preallocate the data sets. Also, allocate the different versions of the backup data sets on different volumes. This better ensures that you can recover your backup versions. What you say makes more sense than the above when using SMS. Thanks again, Gil. On Wed, 12 Aug 2009 11:13:53 -0400, O'Brien, David W. (NIH/CIT) [C] wrote: >Gil, > >The manual says to allocate the backups on volumes other than the ones containing the CDSs being backed up. > >Thank You, >Dave O'Brien >NIH Contractor > >From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of O'Brien, David W. (NIH/CIT) [C] >Sent: Wednesday, August 12, 2009 10:55 AM >To: IBM-MAIN@bama.ua.edu >Subject: Re: Backing up CDS's to DASD > >Gil, > >The requirement to separate by volume refers to the BCDS, MCDS and OCDS not their Backups. > >The jcl to allocate the backup datasets is in Sys1.samplib(ARCSTRST) look for ALLOCBK1 > >Thank You, >Dave O'Brien >NIH Contractor > >From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Gilbert Cardenas [gilbertcarde...@grocerybiz.com] >Sent: Wednesday, August 12, 2009 10:51 AM >To: IBM-MAIN@bama.ua.edu >Subject: Backing up CDS's to DASD > >Hello all, I am trying to move the CDS backups currently from tape >using HSM as the datamover and noparallel to disk using DSS and >parallel. > >The manual states that I have to preallocate the new dasd backup >datasets but thats all, so do I use the same dcb characteristics as the >current tape datasets...RECFM=VBS LRECL=32760 BLKSIZE=32760? > >I am also again confused by the manual. It makes a case for SMS >managing the backup datasets so that you can use concurrent copy but >then later on it says that you should allocate the different versions of >the backup data sets on different volumes for recoverability purposes. > >That doesn't really make sense because if they are SMS managed I >have no control where the allocation goes. And I do not really want to >create 4 different storage groups/classes just to make sure the >datasets do not go to the same volume. > >Can someone shed some light on these questions? > >Thanks, >Gil. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: GET IBM- MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: GET IBM- MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: GET IBM- MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Backing up CDS's to DASD
Gil, The manual says to allocate the backups on volumes other than the ones containing the CDSs being backed up. Thank You, Dave O'Brien NIH Contractor From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Wednesday, August 12, 2009 10:55 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Backing up CDS's to DASD Gil, The requirement to separate by volume refers to the BCDS, MCDS and OCDS not their Backups. The jcl to allocate the backup datasets is in Sys1.samplib(ARCSTRST) look for ALLOCBK1 Thank You, Dave O'Brien NIH Contractor From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Gilbert Cardenas [gilbertcarde...@grocerybiz.com] Sent: Wednesday, August 12, 2009 10:51 AM To: IBM-MAIN@bama.ua.edu Subject: Backing up CDS's to DASD Hello all, I am trying to move the CDS backups currently from tape using HSM as the datamover and noparallel to disk using DSS and parallel. The manual states that I have to preallocate the new dasd backup datasets but thats all, so do I use the same dcb characteristics as the current tape datasets...RECFM=VBS LRECL=32760 BLKSIZE=32760? I am also again confused by the manual. It makes a case for SMS managing the backup datasets so that you can use concurrent copy but then later on it says that you should allocate the different versions of the backup data sets on different volumes for recoverability purposes. That doesn't really make sense because if they are SMS managed I have no control where the allocation goes. And I do not really want to create 4 different storage groups/classes just to make sure the datasets do not go to the same volume. Can someone shed some light on these questions? Thanks, Gil. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Backing up CDS's to DASD
Gil, The requirement to separate by volume refers to the BCDS, MCDS and OCDS not their Backups. The jcl to allocate the backup datasets is in Sys1.samplib(ARCSTRST) look for ALLOCBK1 Thank You, Dave O'Brien NIH Contractor From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Gilbert Cardenas [gilbertcarde...@grocerybiz.com] Sent: Wednesday, August 12, 2009 10:51 AM To: IBM-MAIN@bama.ua.edu Subject: Backing up CDS's to DASD Hello all, I am trying to move the CDS backups currently from tape using HSM as the datamover and noparallel to disk using DSS and parallel. The manual states that I have to preallocate the new dasd backup datasets but thats all, so do I use the same dcb characteristics as the current tape datasets...RECFM=VBS LRECL=32760 BLKSIZE=32760? I am also again confused by the manual. It makes a case for SMS managing the backup datasets so that you can use concurrent copy but then later on it says that you should allocate the different versions of the backup data sets on different volumes for recoverability purposes. That doesn't really make sense because if they are SMS managed I have no control where the allocation goes. And I do not really want to create 4 different storage groups/classes just to make sure the datasets do not go to the same volume. Can someone shed some light on these questions? Thanks, Gil. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Backing up CDS's to DASD
Hello all, I am trying to move the CDS backups currently from tape using HSM as the datamover and noparallel to disk using DSS and parallel. The manual states that I have to preallocate the new dasd backup datasets but thats all, so do I use the same dcb characteristics as the current tape datasets...RECFM=VBS LRECL=32760 BLKSIZE=32760? I am also again confused by the manual. It makes a case for SMS managing the backup datasets so that you can use concurrent copy but then later on it says that you should allocate the different versions of the backup data sets on different volumes for recoverability purposes. That doesn't really make sense because if they are SMS managed I have no control where the allocation goes. And I do not really want to create 4 different storage groups/classes just to make sure the datasets do not go to the same volume. Can someone shed some light on these questions? Thanks, Gil. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
