An administrator wants to migrate an FLR-enabled file system with DHSM-enabled from a Dell VNX array to a new Dell Unity XT array. What method should they use?

Question

Options

• ANative Unity File Import feature
• BAsynchronous replication
• CReplication using RecoverPoint
• DCTA with Unity as the tiering destination

• A
  80% (16)
• B
  10% (2)
• C
  5% (1)
• D
  5% (1)

Explanation

Native Unity File Import is the correct choice because it is the purpose-built migration path from VNX to Unity XT that explicitly supports preserving both FLR (File Level Retention/WORM) attributes and DHSM (Dynamic Host Storage Management) tiering configurations - these specialized metadata would be lost or unsupported via generic migration methods.

Why the distractors fail:

• B (Async replication): Replication syncs data blocks but does not carry FLR retention locks or DHSM stubs across heterogeneous platforms; it's designed for ongoing DR, not migration.
• C (RecoverPoint): RecoverPoint is a continuous data protection/DR appliance, not a heterogeneous file migration tool, and lacks awareness of FLR/DHSM semantics.
• D (CTA with Unity as tiering destination): CTA (Cloud Tiering Appliance) moves cold data to a tier - it doesn't migrate a source file system wholesale with its compliance and tiering metadata intact.

Memory tip: Think "Import = Intact" - the Native Unity File Import is the only tool that brings the full file system as-is, compliance settings and all, from VNX to Unity XT. If the question mentions FLR or DHSM in a VNX→Unity migration, the answer is always native import.

No community discussion yet for this question.