Backup Server ↔ Fibre Channel Array: Does block-level restore preserve LUN WWN, LUN ID, and fabric zoning?

Question

Backup server restores blocks to a mapped LUN on a Fibre Channel array, creating a new device view for the operating system unless the array or backup plug‑in explicitly retains the source LUN WWN, serial number, and fabric zoning.
The integration‑boundary question is whether block‑level restore preserves these identity attributes and if recovered data can be validated without attaching the original production host.
Uncertainty arises from vendor‑specific firmware behavior, HBA driver versions, and multipathing software, which may affect LUN identity and zoning consistency. The decision requires choosing between presenting the restored LUN on an isolated host for verification or rezoning it to the original production host, and selecting an appropriate validation method. Does the restore preserve the LUN WWN and zoning? Can verification be performed on an isolated host without affecting production? Which validation method is required for transactional databases?

Zoha · Answer

Direct AnswerBlock-level restores to Fibre Channel arrays do not guarantee preservation of LUN WWN, LUN ID, or fabric zoning. These attributes depend on array firmware and the backup integration plugin, not the restore process itself.
Confirmed Behavior
LUN ID and WWN: Most arrays assign new identifiers to restored LUNs, treating them as distinct virtual devices.Fabric zoning: SAN zoning is not automatically recreated; the restored LUN appears on the target array’s fabric ports but requires manual host-to-array mapping.Array plugins: Some vendor-specific backup tools (e.g., NetApp SnapMirror, Dell PowerProtect) can preserve source LUN metadata through explicit mapping, but this is not standard block-level restore behavior.
Verification Steps
After restore, use fcinfo lun get-target (Solaris), systool -c fc_host -v (Linux), or the HBA vendor’s CLI to compare WWN/LUN ID of the restored device against the original.On the restored LUN’s host, verify multipath paths using multipath -ll; refresh with multipath -r if needed.Check fabric visibility: the host HBA must show the restored LUN’s target port WWN. If not, confirm zoning permits access.
Isolated Host ValidationValidation on an isolated host is possible if the SAN fabric allows the restored LUN to be presented without conflicting with production zoning. This typically requires:
A dedicated zone or VSAN on the fabric switch.Explicit LUN masking on the array to the isolated host’s HBA WWNs.
Transactional Database ValidationFor databases (e.g., Oracle, SQL Server), file-level checksum validation is insufficient. Use the application’s native recovery verification:
Oracle RMAN VALIDATE DATABASE after restore.SQL Server RESTORE VERIFYONLY with the restored files.Application-consistent restores require pre-restore log backup and post-restore log replay to confirm transactional integrity.
Action RequiredIdentify your array vendor and backup plugin. Check the vendor’s backup integration guide for LUN identity preservation features. Without this, assume new WWN/LUN ID and manual zoning.

Backup Server ↔ Fibre Channel Array: Does block-level restore preserve LUN WWN, LUN ID, and fabric zoning?

1 answer

Direct Answer

Confirmed Behavior

Verification Steps

Isolated Host Validation

Transactional Database Validation

Action Required

Your perspective belongs here.

1 question comment

Key Clarification

Practical Verification Path

Safe Isolated Validation