Dell Unity: 2-Way NDMP backup failing after rebooting Data Domain VTL

Summary: 2-Way NDMP backup failing after rebooting Data Domain VTL (Customer Correctable)

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

  • 2-Way NDMP backup failing after rebooting Data Domain VTL
  • Dell NetWorker showing Data Domain VTL as offline status however from within Data Domain VTL, it is showing healthy status.
  • Dell Unity could not discover any devices presented from Data Domain VTL.

After rebooting Data Domain VTL, Dell Unity displaying LUNZ and with no Data Domain VTLs detected on the probe as shown below:

# svc_nas ALL -devconfig -list -scsi -nondisks
SVDM_A :
Scsi device table
name            addr            type            info
? LUNZ             ! 0000000000CL  jbox  DGC      ?
? LUNZ             ! 0000000000CL  tape  DGC      ?
? LUNZ             ! 0000000000CL  tape  DGC      ?
? LUNZ             ! 0000000000CL  tape  DGC      ?
? LUNZ             ! 0000000000CL  tape  DGC      ?
? LUNZ             ! 0000000000CL  tape  DGC      ?
c33t0l0         c33t0l0            tape        IBM      ULT3580-HH7
c33t0l1         c33t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

SVDM_B :
Scsi device table
name            addr            type            info
c32t0l0         c32t0l0            tape        IBM      ULT3580-HH7
c32t0l1         c32t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

<nas server> :
Scsi device table
name            addr            type            info
? LUNZ             9n 0000000000CL jbox  DGC      ?
? LUNZ             9n 0000000000CL tape  DGC      ?
? LUNZ             9n 0000000000CL tape  DGC      ?
? LUNZ             9n 0000000000CL tape  DGC      ?
? LUNZ             9n 0000000000CL tape  DGC      ?
? LUNZ             9n 0000000000CL tape  DGC      ?
c33t0l0         c33t0l0            tape        IBM      ULT3580-HH7
c33t0l1         c33t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

Original output from before rebooting Data Domain VTL:

# svc_nas ALL -devconfig -list -scsi -nondisks
SVDM_A :
Scsi device table
name            addr            type            info
c32t0l0         c32t0l0            jbox        STK      L180
c32t0l1         c32t0l1            tape        IBM      ULTRIUM-TD5
c32t0l2         c32t0l2            tape        IBM      ULTRIUM-TD5
c32t0l3         c32t0l3            tape        IBM      ULTRIUM-TD5
c32t0l4         c32t0l4            tape        IBM      ULTRIUM-TD5
c32t0l5         c32t0l5            tape        IBM      ULTRIUM-TD5
c33t0l0         c33t0l0            tape        IBM      ULT3580-HH7
c33t0l1         c33t0l1            jbox        IBM      3573-TL          0055L3A7800T6A
c34t0l0         c34t0l0            tape        IBM      ULT3580-HH7
c34t0l1         c34t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

SVDM_B :
Scsi device table
name            addr            type            info
c32t0l0         c32t0l0            tape        IBM      ULT3580-HH7
c32t0l1         c32t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

<nas server> :
Scsi device table
name            addr            type            info
c32t0l0         c32t0l0            jbox        STK      L180
c32t0l1         c32t0l1            tape        IBM      ULTRIUM-TD5
c32t0l2         c32t0l2            tape        IBM      ULTRIUM-TD5
c32t0l3         c32t0l3            tape        IBM      ULTRIUM-TD5
c32t0l4         c32t0l4            tape        IBM      ULTRIUM-TD5
c32t0l5         c32t0l5            tape        IBM      ULTRIUM-TD5
c33t0l0         c33t0l0            tape        IBM      ULT3580-HH7
c33t0l1         c33t0l1            jbox        IBM      3573-TL          0055L3A7800T6A
c34t0l0         c34t0l0            tape        IBM      ULT3580-HH7
c34t0l1         c34t0l1            jbox        IBM      3573-TL          0055L3A7800T6A

 

Cause

User added additional physical tape devices and zoned them to using same Dell Unity FC initiator port assigned for Data Domain VTL use.

 

Resolution

Remove the additional physical tape device with Dell Unity FC initiator port zone to resolve this issue.

 

Additional Information

As per the Data Domain VTL best practice guide:
Data Domain: Virtual Tape Library Best Practices Guide

VTL Components
Initiators:

  • It is required that the FC initiator port must be dedicated to only Data Domain VTL devices.
  • Only initiators that must communicate with a particular set of VTL target ports on a Data Domain system should be zoned with that Data Domain system.
  • Create a useful alias for every initiator you zone and connect to the Data Domain system, preferably including the hostname and port in the alias name.
  • Use only one-to-one zoning; create zones on your Fibre Channel switch composed of only one initiator and one target per zone.

 

Affected Products

Dell EMC Unity Hybrid
Article Properties
Article Number: 000184423
Article Type: Solution
Last Modified: 26 Jun 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.