NetBackup 7.5 produces Status 156 on the inactive node of a Windows 2008 cluster

  • Modified Date:
  • Article ID:000081391


This issue was initially reported in 6.5.2 and documented in TECH128805 - bpbkar32.exe faults on the inactive node of a Windows 2008 cluster (linked below).

It was formally resolved in with the aid of a new -ignore_unresolved_volumes switch for w2koption.

However, starting in 7.5 GA, although the w2koption command still exists and runs without error, it no longer prevents a Shadow Copy Components backup from attempting to snapshot the absent volume.

Error Message

Activity Monitor = Status Code: 156

The below snips come from bpbkar captured using Client side logging at General Level 2:

It acknowledges that the correct w2koption command was run correctly:
11:02:51.712 AM: [2076.2516] <2> tar_base::V_vTarMsgW: WRN - You have chosen to ignore unresolved volumes for Shadow Copy Components backups. Your backup will exit status zero even if the following volumes cannot be resolved E:  

However, upon discovering the unresolved volume, the job ends with Status Code 156:
11:03:02.243 AM: [2076.2516] <2> ov_log::V_GlobalLog: INF - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) for object 'System Files'.  Faild to resolve volume path name for 'e:\program files\symantec\netbackup dlo\' in SHADOW::SetSelectedForBackup

11:03:02.243 AM: [2076.2516] <2> tar_base::V_vTarMsgW: ERR - Volume resolution error for (System State:\System Files\System Files)
11:03:02.259 AM: [2076.2516] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encountered


This issue is exclusive to Windows 2008 and Windows 2008 R2 NetBackup Clients.
The sequence of events which cause this error are:
1.  On a NetBackup Client, an application installation creates a Service with a "Path to executable" that points to a non-local volume.
2.  The NetBackup Client can be a node in a cluster
3.  When the machine is the Passive Node in the cluster, the non-local volume which the Service points to, is no longer present on the Operating System
4.  A Shadow Copy Components backup is run on the Passive Node in the cluster
Newly in Windows 2008 and Windows 2008 R2, every "Path to Executable" for every Windows Service is cataloged into the VSS System Writer and is therefore backed up by Shadow Copy Components.  When a Shadow Copy Components backup starts, all of the VSS Writers are interrogated to compile a list of Volumes on which files classified into Shadow Copy Components reside - then Microsoft takes a Snapshot of those volumes.
The Microsoft Volume Shadow Copy service is unaware that the node is Passive and the drive letter for the Service is not present.  NetBackup attempts to snap the absent volume and an unexpected error occurs.


The formal resolution for this issue (Etrack 3013200) is included in the following release:

  • NetBackup 7.5 Maintenance Release 5 (

NetBackup is now available - please access the Related Article below for more information.

Once the problem host has been upgraded with the maintenance release, the NetBackup Client Agent will again properly respond to w2koption -backup -ignore_unresolved_volumes and ignore the identified absent volume(s).

Note: This hotfix is no longer publicly available, as all of its fixes are included in the NetBackup Maintenance Release.  If any of these issues are experienced in a NetBackup 7.5.0.x environment, the supported resolution is to apply the maintenance release.

Symantec Bug ID: ET 3013181

Version:  NetBackup_7.5.0.4

Installation Location:  client

Installation Instructions: 
Please follow the EEB Installer instructions available on

Package Contents:
Please choose the appropriate platform after download:
eebinstaller.3013181.1.AMD64.exe Windows x64 Installation
eebinstaller.3013181.1.x86.exe Windows x86 Installation

4185558798 1901568 AMD64/bedsshadow.dll
2529072528 1491968 x86/bedsshadow.dll

Recommended service state:
To ensure proper .dll replacement, all client services should be stopped before installing this EEB.

Applies To

Windows 2008
Windows 2008R2
NetBackup 7.5.x.x

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)