cancel
Showing results for 
Search instead for 
Did you mean: 

Backup failing with error "snapshot error encountered  (156)"

Mehul_Vyas
Level 4

Hello Team,

Backup for one of the server in cluster failing with error 

snapshot error encountered  (156)

Below is the error log details for the job.

Nov 29, 2018 4:11:11 PM - Info nbjm (pid=23308) starting backup job (jobid=26793350) for client atmmwdcdscob2, policy oh306_prd_mo_net_msw_win_su_crebm2400_grp_1, schedule 1m_si_incr
Nov 29, 2018 4:11:11 PM - Info nbjm (pid=23308) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=26793350, request id:{54F6503C-F3AE-11E8-A9A8-3EA05408F03E})
Nov 29, 2018 4:11:11 PM - requesting resource  CREBM2400_FS
Nov 29, 2018 4:11:11 PM - requesting resource  crebm2400.NBU_CLIENT.MAXJOBS.atmmwdcdscob2
Nov 29, 2018 4:11:11 PM - requesting resource  crebm2400.NBU_POLICY.MAXJOBS.oh306_prd_mo_net_msw_win_su_crebm2400_grp_1
Nov 29, 2018 4:11:11 PM - granted resource  crebm2400.NBU_CLIENT.MAXJOBS.atmmwdcdscob2
Nov 29, 2018 4:11:11 PM - granted resource  crebm2400.NBU_POLICY.MAXJOBS.oh306_prd_mo_net_msw_win_su_crebm2400_grp_1
Nov 29, 2018 4:11:11 PM - granted resource  O2C03I
Nov 29, 2018 4:11:11 PM - granted resource  OH1DF7C3R4
Nov 29, 2018 4:11:11 PM - granted resource  crems2406_hcart3_tld0
Nov 29, 2018 4:11:11 PM - estimated 0 kbytes needed
Nov 29, 2018 4:11:11 PM - Info nbjm (pid=23308) started backup (backupid=atmmwdcdscob2_1543479071) job for client atmmwdcdscob2, policy oh306_prd_mo_net_msw_win_su_crebm2400_grp_1, schedule 1m_si_incr on storage unit crems2406_hcart3_tld0
Nov 29, 2018 4:11:12 PM - Info bpbrm (pid=67562) atmmwdcdscob2 is the host to backup data from
Nov 29, 2018 4:11:12 PM - Info bpbrm (pid=67562) telling media manager to start backup on client
Nov 29, 2018 4:11:12 PM - Info bptm (pid=67651) using 524288 data buffer size
Nov 29, 2018 4:11:12 PM - Info bptm (pid=67651) using 128 data buffers
Nov 29, 2018 4:11:13 PM - Info bpbrm (pid=67562) spawning a brm child process
Nov 29, 2018 4:11:13 PM - Info bpbrm (pid=67562) child pid: 72510
Nov 29, 2018 4:11:13 PM - Info bpbrm (pid=67562) sending bpsched msg: CONNECTING TO CLIENT FOR atmmwdcdscob2_1543479071
Nov 29, 2018 4:11:13 PM - connecting
Nov 29, 2018 4:11:14 PM - Info bpbrm (pid=67562) start bpbkar on client
Nov 29, 2018 4:11:14 PM - connected; connect time: 0:00:00
Nov 29, 2018 4:11:14 PM - begin writing
Nov 29, 2018 4:11:21 PM - Info bpbkar (pid=9500) Backup started
Nov 29, 2018 4:11:21 PM - Info bpbrm (pid=67562) Sending the file list to the client
Nov 29, 2018 4:11:21 PM - Info bpbkar (pid=9500) change time comparison:<disabled>
Nov 29, 2018 4:11:21 PM - Info bpbkar (pid=9500) archive bit processing:<enabled>
Nov 29, 2018 4:11:21 PM - Warning bpbrm (pid=72510) from client atmmwdcdscob2: 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 F:
Nov 29, 2018 4:11:25 PM - Info bpbkar (pid=9500) not using change journal data for <C:\>: not enabled
Nov 29, 2018 4:11:25 PM - Info bpbkar (pid=9500) not using change journal data for <D:\>: not enabled
Nov 29, 2018 4:12:07 PM - Error bpbrm (pid=72510) from client atmmwdcdscob2: ERR - Volume resolution error for (System State:\System Files\System Files)
Nov 29, 2018 4:12:07 PM - Info bpbrm (pid=67562) sending message to media manager: STOP BACKUP atmmwdcdscob2_1543479071
Nov 29, 2018 4:12:08 PM - Info bpbrm (pid=67562) media manager for backup id atmmwdcdscob2_1543479071 exited with status 150: termination requested by administrator
Nov 29, 2018 4:12:08 PM - end writing; write time: 0:00:54
snapshot error encountered  (156).
 

Tried w2koption to ignore unresolved volumes, but still failing.

Client = win2008, NBU version = 7.7.3

Master = Linux, NBU Version = 8.1

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The bug was re-introduced in 7.7.3. 
See https://www.veritas.com/support/en_US/article.000115974

Cause

This is a regression that has been identified in NetBackup 7.7.3.  Prior versions of NetBackup (7.7.1 and 7.7.2) function correctly when using the W2KOption command detailed above.

Solution

Veritas Technologies LLC has acknowledged that the above-mentioned issue (Etrack 3898616) is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.  The formal resolution for this issue was scheduled to be included in the following release:

  • NetBackup 8.0

Workaround:
Download and apply the attached hotfix to all nodes in the cluster.

View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The bug was re-introduced in 7.7.3. 
See https://www.veritas.com/support/en_US/article.000115974

Cause

This is a regression that has been identified in NetBackup 7.7.3.  Prior versions of NetBackup (7.7.1 and 7.7.2) function correctly when using the W2KOption command detailed above.

Solution

Veritas Technologies LLC has acknowledged that the above-mentioned issue (Etrack 3898616) is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.  The formal resolution for this issue was scheduled to be included in the following release:

  • NetBackup 8.0

Workaround:
Download and apply the attached hotfix to all nodes in the cluster.

Thanks Marianne.

 

Will apply the EEB's on clients and update.

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Why not just upgrade Client software?