Interfamily Connectivity

Transcription

1 Interfamily Connectivity SRDF Interfamily Connectivity Information REV 01 May 2017 This document defines the versions of HYPERMAX OS and Enginuity that can make up valid SRDF replication and SRDF/Metro configurations. In addition, there is information on the versions that can participate in Non-Disruptive Migration (NDM). Introduction... 2 SRDF Remote Replication...3 SRDF/Metro NDM...13 Requirements for performing system upgrades...14

2 Interfamily Connectivity Introduction The versions of HYPERMAX OS and Enginuity that participate in an SRDF remote replication configuration, a SRDF/Metro high-availability configuration, or a Non- Disruptive Migration (NDM) configuration need to be compatible. This document contains advice on which versions of HYPERMAX OS and Enginuity can participate in those configurations. Note This document covers interfamily connectivity for major releases of HYPERMAX OS and Enginuity and for their service packs. For the latest connectivity information including interim releases and information on any hot fixes or epacks that are required, refer to Knowledgebase article Related documents The following VMAX All Flash, VMAX3, and VMAX documents contain information on SRDF. VMAX All Flash and VMAX3 series: EMC VMAX3 Family Product Guide for VMAX 100K, VMAX 200K, VMAX 400K with HYPERMAX OS EMC VMAX All Flash Product Guide for VMAX 250F, 450F, 850F, 950F with HYPERMAX OS VMAX series: Symmetrix Remote Data Facility (SRDF) Product Guide All systems: FBA environments: EMC Solutions Enabler SRDF Family CLI User Guide CKD environments: EMC Mainframe Enablers SRDF Host Component for z/os Product Guide 2 SRDF Interfamily Connectivity

3 Interfamily Connectivity Information SRDF Remote Replication Connectivity tables Use this section to determine valid SRDF replication configurations and understand any limitations associated with those configurations. A SRDF configuration consists of one or more pairs of storage arrays. One array is the source, and is known as the R1 side. The other array is the target that receives data from the source array, and is known as the side: FBA These tables show the valid combinations of HYPERMAX OS or Enginuity that can be a SRDF pair. Use the table for appropriate the device emulation in use: FBA or CKD. Table 1 FBA interfamily connectivity When R1 runs HYPERMAX OS can run or later with epack (if the Service Processor runs Windows 7). Otherwise with epack or later with epack (if the Service Processor runs Windows 7). Otherwise with epack with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack (if the Service Processor runs Windows 7). Otherwise with epack or later with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack SRDF Remote Replication 3

4 Interfamily Connectivity Table 1 FBA interfamily connectivity (continued) When R1 runs can run or later with epack , with epack containing fixes to support N-x connectivity, or later In this case, requires an epack containing fixes to support N-x connectivity with epack containing N-x fixes, or later or later or later with a Proactive epack, or later In this case, requires an epack or later with a Proactive epack, or later or later or later or later 4 SRDF Interfamily Connectivity

5 Interfamily Connectivity Information Table 1 FBA interfamily connectivity (continued) When R1 runs can run or later or later with Proactive epack or later CKD Table 2 CKD interfamily connectivity When R1 runs can run or later HYPERMAX OS VMAX 40K systems: with epack (if the Service Processor runs Windows 7). Otherwise with epack. All other VMAX systems: with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack (if the Service Processor runs Windows 7). Otherwise with epack with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack (if the Service Processor runs Windows 7). Otherwise, with epack or later with epack Connectivity tables 5

6 Interfamily Connectivity Table 2 CKD interfamily connectivity (continued) When R1 runs can run or later with epack or later or later or later or later or later or later with epack 6 SRDF Interfamily Connectivity

7 Interfamily Connectivity Information How to determine valid SRDF configurations 2 site These procedures show how to use Table 1 on page 3 and Table 2 on page 5 to determine valid configurations for 2-site and 3-site SRDF. Follow the appropriate procedure. Procedure 1. Locate the version of HYPERMAX OS or Enginuity that the R1 side runs in the When the R1 runs column. 2. The corresponding entries in the can run column show the versions of HYPERMAX OS and Enginuity that can be on the side. Choose one of those versions. For example, the R1 side in FBA configuration runs HYPERMAX OS From Table 1 on page 3 the side can run HYPERMAX OS or later, Enginuity with an epack, or Enginuity with an epack. The side can also run with an epack or with an epack. 3-site concurrent Procedure 1. Locate the version of HYPERMAX OS or Enginuity that the R11 site runs in the When R1 runs column. 2. The corresponding entries in the can run column show the versions of HYPERMAX OS and Enginuity that can be on the sites. Choose one of those versions for each side. The two sides can run different versions of HYPERMAX OS and Enginuity. For example, the R11 side in a FBA configuration runs HYPERMAX OS From Table 1 on page 3 each side can run HYPERMAX OS or later, or Enginuity with an epack. How to determine valid SRDF configurations 7

