Glenn,
Thank you for your excellent suggestions. We implemented things exactly
your way and we're quite pleased.
My POC did not use incremental flashcopy. We're using it now, based upon
your suggestion, and the result is the controller does a lot less work
-- which is great. The only downside is the surprising inability to
issue SPACEREL on thinly-provisioned volumes in a permanent
relationship. We will wait to see if that becomes an issue over time.
DSS dump conditioning results in no DSF CLIP needed after a full-volume
restore of a z/OS volume. That's a blessing.
We're even using HSM to back up PIT flashcopies of our z/VSE, z/VM and
Linux for Z volumes. In some cases, we're using BACKVOL and in other
cases DSS DUMPing the flashcopy target to zEDC-compressed, SMS-managed
DASD data sets which are then instantly migrated to ML2 tape.
Eventually, we intend to use TCT and cloud for much of this. (I found a
leading cloud provider that charges literally ZERO for unlimited object
storage.)
It sure would be nice if:
a) HSM could perform data set-level recovery from SMS COPYPOOL
full-volume dumps just as it does for other full-volume dumps!
b) HSM could provide FRBACKUP-like processing (i.e., manage flashcopy
"under the covers") for non-SMS managed volumes!
Thanks again for your help!
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
On 5/3/2021 12:45 PM, Glenn Wilcock wrote:
Hey Ed,
Chatted with some DFSMS folks about what you want to do. First, you are
correct. The HSM FR support is only for SMS-managed volumes. It is tightly
integrated with several SMS constructs for managing the volumes and policy.
(In the future, feel free to send me a direct email to save yourself alot of
reading :)
Next, for your scenario, we <believe> that it will work if you do the following:
1) Identify your source to target pairings
2) We HIGHLY recommend that you use FC Incremental because it creates a
persistent relationship between the source and the target. Because the HSM
dump will be done in the standard dump path, it doesn't have the 'smarts' to do
things like withdraw a NOCOPY relationship, etc. Also, more later on why it
will be very useful.
3) Create the FC with DSS and dump conditioning to the target, and with
FCINCREMENTAL
4) I believe that you are all set with adding the FC Target volumes to HSM,
setting up the appropriate dump class, dump cycle, etc and having them picked
up as a part of autodump / dump command.
5) What makes the dump copies fundamentally different from a standard HSM Dump or an
FRBACKUP DUMP - a) DSS is smart enough to know that a FC dump conditioned target
volume is being dumped, so the dump copy that it creates will be written with the
volser of the source volume and will be created as if it came directly from the
source b) HSM is <not> smart enough to know that it is a dump conditioned
volume, so the HSM CDS dump record and LIST output will record it as a dump of the
target, with the FC target volser. Hence, the recommendation for a persistent
relationship between your source and target volumes. Then you can manage the
inconsistency between the HSM dump records and which volume was actually dumped.
6) As you indicate, you can use HSM Recover with TOVOLUME to recover directly
back to the source. Since the dump volume is actually of the source, all
should be well after the recovery ends. The volser will stay the same during
the recovery process since the dump tape has the source volser. We believe
that you shouldn't have to do a clip or anything after the Recovery. All
should be well.
There's a lot going on here. If you'd like to set up call to discuss, reach
out and I can setup a call with all of the right SMEs to walk you through this.
--------------------------------------------------------------------------------
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
