A potential for data loss where a backup of an NDMP filer with multiple file-directives succeeded

A potential for data loss where a backup of an NDMP filer with multiple file-directives succeeded

Article: 100045070
Last Published: 2019-04-05
Ratings: 4 1
Product(s): Appliances, NetBackup


Potential Data Loss



Affects versions of NetBackup 7.7.3 and lower

During the NDMP backup of a policy file-directive, the list of files in the volume is recorded in the catalog, but due to an NDMP error condition, NetBackup skips these affected files and the data is not written to the media. 

In this scenario, NetBackup did not respond to the filer problem and records a successful status code 0 for the backup.

When restoring a file from one of the affected volumes the following error is encountered.

NDMP policy restore error  (2813)


Action Required

Upgrade any media servers writing NDMP images to NetBackup 8.0 or later.


How to Determine if Affected:

Confirm NDMP backups were taken using NetBackup 7.7.3 or older, using multiple file directives in the Backup Selection.

The root cause is indeterminate at this time, and may be related to interactions with specific NDMP filer versions.  To date the problem has been encountered once with a NetApp v8.2.1 filer, but all NDMP backups that used multiple file directives should be checked to confirm they are not affected.

A modified version of the utility cat_convert is available at NetBackup version 8.1 as an EEB that can detect the problem.  The utility is run on each NetBackup image catalog files file (*.f).  The utility can detect the signature of the missing volumes.


Formal Resolution:

The formal resolution to this issue is included in the following NetBackup releases:

  • NetBackup Server/Enterprise Server 8.0
  • NetBackup Appliance 3.0


Restore the file from a different backup image unaffected by this rare problem.

Best Practices:

Veritas strongly recommends the following best practices:

  1. Always perform a Full backup prior to and after any changes to your environment.
  2. Always make sure that your environment is running the latest version and patch level.
  3. Perform periodic "test" restores.
  4. Subscribe to technical articles.


Etrack : 3872050 Etrack : 3962701

Was this content helpful?