H13-629_V3.0 · Question #87
When performing heterogeneous takeover before migration based on intelligent virtualization and intelligent migration, the operator needs to create eDevLUN for LUN from the heterogeneous storage…
The correct answer is A. True. Option A is correct because, in Huawei's SmartVirtualization (intelligent virtualization) framework, heterogeneous takeover requires the Huawei storage system to "see" and manage LUNs from a third-party array - and this is achieved by creating an eDevLUN (External Device LUN)…
Question
When performing heterogeneous takeover before migration based on intelligent virtualization and intelligent migration, the operator needs to create eDevLUN for LUN from the heterogeneous storage system
Options
- ATrue
- BFalse
How the community answered
(42 responses)- A71% (30)
- B29% (12)
Explanation
Option A is correct because, in Huawei's SmartVirtualization (intelligent virtualization) framework, heterogeneous takeover requires the Huawei storage system to "see" and manage LUNs from a third-party array - and this is achieved by creating an eDevLUN (External Device LUN), which maps the foreign LUN into the Huawei namespace as a virtual representation. Without the eDevLUN, the intelligent migration engine has no local object to track, migrate data from, or present to hosts during the cutover. This eDevLUN creation is therefore a mandatory prerequisite step, not an optional one, making option B (False) incorrect - skipping it would break the migration workflow entirely.
Memory tip: Think of eDevLUN as an "adapter plug" - before you can plug a foreign device into the Huawei system and move its data, you must first create the adapter (eDevLUN); no adapter = no migration.
Topics
Community Discussion
No community discussion yet for this question.