Yes, you are correct. In the HSM startup you define the volume(s) that you
want and the dumptype(frequency) that you want them to have:
This is for NON-SMS volumes and in this case it's for a z/OS res volume
ADDVOL C24RES /* ADD A VOLUME (PROVIDE SERIAL) */ -
UNIT(3390) /* WITH UNIT TYPE (PROVIDE TYPE) */ -
PRIMARY /* AS A PRIMARY VOLUME THAT IS A */ -
(AUTOBACKUP /* CANDIDATE FOR AUTOBACKUP. */ -
AUTODUMP(FRIDAY) /* DUMPVOLUME AS SPECIFIED */ -
NOAMIG /* CANDIDATE FOR AUTOMIGRATION. */ -
BACKUPDEVICECATEGORY(TAPE) /* BACKED UP TO TAPE. */ -
) /* */ -
THRESHOLD(100 0) /* NO INTERVAL MIGRATION */
And I have FRIDAY defined as:
DEFINE DUMPCLASS(FRIDAY DAY(5) -
RETPD(7) NOAUTOREUSE NORESET -
DATASETRESTORE VTOCCOPIES(4) MINSTACK(4) MAXSTACK(15))
So what ends up happening is that on FRIDAYs, all of the volumes I have defined
this way will be backed up by HSM, I try to keep sets together, meaning volumes
that work together.
Obviously you can change the parms to match what you are expecting to do, but
this way everything is automatically kept under HSM's umbrella, and BACKUP and
DUMP copies of datasets can be used interchangeably.
Otherwise you end up running a batch DF/dss job to do this same thing but
without the benefits of HSM.
If you have questions, feel free to ask.
Brian
On Sun, 2 May 2021 18:07:54 +0000, Gibney, Dave <[email protected]> wrote:
>I've not done this, but, I remember that you can add non-SMS volumes to HSM as
>Primary volumes. I've generally thought that this would be so that you can do
>the kind of processing you are looking for.
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List <[email protected]> On
>> Behalf Of Ed Jaffe
>> Sent: Sunday, May 02, 2021 10:49 AM
>> To: [email protected]
>> Subject: Re: Flashcopy for Non-SMS volume backup?
>>
>> Crickets. Fab. 😕
>>
>> Here's what I'm thinking we should do:
>>
>> Use DSS to periodically create flashcopy backups of our Non-SMS volumes
>> using COPY FULL or COPY TRACKS with FASTREPLICATION and
>> DUMPCONDITIONING. The flashcopy targets would then be dumped using
>> HSM
>> BACKVOL with VOLUMES and DUMP (or perhaps be pre-defined to HSM as
>> PRIMARY volumes for automatic dump processing).
>>
>> Restoration of a volume dumped this way would be done using HSM
>> RECOVER
>> with TOVOLUME, FROMDUMP and TARGETVOLUME potentially followed by
>> DSF
>> REFORMAT to CLIP the restored volume to the right volser, if necessary.
>>
>> What I don't like about this procedure is having to use other utilities
>> (DSS and possibly DSF) independently of HSM to perform the flashcopy and
>> perhaps CLIP after restore, but I can't find a way in HSM to make a
>> flashcopy volume backup occur for other than SMS-Managed volumes. I
>> have
>> done a LOT of reading, but I feel like I must have missed something.
>>
>> I'm curious to learn how other shops handle this.
>>
>> Thanks...
>>
>> On 4/30/2021 4:27 PM, Ed Jaffe wrote:
>> > To all Storage Management Gurus on IBM-MAIN:
>> >
>> > What is the "best practice" procedure for creating a fast-replication
>> > (flashcopy) Non-SMS volume backup?
>> >
>> > FRBACKUP makes it easy for SMS-managed volumes...
>> >
>> > Thanks,
>> >
>> >
>> --
>> Phoenix Software International
>> Edward E. Jaffe
>> 831 Parkview Drive North
>> El Segundo, CA 90245
>> https://urldefense.com/v3/__https://www.phoenixsoftware.com/__;!!JmP
>> EgBY0HMszNaDT!50Az-
>> xBlndXZ4wT_rA8Ezu2fBMg56HLYBIgbq3WLTZrKkp4Mlrdnir4LdX7Hew$
>>
>>
>> --------------------------------------------------------------------------------
>> This e-mail message, including any attachments, appended messages and
>> the
>> information contained therein, is for the sole use of the intended
>> recipient(s). If you are not an intended recipient or have otherwise
>> received this email message in error, any use, dissemination, distribution,
>> review, storage or copying of this e-mail message and the information
>> contained therein is strictly prohibited. If you are not an intended
>> recipient, please contact the sender by reply e-mail and destroy all copies
>> of this email message and do not otherwise utilize or retain this email
>> message or any or all of the information contained therein. Although this
>> email message and any attachments or appended messages are believed to
>> be
>> free of any virus or other defect that might affect any computer system into
>> which it is received and opened, it is the responsibility of the recipient
>> to ensure that it is virus free and no responsibility is accepted by the
>> sender for any loss or damage arising in any way from its opening or use.
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
