HP0-J73 · Question #307
Which storage functionality is leveraged to enable single volume migration with the HP 3PAR OS 3/1.3 storage federation enhancement? (Select two)
The correct answer is B. HP 3PAR StoreServ Remote Copy E. HP SPAR StoreServ ALUA compliant host personas. Single volume migration in HP 3PAR OS 3.1.3 storage federation relies on Remote Copy for data replication and ALUA compliant host personas for transparent host path management during migration.
Question
Which storage functionality is leveraged to enable single volume migration with the HP 3PAR OS 3/1.3 storage federation enhancement? (Select two)
Options
- AHP 3PAR StoreServ Port Persistence
- BHP 3PAR StoreServ Remote Copy
- CHP 3PAR StoreServ Peer Persistence
- DHP SPAR StoreServ Peer Motion
- EHP SPAR StoreServ ALUA compliant host personas
How the community answered
(24 responses)- A8% (2)
- B83% (20)
- C4% (1)
- D4% (1)
Why each option
Single volume migration in HP 3PAR OS 3.1.3 storage federation relies on Remote Copy for data replication and ALUA compliant host personas for transparent host path management during migration.
HP 3PAR StoreServ Port Persistence preserves host-facing WWN or iSCSI identifiers across controller failover events and is not a mechanism that enables volume migration between federated arrays.
HP 3PAR StoreServ Remote Copy provides the underlying replication engine that moves volume data between federated 3PAR arrays, enabling non-disruptive single volume migration by synchronizing data across systems before cutover.
HP 3PAR StoreServ Peer Persistence is a high-availability feature that enables transparent array-level failover between two 3PAR systems, not the underlying functionality for single volume migration within a federation.
HP 3PAR StoreServ Peer Motion enables live volume migration between arrays, but it is a separate product feature and not the storage functionality leveraged as the foundation of the 3.1.3 federation enhancement described.
HP 3PAR StoreServ ALUA compliant host personas allow hosts to transparently manage active and standby I/O paths during migration, ensuring continuous host access as volumes transition between source and target arrays in the federation.
Concept tested: HP 3PAR OS 3.1.3 federation single volume migration mechanisms
Source: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-c03290624
Topics
Community Discussion
No community discussion yet for this question.