cancel
Showing results for 
Search instead for 
Did you mean: 

snapshot error encountered (156)

SachinSharma
Level 3
One of the Windows 2003 server client has been failing regulary with snapshot error, we are using Microsoft Volume Shadow Copy Service (VSS).

To resolve the issue we increased the space allocated for Shadow copy on the respective volume which is large enough compared to one that was allocated earlier. However it still fails wtih SC: 156. Strangely after we rerun the backup it completes successfully.

ERROR DESCRIPTION -

03/08/2010 17:39:32 - Error bpbrm (pid=8888) from client xyz: ERR - failure reading file: D:\ITL\backup\Data\Datasave_FULL.arc (WIN32 2: Unknown error)
03/08/2010 17:39:33 - Error bpbrm (pid=8888) from client xyz: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy214\ITL\backup\Data\Datasave_FULL.arc
03/08/2010 17:39:35 - Critical bpbrm (pid=8888) from client xyz: FTL - Backup operation aborted!
03/08/2010 17:39:43 - end writing; write time: 1:07:52
03/09/2010 05:14:54 - job 21719 was restarted as job 21721
snapshot error encountered (156)

Master server is on: 6.5.5
Client is on: 6.5 MP5
Client OS: Windows 2003 Standard edition with Service pack 2

Did find the following solution which has been already implemented  - http://seer.entsupport.symantec.com/docs/276739.htm

Thanks.
1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

If you have a double VSS snap of the same drive you may experience the first snap being dissolved. As a workaround you may set Netbackup to continue on snap failures, open files will then be skipped.

# Disable & Continue
bpclient -client {hostname} -add  -WOFB_error 1

View solution in original post

2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified
It seems as if database backups/dumps are being written to local disk on the client. Ensure that backups via NetBackup is not running at the same time as the database dumps. If the database dumps are static (no access/changes) there should be no reason to attempt a snapshot on these files.
Ensure that you have bpfis log to troubleshoot snapshot errors.

Nicolai
Moderator
Moderator
Partner    VIP   

If you have a double VSS snap of the same drive you may experience the first snap being dissolved. As a workaround you may set Netbackup to continue on snap failures, open files will then be skipped.

# Disable & Continue
bpclient -client {hostname} -add  -WOFB_error 1