manualshive.com logo in svg

Dell EMC VMAX, Configuration And Best Practices Technical Notes

Share
Download
Dell EMC VMAX Configuration And Best Practices Technical Notes Download Page 36

36 

 

The revert operation may take some time to run.  As the revert is running, the host will discover that the paths to the source array are 
active again. This is monitored by the VMAX, which will wait for the rediscovery before proceeding. 

C:\>symdm cancel -sid 0129 -sg lcseb246_sg -revert -nop 
  
A DM 'Cancel Revert' operation is 
in progress for storage group 'lcseb246_sg'. Please wait... 
  
    Analyze Configuration..........................................Started. 
      Source SID:000195703184 
      Target SID:000197800129 
    Analyze Configuration..........................................Done. 
    Revert Data Replication........................................Started. 
    Revert Data Replication........................................In Progress. 
    Revert Data Replication........................................Done. 
    Remove Masking View(s) on Target...............................Started. 
    Remove Masking View(s) on Target...............................In Progress. 
    Remove Masking View(s) on Target...............................Done. 
    Remove Data Replication........................................Started. 
    Remove Data Replication........................................Done. 
    Remove Port Group(s) on Target.................................Started. 
    Remove Port Group(s) on Target.................................Done. 
    Remove Initiator Group(s) on Target............................Started 
    Remove Initiator Group(s) on Target............................Done. 
    Remove Duplicate Device(s) on Target...........................Started. 
    Wait for deallocation to complete..............................Started. 
    Wait for deallocation to complete..............................Done. 
    Remove Duplicate Device(s) on Target...........................In Progress. 
    Remove Duplicate Device(s) on Target...........................Done. 
    Remove Storage Group(s) on Target..............................Started. 
    Remove Storage Group(s) on Target..............................Done. 
  
The DM 'Cancel Revert' operation successfully executed for 
storage group 'lcseb246_sg'. 

After a revert operation, the state of the devices and the systems are the same as they were prior to the create operation. 

 

Note: Following the cancel -revert operation, the host paths to the target array are no longer available. The paths to 
the source array should be returned to the original configuration to avoid Data Unavailability. A host HBA rescan should 
be undertaken to ensure application stability. Note: The revert operation may take some time to complete. The “Revert 
Data Replication” step will repeat and remain “In Progress” until the step is complete. However the application will 
immediately be reverted back to operating on the source array. The length of the revert task is based around the time 
the target array takes to deallocate the target devices and clean up after the cancelled migration. 

 

 

 

 

 

 

 

Summary of Contents for VMAX

Page 1: ...e complexity and size of very large storage environments makes planning for scheduling and executing migrations extremely difficult Migrations also often involve applications that cannot be taken offline even briefly for cutover to a new storage array Dell EMC s VMAX Non Disruptive Migration or NDM allows customers to perform online data migrations that are simple as well as completely non disrupt...

Page 2: ...ll Inc or its subsidiaries All Rights Reserved Dell EMC and other trademarks are trademarks of Dell Inc or its subsidiaries Other trademarks may be trademarks of their respective owners Reference Number H15464 2 ...

Page 3: ...SESSIONS 16 PERFORM A HOST RESCAN 19 CUTOVERREADY AND PASSTHROUGH MODE 19 LIST THE NDM SESSIONS 21 EXAMINE THE DEVICE PAIRING AND IDENTITIES FOLLOWING A CREATE 25 CANCEL A MIGRATION 28 PERFORM A CUTOVER TO THE TARGET ARRAY 29 EXAMINE THE DEVICE IDENTITIES FOLLOWING A CUTOVER 34 REVERT TO THE SOURCE ARRAY 35 COMMIT A MIGRATION 37 PERFORM A HOST RESCAN 38 COMPARE THE PRE AND POST DEVICE IDENTITIES F...

Page 4: ...T ARRAY 77 APPENDIX A HOST MULTIPATHING SOFTWARE NOTES AND SETTINGS 79 AIX NATIVE MULTI PATHING SOFTWARE 79 LINUX NATIVE MULTI PATHING SOFTWARE DEVICE MAPPER 79 POWERPATH VERSION 5 7 AND ABOVE 79 POWERPATH WITH SOLARIS 79 WINDOWS 2012 WITH MPIO 80 VERITAS DYNAMIC MULTI PATHING 80 ESXI WITH NATIVE MULTI PATHING 80 APPENDIX B AIX GPFS ORACLE RAC POWERHA AND POWERPATH WITH NDM 80 ...

