HP0-J73 · Question #58
When designing an HP 3PAR StoreServ environment that involves HP Peer Motion, which configuration requirements must be considered? (Select Two)
The correct answer is B. Source and destination arrays must be at InForm software version 3.1.2 or higher. C. The destination system cannot import volumes with existing Remote Copy membership.. HP 3PAR Peer Motion non-disruptive migration requires compatible InForm OS versions on both arrays and prohibits importing volumes on the destination that already belong to a Remote Copy group.
Question
When designing an HP 3PAR StoreServ environment that involves HP Peer Motion, which configuration requirements must be considered? (Select Two)
Options
- AAll host servers connected to the target array must be removed from the Fibre Channel zoning to
- BSource and destination arrays must be at InForm software version 3.1.2 or higher.
- CThe destination system cannot import volumes with existing Remote Copy membership.
- DVolume Sets are not supported during the migration and volume-set membership must be removed.
How the community answered
(40 responses)- A20% (8)
- B70% (28)
- D10% (4)
Why each option
HP 3PAR Peer Motion non-disruptive migration requires compatible InForm OS versions on both arrays and prohibits importing volumes on the destination that already belong to a Remote Copy group.
Peer Motion is designed for non-disruptive, live migration, so host servers connected to the target array do not need to be removed from Fibre Channel zoning - host access remains intact throughout the migration.
Both the source and destination 3PAR StoreServ arrays must run HP InForm OS version 3.1.2 or higher to ensure the Peer Motion migration protocol is supported and compatible on both ends of the migration path.
The destination 3PAR system cannot accept volumes that already have Remote Copy group membership, because that membership creates a data consistency conflict with the Peer Motion live migration process and must be resolved before migration begins.
Volume Set membership does not need to be removed before a Peer Motion migration; Volume Sets are supported during the migration process and are not a stated configuration restriction.
Concept tested: HP 3PAR Peer Motion non-disruptive migration configuration requirements
Topics
Community Discussion
No community discussion yet for this question.