Sun ZFS Storage 7420
 
Sun Storage 7110 Unified Storage System
 
Oracle ZFS Storage ZS3-2
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun Storage 7410 Unified Storage System
 
Sun ZFS Storage 7120
 
Sun Storage 7310 Unified Storage System
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7320
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Oracle ZFS Storage ZS3-BA
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
 

In this Document

Goal

Solution

Identifying NDMP type issues

Frame and describe the problem

Data collection

References

Applies to:

Goal

Preliminary work to identify NDMP type issues, gather necessary information and data for further analysis. Further data collection may be required depending on the nature of the problem.

Solution

Identifying NDMP type issues

- NDMP type issues are generally identified when backup software has failed, when errors/warnings are generated, or a backup/restore is performing slowly.
On the ZFS Storage Appliance perform general checks to ensure non-NDMP components are working. If necessary resolve any issue seen and then revisit NDMP issues.

Typical ndmp errors may appear similar to the example below:

Frame and describe the problem

Describe the problem as seen on ZFS Storage Appliance and on the Data Management Application (DMA) backup software.

• Include backup/restore detail activities with a date and time stamp when the problem is observed.
• Include any recent changes on all backup/restore components that involve ZFS Storage Appliance.
• Include recent changes including firmware/software updates, hardware components, configuration, TCP/IP network and/or Fibre Channel storage area network for FC connected tape system. When possible, include the procedure to reproduce the problem.

- On DMA backup software

• Activities and errors/warning seen including logs and executed commands
• Consult DMA manuals and engage vendors as required

Data collection

List of general information and data that needs to be collected.
Further data is possible depending on the nature of the problem.

1. Include problem identification as per the above.
2. Collect ZFS Storage Appliance supportbundle using Document 1019887.1  How to collect supportfile bundle using the BUI or CLI
3. DMA errors, warning, failed commands and where applicable include DMA vendor analysis.
4. Network packet capture between DMA backup software and ZFS storage appliance (*).  See Document 1398376.1  "Sun Storage 7000 Unified Storage System: How to get a network trace to assist in troubleshooting network problems" for further details on this.
5. Capture analytics data for ZFS storage appliance NDMP performance
6. Other data can be collected under supervision of Oracle engineer.

Depending on the problem, you may need to capture more data before collecting a supportbundle

 *  for suspected ndmp code

 *  Capture ndmp debug when escalating to engineering.

Starting with the 2011.1.1.0 appliance code, ndmp logging is always enabled (CR 6908633). The log is available at /var/ak/logs/ndmp/ndmplog.

 *  Capture network snoop between DMA and ZFS Storage Appliance.

Preferably from an external device to the ZFS Storage Appliance, but if required capture a network trace from the ZFS Storage Appliance itself. See Document 1398376.1  Sun Storage 7000 Unified Storage System: How to get a network trace to assist in troubleshooting network problems.

(*) By default NDMP uses TCP/IP port 10000. NDMP version 4 can be configured to use a different port number.
Include a network packet trace output when the issue falls in these scenarios:

• An interoperability problem between DMA and ZFS Storage Appliance
• The DMA vendor analysis implicates the ZFS Storage Appliance
• The backup procedure uses remotely connected tape library and drives

Back to NDMP troubleshooting resolution path Document 1387930.1

References

This solution has no attachment