Page 5: ...solutions and planning for and implementing migrations to VMAX3 or VMAX All Flash arrays Please ensure you are working off the latest version of this document as there are frequent updates made The latest version can always be found here https www emc com collateral technical documentation h15464 vmax non disruptive migration pdf NON DISRUPTIVE MIGRATION OVERVIEW Non Disruptive Data Migration NDM ...

Page 6: ...6 Figure 1 NDM Overview ...

Page 7: ...t array a commit operation is performed During a commit operation Solutions Enabler completes the migration by releasing temporary resources allocated to perform the migration permanently disabling access to the source devices and assigning the target device ID to the source devices Environment Remove This is performed after all migrations have been completed to remove the migration environment Th...

Page 8: ...synchronize before the Commit so that DR is maintained throughout the migration SRDF can also be setup in the CutoverNoSync state which is reached when the sync command is used to stop replication For local Snap VX sessions running against the source volumes existing session on the source array can continue as normal during the migration and new sessions can also be created at the same time that t...

Page 9: ...DF group Note The NDM RDF group should not be removed or relabeled Doing either will cause NDM operations to fail Figure 2 NDM RDF Group SETTING UP MULTIPE NDM RELATIONSHIPS Multiple environment setup operations can be performed for a single source array provided that a different target array is specified for each migration environment All NDM RDF groups on a source or target array can be in use s...

Page 10: ...e permitted A SG will not be able to be migrated using NDM if it contains devices that have been added to a second SG that belongs to a masking view Multiple masking views on the SG using the same IG are not allowed unless PGs on the target array already exist for each view and the ports in the PGs are selected to avoid duplicate host paths Only parent SGs and standalone SGs with masking views can...

Page 11: ...e following minimum code levels are required Vmax with Enginuity 5876 309 xxx Fix 90270 Epack VMAX3 or All Flash with HYPERMAX 0S 5977 Q2 2017 Release Unisphere 8 4 Solutions Enabler 8 4 or later CONFIGURATION REQUIREMENTS AND PREREQUISITES Most of the steps for configuring and un configuring NDM is done automatically using the environment setup and remove commands Prior to running the setup the f...

Page 12: ... supported host operating systems multipathing software and cluster software can be found at the E Lab Navigator ELN on Dell EMC s support site below https elabnavigator emc com eln elnhome Please ensure that the environment you are planning to migrate has a match in the support matrix prior to starting the migration The E Lab Advisor ELA application available at the weblink below provides a way f...

Page 13: ...the Solutions Enabler host is directly attached to both This is not required for NDM operations Only the host being migrated is required to be directly attached to both arrays Note In the lab environment used here the Solutions Enabler commands are run from the host that is being migrated That is acceptable for non production environments but it is not recommended for production hosts The SE or Un...

Page 14: ...000 5760 PHYSICALDRIVE10 GK EMC SYMMETRIX 5977 2900001000 5760 Note Using the native parameter with the inq utility will allow the user to display native WWNs of specific devices These devices are in a storage group SG called lcseb246_sg C symaccess show lcseb246_sg type storage sid 84 Symmetrix ID 000195703184 Storage Group Name lcseb246_sg Last update time 10 39 08 AM on Fri May 27 2016 Group la...

Page 15: ...e prerequisites the application host or cluster is zoned to the target array FA ports The ports that the target devices will be masked to is determined automatically by NDM based on where the host HBAs are zoned Note Workload Planner WLP is a Unisphere utility that can be used to determine the ideal target ports to use for an NDM migration If WLP is used it must be run from a control host that has...

Page 16: ...re the migration sessions C symdm create src_sid 3184 tgt_sid 0129 sg lcseb246_sg validate nop A DM Validate Create operation is in progress for storage group lcseb246_sg Please wait Analyze Configuration Validated Create Storage Group s on Target Validated Duplicate Device s on Target Validated Create Initiator Group s on Target Validated Create Port Group s on Target Validated Create Masking Vie...

Page 17: ...uration Done Create Storage Group s on Target Started Create Storage Group s on Target Done Duplicate Device s on Target Started Duplicate Device s on Target Done Create Initiator Group s on Target Started Create Initiator Group s on Target Done Create Port Group s on Target Started Create Port Group s on Target Done Setup Data Replication Started Setup Data Replication In Progress Setup Data Repl...

