HP 3PAR StoreServ 7400 2-node HP 3PAR-to-3PAR Storage Peer Motion Guide (OS 3. - Page 61

following commands, completes, you can stop and delete the Remote Copy group. On the source system

Get HP 3PAR StoreServ 7400 2-node PDF manuals and user guides View all HP 3PAR StoreServ 7400 2-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 61 highlights

6. On the source system, re-admit the primary virtual volume into the original periodic group and restart the group. You do not need to wait for the import virtual volume operation to complete; you are admitting the original periodic group with the original primary and secondary virtual volumes. Issue the following commands: # admitrcopyvv : # startrcopygroup : 7. At this point, you can maintain a full primary-to-secondary Remote Copy relationship for the duration of the import operation, minimizing downtime. Once the peer-motion migration completes, you can stop and delete the Remote Copy group. On the source system, issue the following commands: # stoprcopygroup # removercopygroup 8. On the secondary system, create a new Remote Copy target. Issue the following commands: # creatercopytarget IP|FC # creatercopygroup :periodic # admitrcopyvv : 9. On the secondary system, start the new Remote Copy group and verify the status. Issue the following commands: # startrcopygroup : # showrcopy At this point, the new secondary system should be up and running with functioning secondary periodic Remote Copy groups. 61

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
6.
On the source system, re-admit the primary virtual volume into the original periodic group and
restart the group. You do not need to wait for the import virtual volume operation to complete;
you are admitting the original periodic group with the original primary and secondary virtual
volumes. Issue the following commands:
#
admitrcopyvv <primary_vv> <rcpm_group> <destination_system>:<old_secondary_vv>
#
startrcopygroup <rcpm_group> <primary_vv>:<primary_vv_starting_ss>
7.
At this point, you can maintain a full primary-to-secondary Remote Copy relationship for the
duration of the import operation, minimizing downtime. Once the peer-motion migration
completes, you can stop and delete the Remote Copy group. On the source system, issue the
following commands:
#
stoprcopygroup <rcpm_group>
#
removercopygroup <rcpm_group>
8.
On the secondary system, create a new Remote Copy target. Issue the following commands:
#
creatercopytarget <backup_system> IP|FC <n:s:p:ip_address|wwn>
#
creatercopygroup <new_rcpm_group> <backup_system>:periodic
#
admitrcopyvv <primary_vv> <new_rcpm_group> <backup_system>:<new_secondary_vv>
9.
On the secondary system, start the new Remote Copy group and verify the status. Issue the
following commands:
#
startrcopygroup <new_rcpm_group> <primary_vv>:<primary_vv_starting_ss>
#
showrcopy
At this point, the new secondary system should be up and running with functioning secondary
periodic Remote Copy groups.
61