8 Interfamily Connectivity 3-site cascaded Procedure 1. Locate the version of HYPERMAX OS or Enginuity that the R1 side runs in the When R1 runs column. 2. The corresponding entries in the can run column show the versions of HYPERMAX OS and Enginuty that can run on the 1 side. Choose one of those versions. 3. Locate the chosen 1 version of HYPERMAX OS or Enginuity in the When R1 runs column. 4. The corresponding entries in the can run column show the versions of HYPERMAX OS and Enginuity that can be on the side. Choose one of those versions. For example, the R1 side in a CKD environment runs HYPERMAX OS Table 2 on page 5 shows that the 1 side can run HYPERMAX OS or later, or Enginuity with an epack. Assume that the 1 side runs HYPERMAX OS Locating the row with that version in the When R1 runs column of Table 2 on page 5 shows that the side can run HYPERMAX OS or later, or Enginuity with an epack. 8 SRDF Interfamily Connectivity

9 Interfamily Connectivity Information Limitations There are some limitations to SRDF communications in these environments: 2-site Cascaded Concurrent 2-site R1 and RecoverPoint CDP co-existence is not supported on an array running Enginuity 5876 when the device is on an array running HYPERMAX OS If the SRDF R1 device is tagged as a RecoverPoint CDP source device, disable RecoverPoint consistency before performing any SRDF operations that may cause data to flow from the device to the R1 device. There is no support for FAST coordination propagation between a VMAX3 array running HYPERMAX OS 5977 and Enginuity An update operation on the source (R1) side after a failover where the target () side is still operational to the hosts is not supported when the R1 side is a VMAX 10K, 20K, or 40K array running Enginuity Remote Pair Flashcopy for CKD devices is not supported between a VMAX3 array running HYPERMAX OS 5977 and an array running Enginuity Thick-to-thin connectivity requires at least Enginuity on VMAX arrays. In thin-to-thick and thick-to-thin configurations of arrays running Enginuity 5876 and Enginuity 5773, the thick devices reside on the array running Enginuity In configurations running Enginuity 5876 and HYPERMAX OS 5977, the thick devices reside on the array running Enginuity Concurrent In SRDF/A mode, you cannot move dynamic SRDF devices between groups. Arrays running Enginuity 5876 with CKD zboost require additional fixes to be able to connect to HYPERMAX OS and Contact your Dell EMC representative for more information. Cascaded When a VMAX 10K is part of a configuration, it must run Enginuity to connect to thick FBA devices on: DMX array running Enginuity 5773 VMAX 40K, VMAX 20K, or VMAX arrays running or later When the 1 site is a VMAX 10K it must run Enginuity or later. Limitations 9

10 Interfamily Connectivity SRDF/Metro Use this section to determine valid SRDF/Metro configurations. Multi-Path Cluster Read/Write Read/Write Read/Write Read/Write R1 SRDF links R1 SRDF links Site A Site B Site A Site B Connectivity This table shows the valid configurations for SRDF/Metro. Table 3 SRDF/Metro connectivity When one side runs HYPERMAX OS The other side runs or later or later or later or later or later Limitations SRDF/Metro does not support: CKD device pairs ProtectPoint CloudArray Mobility Safe ID with ALUA Microsoft ODX Microsoft Cluster with non-uniform connection (without cross-connects) SRDF with Consistency with ODX FCoE front-end capabilities 10 SRDF Interfamily Connectivity