Page 18: ...195703184 Storage Group lcseb246_sg Total Source Target Capacity Done Array Array State GB 000195703184 000197800129 Created 200 0 N A Note During an NDM migration the source of the migration will be an R2 or an R21 device if there is existing SRDF DR replication from the source device and the target will be an R1 device This is different than basic SRDF operations and is required to allow DR prot...

Page 19: ... read from either the source or target array Any write that in sent to the target array will be sent across the SRDF link and serviced by the source array No data will be kept on the target array while in a CutoverReady state The CutoverReady state is a transitional state The devices should only be in a CutoverReady state and using pass through mode for as long as it takes to check that the Create...

Page 20: ...FA 1d 61 active alive 0 0 2 port2 path0 tgt5 lun2 c2t5d2 FA 1d 60 active alive 0 0 2 port2 path0 tgt4 lun1 c2t4d1 FA 7e 00 active alive 0 0 1 port1 path0 tgt6 lun2 c1t6d2 FA 2d 61 active alive 0 0 1 port1 path0 tgt5 lun2 c1t5d2 FA 2d 60 active alive 0 0 1 port1 path0 tgt4 lun1 c1t4d1 FA 8e 00 active alive 0 0 Pseudo name harddisk3 Symmetrix ID 000195703184 Logical device ID 015A Device WWN 6000097...

Page 21: ...ed as ports 60 and 61 This does not apply to PP 6 2 and above where the ports are displayed correctly LIST THE NDM SESSIONS There are different options that can be used to list the NDM sessions Adding v to the symdm list command provides more detail about the session C symdm sid 3184 sg lcseb246_sg list v Symmetrix ID 000195703184 Storage Group lcseb246_sg Source Array 000195703184 Target Array 00...

Page 22: ...sg Status OK Dev 00158 0015B Masking Views 1 OK Masking View Name Initiator Group Port Group Status lcseb246_mv lcseb246_ig lcseb246_pg OK Initiator Groups 1 OK Name lcseb246_ig Status OK Initiator WWN 20000025b570a00f 20000025b570b00f Port Groups 1 OK Name lcseb246_pg Status OK Dirport Status 08E 000 OK 07E 000 OK Target Configuration OK Storage Groups 1 OK Name lcseb246_sg ...

Page 23: ...016 Masking Views 1 OK Masking View Name Initiator Group Port Group Status lcseb246_mv lcseb246_ig lcseb246_pg OK Initiator Groups 1 OK Name lcseb246_ig Status OK Initiator WWN 20000025b570a00f 20000025b570b00f Port Groups 1 OK Name lcseb246_pg Status OK Dirport Status 01D 028 OK 01D 029 OK 02D 028 OK 02D 029 OK ...

Page 24: ...up lcseb246_sg Source Array 000195703184 Target Array 000197800129 Migration State CutoverReady Total Capacity GB 200 0 Done N A Device Pairs 4 OK Source Target Dev Status Dev Status 00158 OK 00013 OK 00159 OK 00014 OK 0015A OK 00015 OK 0015B OK 00016 OK C symdm sid 0129 sg lcseb246_sg list v detail sg_info Symmetrix ID 000197800129 Storage Group lcseb246_sg Source Array 000195703184 Target Array ...

Page 25: ...CE PAIRING AND IDENTITIES FOLLOWING A CREATE The create operation automatically configures matching volumes on the target array These volumes will be the same size and configuration though they will most likely not have the same VMAX volume numbers Following the create operation the 4 new volumes on the target array are 0013 through 0016 Volume 0158 and volume 0013 are paired for NDM operations Th...

Page 26: ...the same on the source device 0158 C symdev show 0158 sid 3184 Device Physical Name Not Visible Device Symmetrix Name 00158 Device Serial ID N A Symmetrix ID 000195703184 Number of RAID Groups 0 Encapsulated Device No Encapsulated WWN N A Encapsulated Device Flags None Encapsulated Array ID N A Encapsulated Device Name N A Attached BCV Device N A Attached VDEV TGT Device N A Vendor ID EMC Product ...

