Gadi Ben-Avi wrote: >....What we want to do: >Allow the computers in the production site to use the DS8884 >in the DR site. This is to allow us to continue working at the >production site if there is a catastrophic problem with the >DS8884 in the production site. When I spoke to our Storage >salesperson he told us that HyperSwap is the direction to go. >So I have some questions: >Is HyperSwap the right solution?
The steps Radoslaw outlines are the rough prerequisites for HyperSwap, but it doesn't make much sense to me to make the effort then not enable HyperSwap. Here's the basic question to answer, though: considering your most demanding (most important) business service, end-to-end, what are your Recovery Time Objective (RTO) and Recovery Point Objective (RPO)? Ultimately your organization's top management answers this question, perhaps at the direction of regulators. And this is always about assuring end user service delivery. It doesn't matter if your IBM Z is deployed in a RTO=0/RPO=0 way if nobody can reach it when there's a disaster because there's one much less reliable server sitting in front that's supposed to be doing something and isn't. Fundamentally your RTO/RPO are constrained per the weakest link(s) in service delivery. Assuming HyperSwap is helpful or required to achieve your DR and HA objectives, there are several z/OS HyperSwap deployment variations, as this recent redbook explains: https://www.redbooks.ibm.com/redbooks/pdfs/sg248431.pdf Is this the redbook that you already checked? One area where I might quibble with the redbook is that it seems to imply Parallel Sysplex is a prerequisite for HyperSwap. While Parallel Sysplexes are common and might also be helpful or required to achieve your RTO/RPO, they're not strictly necessary for HyperSwap deployments. - - - - - - - - - - Timothy Sipples I.T. Architect Executive Digital Asset & Other Industry Solutions IBM Z & LinuxONE - - - - - - - - - - E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
