Storage / Unity XT / NAS Migration

Is the Unity import a file project, or a block cutover?

File import is not block import. Freeze mobility network, version gates, share inventory, and cutover windows before the Unity NAS RFQ leaves procurement.

Quick Take

Quick Take: Importing Unity file services into PowerStore is a different project from block migration: it needs a File Mobility Network, a verified Unity OE and PowerStoreOS pairing, and SMB or LDAP identity prep. A quote priced on terabytes alone leaves the cutover work and its risk unfunded.

Why File-Import RFQs Fail

Quick Answer: Teams copy the block RFQ and miss mobility IPs, SMB ACL prep, AD trust checks, and multiprotocol OS gates. Background copy looks fine; cutover day fails on DFS, permissions, or unsupported NAS shapes. Price services against a real NAS inventory rather than a block-import assumption.

Status note: File-import support varies by Unity OE and PowerStoreOS. Confirm the Dell Simple Support Matrix for your exact multiprotocol, NFSv4, FLR, and CTA cases before locking PO or blackout windows.
30–90
Min Cutover Window
3
Mobility Network IPs
1
Pilot NAS First
0
Assume = Block

Unity XT End-of-Sale forces many estates to move block and file in the same program. Block can use non-disruptive import or Storage vMotion; NAS uses native file import with a different prep and cutover shape. Pair this checklist with the method downtime guide, phased cutover schedule, and Unity EoS RFQ guide.

BENQUAN GLOBAL LIMITED supplies Dell PowerStore targets and Unity NAS migration packages with cutover-aware RFQ support — request a free NAS cutover BOM risk assessment.

Failure mode What it looks like RFQ fix
Block template reuse No File Mobility Network line Require mobility IPs + Unity import IF
Version hope OE / OS combo unsupported Matrix check before PO
Share blindness DFS / home dirs break post-cut Share and export inventory attached
One big bang All NAS servers one weekend Pilot + 2–4 waves

NAS Inventory Template (Attach to RFQ)

Quick Answer: One row per Unity NAS server: protocol mix, file-system count, share and export totals, special features such as FLR or CTA stubs, and the identity source. Vendors cannot size import sessions or cutover minutes without it, and any shape the target PowerStoreOS does not confirm belongs in hold-back.

Field Why it matters Example
NAS server name Import unit of work nas-corp-01
Protocol mix OS feature gate SMB-only / NFS / multiprotocol
File systems Cutover duration 12 FS
Shares / exports Client remount plan 80 SMB + 15 NFS
Special features Hold-back risk FLR, CTA stubs, NFSv4.2 labels
Identity Post-cut auth AD domain / LDAP / local

Hold-back rule

If a NAS server uses a feature not confirmed on the target PowerStoreOS, park it in hold-back until OS upgrade or alternate method is approved — do not bury it inside Batch-1.

Version and Network Gates (Non-Negotiable)

Quick Answer: Gate 1 is Unity OE plus PowerStoreOS compatibility for your protocol mix. Gate 2 is File Mobility Network (three IPs) and a dedicated Unity import interface. Gate 3 is SMB ACL parameter prep where required. Skip a gate and the first production NAS cutover inherits unknown auth and path risk.

Gate 1 — Version matrix

Confirm Unity OE and PowerStoreOS for native file import, multiprotocol, and NFSv4 needs against the current Dell support matrix. Some OE builds historically blocked unified file import — verify before CapEx is locked.

Gate 2 — File Mobility Network

PowerStore file import expects a File Mobility Network (cluster + node A + node B IPs on the management subnet range) plus a dedicated, unused production IP on the source Unity NAS server for migration traffic.

Gate 3 — SMB / time / identity

For SMB imports, apply Dell-documented ACL parameter prep on Unity where required; keep NTP within a few seconds across systems; validate AD or LDAP bindings before cutover, not after.

Hard rule: Do not schedule production NAS cutover on the same day PowerStore is unboxed. Commission mobility network and run a pilot NAS import first.

Cutover Windows and Dual-Run

Quick Answer: Background copy keeps clients on Unity; cutover moves the NAS server to PowerStore and typically needs a 30–90 minute blackout. Pilot one low-risk NAS server, then batch by dependency. Keep Unity dual-run until permissions, DFS, and backup jobs are signed off.

Phase Client impact Ops focus
Prep None Inventory, matrix, mobility IPs
Background copy None (source still live) Watch session health / bandwidth
Cutover 30–90 min typical Quiesce, flip, remount checks
Dual-run None if cut clean ACL / DFS / backup validation
Wipe gate N/A Only after all NAS batches signed

Place NAS waves on the same program calendar as block cutovers — see the phased Elite + Unity schedule — but never assume identical minutes or owners.

RFQ Checklist for Unity NAS File Import

Quick Answer: Attach NAS inventory, OE/OS matrix result, mobility IP plan, SMB prep notes, pilot NAS name, blackout windows, rollback criteria, and dual-run wipe gate. Ask vendors to price the array plus file-import services against that whole package, never against a one-night NAS go-live.

  • NAS server spreadsheet (protocol, FS count, shares/exports, special features)
  • Written OE + PowerStoreOS compatibility for each NAS shape
  • File Mobility Network IPs reserved; Unity import interface named
  • SMB ACL / NTP / AD prep owned and dated
  • Pilot NAS server identified (non-critical)
  • Production batch list with blackout owners
  • Post-cutover validation: ACL sample, DFS, backup, quota
  • Unity retention / wipe gate after all NAS batches signed
  • Target array BOM options (including Elite if that is the CapEx path)

Frequently Asked Questions

Quick Answer: File import is not block import. Budget about 30–90 minutes for cutover after background copy. RFQs need inventory, version gates, and mobility network. Multiprotocol support depends on PowerStoreOS — lock the OS version before assuming every Unity NAS server imports cleanly.

No. File import moves NAS servers and share config through a different workflow with mobility-network prep and a planned cutover window — typically longer than a non-disruptive block path flip.

Plan roughly 30–90 minutes per wave depending on file-system and interface count. Background copy can run while clients stay on Unity; cutover is when I/O must land on PowerStore.

NAS inventory, OE/OS compatibility, File Mobility Network IPs, SMB prep if required, blackout windows, pilot scope, and dual-run wipe criteria.

It depends on PowerStoreOS generation. Dual-protocol and multiprotocol paths expanded in later releases — lock the target OS in the RFQ before assuming every NAS server can import as-is.

Send the NAS inventory and target go-live via Free Compatibility & Delivery Risk Assessment or email info@benquan.hk. You receive PowerStore options with schedule-aware file-import notes from a global free-port hub.

Key Takeaway

Key Takeaway: Fund the migration as services rather than capacity: name the pilot NAS server, reserve the three mobility IPs, and hold any share using FLR, CTA stubs or NFSv4 labels out of the first wave. BENQUAN GLOBAL LIMITED supplies Dell PowerStore arrays with competitive pricing.

Is your Unity NAS still priced like a LUN import?

If the RFQ prices TB but omits mobility network, protocol gates, and NAS cutover windows, request a free compatibility and delivery risk assessment. We align PowerStore options with a file-import cutover package from a global free-port hub.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834 · info@benquan.hk

Contents