Page 27: ...evice paths are active C symdev show 0013 sid 0129 Device Physical Name Not Visible Device Symmetrix Name 00013 Device Serial ID N A Symmetrix ID 000197800129 Number of RAID Groups 0 Encapsulated Device No Encapsulated WWN N A Encapsulated Device Flags None Encapsulated Array ID N A Encapsulated Device Name N A Attached BCV Device N A Attached VDEV TGT Device N A Vendor ID EMC Product ID SYMMETRIX...

Page 28: ...ancel nop A DM Cancel operation is in progress for storage group lcseb246_sg Please wait Analyze Configuration Started Source SID 000195703184 Target SID 000197800129 Analyze Configuration Done Remove Masking View s on Target Started Remove Masking View s on Target In Progress Remove Masking View s on Target Done Remove Data Replication Started Remove Data Replication Done Remove Port Group s on T...

Page 29: ...age Group lcseb246_sg Source Array 000195703184 Target Array 000197800129 Migration State CutoverReady Total Capacity GB 200 0 Done N A Device Pairs 4 OK Source Target Dev Status Dev Status 00158 OK 00013 OK 00159 OK 00014 OK 0015A OK 00015 OK 0015B OK 00016 OK A cutover operation moves the target devices out of pass through mode initiates data synchronization from the source to the target and mak...

Page 30: ...er operation completes the data copy begins The session is in a Migrating state and will remain in that state until either the pairs are cutover to the new array or other action is taken The data movement can be monitored with symdm list using any of the options for displaying Storage Group Masking View Initiator Group Port Group and device pairs or run without any of the details C symdm sid 0129 ...

Page 31: ...eb246_sg list Symmetrix ID 000197800129 Storage Group lcseb246_sg Total Source Target Capacity Done Array Array State GB 000195703184 000197800129 Migrating 200 0 100 The volumes are now in a CutoverSync state C symdm sid 0129 sg lcseb246_sg list Symmetrix ID 000197800129 Storage Group lcseb246_sg Total Source Target Capacity Done Array Array State GB 000195703184 000197800129 CutoverSync 200 0 N ...

Page 32: ...ield C powermt display dev all Pseudo name harddisk1 Symmetrix ID 000195703184 Logical device ID 0158 Device WWN 60000970000195703184533030313538 state alive policy SymmOpt queued IOs 0 Host Stor I O Path Stats HW Path I O Paths Interf Mode State Q IOs Errors 2 port2 path0 tgt6 lun1 c2t6d1 FA 1d 61 active alive 0 0 2 port2 path0 tgt5 lun1 c2t5d1 FA 1d 60 active alive 0 0 2 port2 path0 tgt4 lun0 c2...

Page 33: ...t5d3 FA 1d 60 active alive 0 0 2 port2 path0 tgt4 lun2 c2t4d2 FA 7e 00 active dead 0 0 1 port1 path0 tgt6 lun3 c1t6d3 FA 2d 61 active alive 0 0 1 port1 path0 tgt5 lun3 c1t5d3 FA 2d 60 active alive 0 0 1 port1 path0 tgt4 lun2 c1t4d2 FA 8e 00 active dead 0 0 Pseudo name harddisk4 Symmetrix ID 000195703184 Logical device ID 015B Device WWN 60000970000195703184533030313542 state alive policy SymmOpt q...

Page 34: ...d Device No Encapsulated WWN N A Encapsulated Device Flags None Encapsulated Array ID N A Encapsulated Device Name N A Attached BCV Device N A Attached VDEV TGT Device N A Vendor ID EMC Product ID SYMMETRIX Product Revision 5876 Device WWN 60000970000195703184533030313538 Device Emulation Type FBA Device Defined Label Type N A Device Defined Label N A Device Sub System Id 0x0001 Cache Partition Na...

Page 35: ...ULT_PARTITION Bound Pool Name SRP_1 Device Block Size 512 Device Capacity Cylinders 27307 Tracks 409605 512 byte Blocks 104858880 MegaBytes 51201 KiloBytes 52429440 Geometry Limited No Device External Identity Device WWN 60000970000195703184533030313538 REVERT TO THE SOURCE ARRAY Because the migration is not permanent until the commit operation is run after a cutover the migration can still be can...

