cancel
Showing results for 
Search instead for 
Did you mean: 

Windows 2008 fails with 156:ERR - Volume resolution error for (System State:\System Files\System Files)

Sughi
Level 4
Certified

Hi,

I have 7.1.0.2 solaris Master running 7.1.0.2 solaris media servers. I get 156 error for few windows 2008 servers even after disabling open file backup option.

There are no old snaps on these clients.

Here is the log  for  a server where backup fails

01/16/2012 03:10:58 - Error bpbrm (pid=5749) from client XXXXX: ERR - Volume resolution error for (System State:\System Files\System Files)

01/16/2012 03:11:01 - Error bptm (pid=5866) media manager terminated by parent process

 

01/16/2012 03:11:21 - Info bpbkar (pid=7500) done. status: 156: snapshot error encountered
 
01/16/2012 03:11:21 - end writing; write time: 0:01:06
 
snapshot error encountered  (156)
5 REPLIES 5

Mark_Solutions
Level 6
Partner Accredited Certified

Sounds very much like this one:

http://www.symantec.com/docs/TECH162645

Sughi
Level 4
Certified

This tech note is fine if we have open file backup option enabled.

I have already disabled open file backup option. But not sure why it uses shadow copy.

I am now worried if my changes are not refelecting on master server.

 Dynamic Address:       no

 

 Free Browse:   Allow
 List Restore:  Not Specified
 Max Jobs This Client:  Not Specified
 WOFB Enabled:  no
 WOFB FIM:      VSP
 WOFB Usage:    Individual Drive Snapshot
 WOFB Error Control:    Abort on Error
 Client Direct: Deduplication on the media server or
                Move data via media server
 Client Direct Restore: Move data via media server
 OST Proxy:     Off
 OST Proxy Server:      Unspecified
Connect options:        2 2 3
 Offline:       No

Mark_Solutions
Level 6
Partner Accredited Certified

Rather than trying to back up open files this is just happening when trying to back up the Shadow Copy Components (The System State)

I believe VSS gets involved anyway when backing it up

Nicolai
Moderator
Moderator
Partner    VIP   

The only supported way to backup ShadowCopyComponents is via VSS. It's a Windows API Netbackup is calling by the way.

Pritesh_Pisal
Level 5
Partner Accredited
make sure your all VSS writers are in stable state during the backup,just check the output of the following command vssadmin list writers