Status 156 ERR - Volume resolution error for (System State:\System Files\System Files)

Problem

Error may occur on:

- non-clustered Windows servers when a file path exists in the registry for a drive letter and file path that no longer exist.  (Typically due to a software package that was not uninstalled, or server was cloned from another server with different disk configuration)

- the file name or path is empty

- the passive node of a Windows clustered server  

Error Message

Detailed status of job:

<time stamp> - Error bpbrm (pid=xxxxx) from client xxxxxxxx; ERR - Volume resolution error for (System State:\System Files\System Files)

bpbkar log with GENERAL Level 2 and VERBOSE Level 5:

---------------------------------------------------------------------------------------------------------

.
<2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = Shadow Copy Components:\
.
<2> ov_log::V_GlobalLog: INF - Could not resolve volume path name for 'e:\mysql\bin' when getting file descriptors
.
<2> ov_log::V_GlobalLog: INF - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) processing file path e:\mysql\bin when getting file descriptors
<16> dos_backup::V_InitializeSystemState: ERR - FS_AddToSnapshotSet() Failed! (System State:\System Files\System Files) $s
<2> tar_base::V_vTarMsgW: ERR - Volume resolution error for (System State:\System Files\System Files)
.
<2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encountered

---------------------------------------------------------------------------------------------------------

Cause

The system registry contains a file path for a drive letter that no longer exists or is empty.

OR:

In the clustered scenario, the passive node does not have access to the shared drive(s).  Any shadow copy components that reside on the shared drive(s) (such as SQL server system components) will not be accessible by the snapshot writer/provider, and it cannot be frozen, which returns the 156 status code.

Solution

Use the NetBackup command w2koption on the client to ignore the problem volume drive letter noted in the bpbkar log ( e:\path ).

Example for log above:

<install path>\netbackup\bin\

         w2koption -backup -ignore_unresolved_volumes E: 

or for the case of the file path or name being empty

         w2koption -backup -ignore_unresolved_volumes null: 

If the backup finds other unresolved volumes, run the command with multiple volume letters:     

         w2koption -backup -ignore_unresolved_volumes x:y:z:

To view the result:  w2koption -backup -display

To clear the unresolved volume list:  

           w2koption -backup -ignore_unresolved_volumes