Page 36: ...get Started Wait for deallocation to complete Started Wait for deallocation to complete Done Remove Duplicate Device s on Target In Progress Remove Duplicate Device s on Target Done Remove Storage Group s on Target Started Remove Storage Group s on Target Done The DM Cancel Revert operation successfully executed for storage group lcseb246_sg After a revert operation the state of the devices and th...

Page 37: ...ete replication between the source and target arrays is terminated The source devices are no longer be visible to a host because the masking has been removed The source device IDs have also been permanently swapped with the target device IDs C symdm commit sid 0129 sg lcseb246_sg nop A DM Commit operation is in progress for storage group lcseb246_sg Please wait Analyze Configuration Started Source...

Page 38: ...queued IOs 0 Host Stor I O Path Stats HW Path I O Paths Interf Mode State Q IOs Errors 2 port2 path0 tgt6 lun1 c2t6d1 FA 1d 60 active alive 0 0 2 port2 path0 tgt5 lun1 c2t5d1 FA 1d 61 active alive 0 0 1 port1 path0 tgt6 lun1 c1t6d1 FA 2d 61 active alive 0 0 1 port1 path0 tgt5 lun1 c1t5d1 FA 2d 60 active alive 0 0 Pseudo name harddisk2 Symmetrix ID 000195703184 Logical device ID 0159 Device WWN 600...

Page 39: ...essing devices on the target array only The source devices are no longer accessible though they are not removed by NDM C symdev show 013 sid 0129 Device Physical Name PHYSICALDRIVE11 Device Symmetrix Name 00013 Device Serial ID 2900013000 Symmetrix ID 000197800129 Number of RAID Groups 0 Encapsulated Device No Encapsulated WWN N A Encapsulated Device Flags None Encapsulated Array ID N A Encapsulat...

Page 40: ...ctors Track 128 Tracks Cylinder 15 Cylinders 54614 512 byte Blocks 104858880 MegaBytes 51201 KiloBytes 52429440 Device Configuration TDEV SCSI 3 Persistent Reserve Enabled Dynamic Spare Invoked No Dynamic RDF Capability RDF1_OR_RDF2_Capable STAR Mode No STAR Recovery Capability None STAR Recovery State NA SQAR_MODE No Device Service State Normal Device Status Ready RW Device SA Status Ready RW Dev...

Page 41: ...EVICE IDENTITIES FOLLOWING A COMMIT Following the commit operation each device presents the opposite device ID The source device now presents the target device ID as its external identity and the target presents the source device ID as its external identity These changes are permanent and will persist across system power cycles and even the deletion and recreation of the devices In other words if ...

Page 42: ...54614 Tracks 819210 512 byte Blocks 104858880 MegaBytes 51201 KiloBytes 52429440 Geometry Limited No Device External Identity Device WWN 60000970000197800129533030303133 Target device C symdev show 013 sid 0129 Device Physical Name Not Visible Device Symmetrix Name 00013 Device Serial ID N A Symmetrix ID 000197800129 Number of RAID Groups 0 Encapsulated Device No Encapsulated WWN N A Encapsulated ...

Page 43: ... environment such as a connectivity issue between the source and target arrays or the failure of a command to complete that leaves an NDM operation only partially finished In this example a create failed because of a transient issue on the target array The transient issue resolved itself within seconds and a recover operation was immediately run The recover operation picks up where the create comm...

Page 44: ... Done The DM Recover operation successfully executed for storage group lcseb246_sg REMOVE THE MIGRATION ENVIRONMENT Running the environment remove takes down the replication pathway configured by the environment setup operation deletes the RDF group and removes all resources that were used to support NDM on the source and target arrays Upon successful completion of an environment remove operation ...

Page 45: ...meaning directly connected to the host and not discovered as a remote array via SRDF Both arrays will appear as local arrays if the Unisphere host is directly attached to both This is not required for NDM operations Only the host being migrated is required to be directly attached to both arrays Note In the lab environment used here the Solutions Enabler commands are run from the host that is being...

Page 46: ...46 There are four 50 GB data volumes presented to the host from the source array volumes 0158 to 015B They are non SRDF volumes ...

Page 47: ...determine the ideal target ports to use for an NDM migration If WLP is used it must be run from a control host that has access to both arrays It cannot be run from Embedded Unisphere for VMAX Note The Windows disk numbers will change in the output due to changes in the test environment SET UP THE ENVIRONMENT Once the required pre migration tasks are completed the environment can be setup using NDM...

