Forum Discussion

T_N's avatar
T_N
Level 6
11 years ago

(156) snapshot error encountered

Hi All,

I have issue with window 2012 client, I am using multiplexing to backup ALL_LOCALL_DRIVES but it failed with status 156 on D drive (child job). Can anyone know how to fix it or hotfix for windown 2012 ?  Here backup job detail:

 

10/10/2014 23:41:13 - Info nbjm (pid=16001) starting backup job (jobid=4571395) for client ghdspwfe3wpl, policy mco_prod_w12_sharepoint_loc, schedule weekly_1mo_ret
10/10/2014 23:41:13 - Info nbjm (pid=16001) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=4571395, request id:{9826AF76-5111-11E4-A19F-3741B621C4E3})
10/10/2014 23:41:13 - requesting resource DXI07_WIN_PRD_REP
10/10/2014 23:41:13 - requesting resource veritas.NBU_CLIENT.MAXJOBS.ghdspwfe3wpl
10/10/2014 23:41:13 - requesting resource veritas.NBU_POLICY.MAXJOBS.mco_prod_w12_sharepoint_loc
10/10/2014 23:41:14 - awaiting resource DXI07_WIN_PRD_REP. No drives are available.
10/10/2014 23:44:48 - granted resource  veritas.NBU_CLIENT.MAXJOBS.ghdspwfe3wpl
10/10/2014 23:44:48 - granted resource  veritas.NBU_POLICY.MAXJOBS.mco_prod_w12_sharepoint_loc
10/10/2014 23:44:48 - granted resource  G70611
10/10/2014 23:44:48 - granted resource  HP.ULTRIUM5-SCSI.231
10/10/2014 23:44:48 - granted resource  ghdnbk05lps-hcart2-robot-tld-18
10/10/2014 23:44:48 - estimated 119588613 kbytes needed
10/10/2014 23:44:48 - Info nbjm (pid=16001) started backup (backupid=ghdspwfe3wpl_1413009888) job for client ghdspwfe3wpl, policy mco_prod_w12_sharepoint_loc, schedule weekly_1mo_ret on storage unit ghdnbk05lps-hcart2-robot-tld-18
10/10/2014 23:44:48 - started process bpbrm (pid=14834)
10/10/2014 23:44:49 - Info bpbrm (pid=14834) ghdspwfe3wpl is the host to backup data from
10/10/2014 23:44:49 - Info bpbrm (pid=14834) reading file list from client
10/10/2014 23:44:49 - Info bpbrm (pid=14834) starting bpbkar on client
10/10/2014 23:44:49 - connecting
10/10/2014 23:44:49 - connected; connect time: 0:00:00
10/10/2014 23:44:50 - Info bpbkar (pid=46160) Backup started
10/10/2014 23:44:50 - Info bpbrm (pid=14834) bptm pid: 14841
10/10/2014 23:44:50 - Info bptm (pid=14841) start
10/10/2014 23:44:50 - Info bptm (pid=14841) using 262144 data buffer size
10/10/2014 23:44:50 - Info bptm (pid=14841) using 128 data buffers
10/10/2014 23:44:50 - Info bptm (pid=14841) start backup
10/10/2014 23:44:50 - Info bptm (pid=14841) backup child process is pid 14846
10/10/2014 23:44:50 - Info bptm (pid=14841) media id G70611 mounted on drive index 15, drivepath /dev/nst74, drivename HP.ULTRIUM5-SCSI.231, copy 1
10/10/2014 23:44:50 - mounted G70611
10/10/2014 23:44:50 - positioning G70611 to file 2
10/10/2014 23:44:50 - positioned G70611; position time: 0:00:00
10/10/2014 23:44:50 - begin writing
10/10/2014 23:57:33 - Error bpbrm (pid=14834) from client ghdspwfe3wpl: ERR - failure reading file: D:\BlobCache\285403163\wCGc90+AN06QdvIUs79zLg\USER PHOTOS\PROFILE PICTURES\10010265_MTHUMB-rnmJiGhVMk6inVWJj0949w.JPG (WIN32 2: The system cannot find the file specified. )
10/10/2014 23:57:34 - Error bpbrm (pid=14834) from client ghdspwfe3wpl: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy325\BlobCache\285403163\wCGc90+AN06QdvIUs79zLg\USER PHOTOS\PROFILE PICTURES\10010265_MTHUMB-rnmJiGhVMk6inVWJj0949w.JPG
10/10/2014 23:57:34 - Critical bpbrm (pid=14834) from client ghdspwfe3wpl: FTL - Backup operation aborted!
10/10/2014 23:57:34 - Error bptm (pid=14846) system call failed - Connection reset by peer (at child.c.1298)
10/10/2014 23:57:34 - Error bptm (pid=14846) unable to perform read from client socket, connection may have been broken
10/10/2014 23:57:34 - Error bptm (pid=14841) media manager terminated by parent process
10/10/2014 23:57:35 - Error bpbrm (pid=14834) could not send server status message
10/10/2014 23:57:35 - Info bpbkar (pid=46160) done. status: 156: snapshot error encountered
10/10/2014 23:57:35 - end writing; write time: 0:12:45
10/11/2014 00:00:05 - job 4571395 was restarted as job 4571523
snapshot error encountered  (156)

Agents
Backing Up
Backup and Recovery
Error messages
NetBackup
Tip-How to
Windows Server (2003-2008)
  • Nicolai's avatar
    Nicolai
    Moderator
    11 years ago

    my guess is that VSS is running out of space, take a look at the tech note below.

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

    It's writte for hyper-V backup but work on phycial host as well - the main topic is the VSS limit.

  • Pangal's avatar
    Pangal
    Level 5
    11 years ago

    Hi,

               In addition to Nicolai post could you pls post the following results

              What is the version of netbackup

              Could you post the output of of vssadmin list writers and vssadmin list shadows

                Possible reasons it mite be referring to old snapshot during backup

     

     

     

     

     

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    11 years ago

    As it seems to be a cache it might not need to be backed up, then a solution could be to exclude the BlobCache from the backup