In NetBackup 7.7.x, System State restores fail when attempted from synthetic full backups.

  • Article ID:100032521
  • Modified Date:
  • Product(s):


Document History:
July 11, 2016: Initial publication
August 23, 2016: Hotfix available, attached to article

When creating a synthetic full backup of a file system, all the recent incremental backups are merged with the most recent full backup to create a new full.  When creating a synthetic full backup of System State, only the most recent backup of System State is collected, even if it is only an incremental backup.  Prior to NetBackup 7.7.1, this was sufficient because System State backups were always full backups.  Starting in NetBackup 7.7.1, incremental backups of System State are no longer full backups as they were in the past.

Because synthetic full backups only use the most recent System State backup and if the System State backup was an incremental backup, the synthetic full backup will be incomplete, even though the backup ended with a Status 0.  This will cause restore failures, including those used for Bare Metal Restore.

This issue affects windows clients backed up with a policy of type MS-Windows at the following versions of NetBackup:

  • 7.7.1
  • 7.7.2
  • 7.7.3

Because System State is at the heart of the issue, policies with the following backup directives are affected:

System State:\
Shadow Copy Components:\

Error Message

Example of the issue:
The synthetic full does not contain any _SharedHardlinkData_ components of System State. The restore job failed with status code 2808 reported.  Here is a portion of the restore progress log: 
15:32:18 ( Found (9) files in (1) images for Restore Job ID
15:32:20 ( Searched (20) files of (9) files for Restore Job ID
15:32:20 (273.001) Restoring from copy 1 of image created 3/28/2016 11:41:34 AM from policy XYZ-BMR-2012
15:32:30 (273.001) INF - Beginning restore from server nbmaster1 to client nbclient2.
15:32:30 (273.001) TAR - System State:\
15:32:32 (273.001) ERR - Aborting restore. System State needs to be restored from FULL backup or as a backup set with FULL first followed by incremental or differential as part of the same job.: System State:\.
15:32:32 (273.001) INF - TAR EXITING WITH STATUS = 0
15:32:32 (273.001) INF - TAR KEPT 0 EXISTING FILES


Veritas Technologies LLC is aware that the above-mentioned issue (Etrack 3874297) is present in the current version(s) of the product(s) mentioned in this article. Veritas is committed to product quality and satisfied customers.  This issue was scheduled to be included in the following release:
  • NetBackup 8.0

When NetBackup 8.0 is available, please access the following link for download and README information:

Please note that Veritas reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Veritas' plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

For NetBackup 7.7.3, download and apply the attached hotfix to all media servers and any affected Windows clients.

For previous versions, if upgrade to NetBackup 7.7.3 and applying the hotfix is not possible, the only workaround is to NOT use Synthetic backups for System State.

Hotfix information:

Veritas Bug ID: ET 3890720

Version:  NetBackup_7.7.3

Installation Location:  servers and Windows clients

Installation Instructions: Please follow the EEB Installer instructions available on

Package Contents:
Please choose the appropriate platform after download:
eebinstaller.3890720.1.hpia64       HP-UX Itanium Installation
eebinstaller.3890720.1.linuxR_x86   RedHat x64 Installation
eebinstaller.3890720.1.linuxS_x86   Suse x64 Installation
eebinstaller.3890720.1.rs6000       AIX Installation
eebinstaller.3890720.1.solaris      Solaris SPARC Installation
eebinstaller.3890720.1.solaris_x86  Solaris x64 Installation
eebinstaller.3890720.1.zlinuxR      Redhat zLinux Installation
eebinstaller.3890720.1.zlinuxS      Suse zLinux Installation
eebinstaller.3890720.1.AMD64.exe    Windows x64 Installation

3827014739 12161471 linuxR_x86/nbjm
237736994 3426329 linuxR_x86/bpbrm
3407771162 30637822 rs6000/nbjm
2553239564 5733813 rs6000/bpbrm
590769009 12323734 zlinuxS/nbjm
2073429451 3620095 zlinuxS/bpbrm
227485183 11313030 linuxS_x86/nbjm
1040227796 3294396 linuxS_x86/bpbrm
1453424326 19310848 solaris/nbjm
2296871949 5118880 solaris/bpbrm
3807825057 71787112 hpia64/nbjm
3260064842 14354952 hpia64/bpbrm
3869445378 23535936 solaris_x86/nbjm
2277447107 5843864 solaris_x86/bpbrm
3481011281 13211644 zlinuxR/nbjm
761022835 3776898 zlinuxR/bpbrm
135821222 6034432 AMD64/nbjm.exe
4273587428 1606656 AMD64/bpbrm.exe
3462992302 2354176 AMD64/bpbkar32.exe

Recommended service state: Shut down services on the master server before applying.


Was this content helpful?

Get Support