Page 48: ...elect Run Now When the task completes the Source and Target arrays are displayed in a State of OK indicating migrations are now possible between the arrays listed Note Workload Planner WLP is a Unisphere utility that can be used to determine the ideal target ports to use for an NDM migration If WLP is used it must be run from a control host that has access to both arrays It cannot be run from Embe...

Page 49: ... Passthrough mode that allows the data to be accessed from both the source and target devices Prior to running the create the target array resources can be validated to ensure that the target array has the resources required to configure the migration sessions Click on the storage group to select it click the double angle brackets and click Manage Select the remote VMAX array from the Symmetrix pu...

Page 50: ...50 Click the Create Data Migration radio button and click Next Note If compression is available on a VMAX All Flash target array a Compression checkbox will appear on this screen ...

Page 51: ...51 View the summary Click the angle bracket next to Add to Job List and click Run Now Confirm that the migration session was created ...

Page 52: ... is existing SRDF DR replication from the source device and the target will be an R1 device This is different than basic SRDF operations and is required to allow DR protection during a migration using a cascaded SRDF configuration See the section entitled ADDING DISASTER RECOVERY TO THE TARGET ARRAY for more details ...

Page 53: ...t arrays through the host multipathing software This is possible because the target devices are in Passthrough mode See Appendix A for more details on the host multipathing software CUTOVERREADY AND PASSTHROUGH MODE Passthrough mode allows the host to write to or read from either the source or target array Any write that in sent to the target array will be sent across the SRDF link and serviced by...

Page 54: ...ARRAY for more details PowerPath shows all paths to the source and target devices as alive HYPERMAX OS will ensure that all I Os that are directed to the target array by the host are actually serviced by the source array until the cutover The paths will all remain in an alive state until after the commit operation VIEW MIGRATION SESSION DETAILS Double Click the migration session to view details ab...

Page 55: ...s will be the same size and configuration though they will most likely not have the same VMAX volume numbers Following the create operation the 4 new volumes on the target array are 0166 through 0169 Volume 0166 and volume 002E are paired for NDM operations Source Device ID The native and effective device IDs are the same on the source device 0166 ...

Page 56: ...ective target device IDs are not the same on the target device 001D Device 001D has a unique native device ID but its effective ID is the same as device 0158 This is required at this stage of the migration because all device paths are active ...

Page 57: ...as not moved to the target array Cancelling a migration removes the storage and groups provisioned for the migration on the target array releases resources allocated by Solutions Enabler to perform the migration and places the source devices into the state they were in before the Create operation was run It does not affect the replication pathways put in place with the environment setup To cancel ...

Page 58: ...acket next to Add to Job List and click Run Now Note The Revert option will have a checkbox when a revert operation is applicable It is not required before running a cancel operation while the SG is in a CutoverReady state ...

Page 59: ...istrator should perform a rescan to remove the dead paths to the target array PERFORM A CUTOVER TO THE TARGET ARRAY Prior to this step the migration session that was cancelled in the last step was simply created again The host also rescanned for devices so the pairs are in a CutoverReady state To cut the storage group over to the target click Cutover ...

Page 60: ...60 Click the angle bracket next to Add to Job List and click Run Now ...

Page 61: ...n moves the target devices out of pass through mode initiates data synchronization from the source to the target and makes the host paths to the source array inactive so that all I Os are being serviced by the target array ...

Page 62: ...utover operation completes the data copy begins The session is in a Migrating state and will remain in that state until either the pairs are cutover to the new array or other action is taken The volumes are now in a CutoverSync state ...

Page 63: ...ive In PowerPath the terms used are dead and alive Note The PowerPath mode is active for all paths This is a PowerPath term and is unrelated to the active and inactive path states in NDM terminology PowerPath will show the state of the path and whether it is alive or dead in the state field Following the cutover two paths are dead and the devices are degraded ...

Page 64: ...array from the target array and the migration can be cancelled EXAMINE THE DEVICE IDENTITIES FOLLOWING A CUTOVER The device IDs used on the source and target devices have not changed following the Cutover operation The target devices are still using the effective WWN of the source devices The source devices still have the same native and effective IDs ...

Page 65: ...65 Source device ...

Page 66: ... to the source array To revert back to the source array following a cutover a cancel is run with the revert option The revert option moves the processing back to the source array and the cancel removes all of the target side entities created for the migration This operation will leave the environment in the same state as it was prior to the create operation The revert operation may ...