11 Interfamily Connectivity Information Active is the only valid SRDF mode. You cannot change this mode once the device pairs are in an SRDF/Metro configuration. You cannot change the SRDF Consistency state once it is enabled for all SRDF devices. Consistency Group (CG) SRDF control and set operations are allowed on one SRDF group at a time. VAAI commands are available with HYPERMAX OS and later except for xcopy/odx. SCSI 2 and 3 reservations are available on HYPERMAX OS and later only. Array witness If one or more device pairs become Not Ready or connectivity is lost between the arrays, SRDF/Metro must decide which side of the pair remains accessible to the hosts. One of the available methods is the Array Witness which uses a third array to choose the side that remains available. SRDF/Metro Witness array: SRDF Witness group SRDF Witness group R1 SRDF links R1 array array The version of HYPERMAX OS or Enginuity that runs on the witness array must be compatible with that running on each SRDF/Metro array. Use Table 1 on page 3 to determine the compatibility for the systems that make up your SRDF/Metro pair. For example, the R1 and sides both run HYPERMAX OS Table 1 on page 3 shows that the Array Witness can run HYPERMAX OS or later, or Enginuity , with an epack. Array witness 11

12 Interfamily Connectivity Disaster recovery In HYPERMAX OS or later, you can attach disaster recovery arrays to a SRDF/Metro configuration. Either or both sides of the configuration can replicate to another array: Single-sided replication SRDF/Metro SRDF/Metro R11 R1 1 Site A Site B Site A Site B SRDF/A or Adaptive Copy Disk SRDF/A or Adaptive Copy Disk Site C Site C Double-sided replication SRDF/Metro SRDF/Metro R11 1 R11 1 Site A SRDF/A or Adaptive Copy Disk Site B SRDF/A or Adaptive Copy Disk Site A SRDF/A or Adaptive Copy Disk Site B SRDF/A or Adaptive Copy Disk Site C Site D Site C The version of HYPERMAX OS or Enginuity that runs on the disaster recovery array or arrays must be compatible with that running on the SRDF/Metro array it is connected to. Use the Table 1 on page 3 to determine the compatibility for the systems that make up your SRDF/Metro configuration. For example, a double-sided configuration replicates the R11 and 1 sides to a shared, third array. Also, both the R11 and 1 SRDF/Metro partners run HYPERMAX OS Table 1 on page 3 shows that the disaster recovery array can run HYPERMAX OS or later, Enginuity with an epack, or Enginuity with an epack. 12 SRDF Interfamily Connectivity

13 Interfamily Connectivity Information NDM NDM uses SRDF to migrate data from an array that runs Enginuity 5876 to another that runs HYPERMAX OS or later. NDM does not affect the operation of the application host, allowing applications to continue to run while the migration takes place. Once the migration is complete, the application host switches to using the array that runs HYPERMAX OS. A typical use of NDM is when a data center replaces an existing array with a new one. This table shows the versions of HYPERMAX OS 5977 and Enginuity 5876 that are compatible for use in NDM operations. Table 4 NDM compatibility HYPERMAX OS version HYPERMAX OS Enginuity version with epack (if the Service Processor runs Windows 7). Otherwise with epack with epack (if the Service Processor runs Windows 7). Otherwise with epack with epack (if the Service Processor runs Windows 7). Otherwise with epack with epack with epack (if the Service Processor runs Windows 7). Otherwise with epack. Refer to the host support matrix for information on the hosts that are supported for these combinations of operating environment. For disaster recovery (DR) purposes, either or both arrays in an NDM configuration can be connected to additional arrays using SRDF. The rules for SRDF connectivity between a NDM array and a DR array are the same as a regular 2-site SRDF replication configuration. When both sides of the NDM configuration are connected to other arrays, treat each side as a separate, 2-site configuration. NDM 13

14 Interfamily Connectivity Requirements for performing system upgrades When upgrading HYPERMAX OS in any SRDF configuration, ensure that the arrays remain in a supported scenario throughout the upgrade process. For example, in a 2- site configuration upgrading Site A to or later leaving Site B running is not supported. To avoid unsupported configurations, use an upgrade path similar to the following example of a 3-site SRDF configuration. Initially, all sites are running and the aim is to upgrade to Upgrade Site A to Upgrade Site B to Upgrade Site C to Upgrade Site A to Upgrade Site B to Upgrade Site C to SRDF Interfamily Connectivity

15 Interfamily Connectivity Information Copyright 2017 Dell Inc. or its subsidiaries. All rights reserved. Published May 2017 Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. Requirements for performing system upgrades 15

16 Copyright 2015 EMC Corporation. All rights reserved. Published in USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support (