Page 67: ...ctive again This is monitored by the VMAX which will wait for the rediscovery before proceeding To cancel the migration click the double angle brackets and click Cancel Migration At the Cancel Migration dialog box make sure the Revert box is checked Click the angle bracket next to Add to Job List and click Run Now ...

Page 68: ...lable The paths to the source array should be returned to the original configuration to avoid Data Unavailability A host HBA rescan should be undertaken to ensure application stability Note The cancel revert operation may take some time to complete The Revert Data Replication step will repeat and remain In Progress until the step is complete ...

Page 69: ...y system resources used for the migration Once the commit is complete replication between the source and target arrays is terminated The source devices are no longer be visible to a host because the masking has been removed The source device IDs have also been permanently swapped with the target device IDs Figure 13 Commit To commit the state of the migration sessions must be CutoverSync or Cutove...

Page 70: ... next to Add to Job List and click Run Now After the commit operation succeeds the migration is complete Because the commit completes the migration and removes all of the source side masking there are no longer any active paths seen to the source array ...

Page 71: ...e opposite device ID The source device now presents the target device ID as its external identity and the target presents the source device ID as its external identity These changes are permanent and will persist across system power cycles and even the deletion and recreation of the devices In other words if device 166 is deleted when recreated it will still show the identity of device 001D ...

Page 72: ...72 Source Device ...

Page 73: ...73 Target Device ...

Page 74: ...port This is to be rectified in the next Hypermax OS release and will be user adjustable as long as the LUN is not in a replication session USE THE RECOVER COMMAND The recover command can be used if a migration step fails due to some problem in the environment such as a connectivity issue between the source and target arrays or the failure of a command to complete that leaves an NDM operation only...

Page 75: ...75 Click the angle bracket next to Add to Job List and click Run Now ...

Page 76: ...the resources that were configured to support NDM on the source and target arrays Upon successful completion of an environment remove operation only running an environment setup operation is allowed This should be run only after all migrations from the source array have been completed From the Data Protection Tab click the Manage Environments Option ...

Page 77: ...ve Once the task has complete the Environment is no longer available for migrations and will need to be setup should further migrations be required ADD DISASTER RECOVERY TO THE TARGET ARRAY Prior to a migration many environments contain both local Snap VX sessions and SRDF remote replication sessions ...

Page 78: ...ss the R1 or the R21 In most SRDF environments only the R1 or R2 can be written to never both at the same time The exceptions to this are NDM and SRDF Metro During an NDM migration DR is preserved by configuring local and remote replication SRDF and Snap VX when the NDM session is in a CutoverSync state The following diagram shows the configuration with existing SRDF replication and what the envir...

Page 79: ...D ABOVE Use the default Powerpath multi path settings To detect rescan and configure new paths use the powermt config command Specifically for Linux use etc opt emcpower emcplun_linux scan all noprompt may be used This will rescan and perform a powermt config Refer to the PowerPath for Linux manual on http support emc com for further information Use Powerpath commands scripts to scan on Linux usr ...

Page 80: ...mp_restore_cycles 10 10 iopolicy per DMP node name MinimumQ MinimumQ When these values are not set the cancel revert will not work correctly Use the rescan command On Linux usr bin rescan_scsi_bus sh followed by vxdisk scandisks to detect new paths Use vxdmpadm to verify that the new paths are added https sort symantec com public documents dmp 6 0 vmwareesx productguides html dmp_admin ch06s08 htm...

Page 81: ...es by running emc_pp_configure sh script This script will configure the new native devices on the target side into PowerPath by copying the attributes of the PowerPath hdiskpower pseudo devices into the new native devices and reconfigure the native devices 4 Cutover Storage Group to VMAX3 or VMAX All Flash array 5 Monitor for synchronization to complete 6 Commit the migration Note This script MUST...

Page 82: ...ntinue with synchronization and movement towards the CutoverSync state will not be affected by the removal of the inactive paths following a reboot Cutover Ready Since the paths to both arrays were alive at the time of reboot they will not be affected Recommendation at the point is to verify all paths initialize as expected before continuing CutoverNoSync A reboot during the CutoverNoSync state ma...

Reviews:

No comments

Brands by name

Popular brands

Load more brands