Forum Discussion

john10's avatar
john10
Level 6
11 years ago
Solved

Backup is failing with status 156

HI All,

we are using w2k8 with NBU 7.0 as Master/Media/Client as same server, and coming to incremental backup is running fine, but coming to full backup D:\ is failing with 156 every week, and if we restart the backup manually  mostly its completing, for the same i'm attaching some logs, could any one help me on this ?

Total disk space:- 1.6 TB

free space 163 GB

Failed job details:-

1/6/2015 3:07:42 PM - requesting resource
1/6/2015 3:07:42 PM - requesting resource
1/6/2015 3:07:42 PM - requesting resource
1/6/2015 3:07:42 PM - granted resource 
1/6/2015 3:07:42 PM - granted resource 
1/6/2015 3:07:42 PM - granted resource 
1/6/2015 3:07:42 PM - granted resource IBM.ULTRIUM-HH5.000
1/6/2015 3:07:42 PM - granted resource 
1/6/2015 3:07:45 PM - estimated 1157183374 Kbytes needed
1/6/2015 3:07:54 PM - mounting 09I161
1/6/2015 3:08:01 PM - mounted; mount time: 00:00:07
1/6/2015 3:08:01 PM - positioning to file 28
1/6/2015 3:08:24 PM - connecting
1/6/2015 3:08:24 PM - connected; connect time: 00:00:00
1/6/2015 3:08:24 PM - positioned ; position time: 00:00:23
1/6/2015 3:08:24 PM - begin writing
1/6/2015 3:14:38 PM - Warning bpbrm(pid=28808) from client .: WRN - can't open file: D:\BACKUP OLD SERVER\Drive C\GHS\ppc424\rtserv.exe (WIN32 5: Access is denied. )
1/7/2015 5:10:28 AM - Warning bpbrm(pid=28808) from client: WRN - can't open file: D:\DeptData\HSEF\From Sharedata\SECURITY\ACCESS CARD & FP\FINGER PRINT\att_setup(3.6.6 build 9)\ZK6000\setup.exe (WIN32 5: Access is denied. )
1/7/2015 5:34:39 AM - Warning bpbrm(pid=28808) from : WRN - can't open file: D:\DeptData\IS\Public\Temporary\Runner 10.6\Program Files\Winshuttle\Winshuttle Runner\TRANSACTIONRunner\TxRunnercom.exe (WIN32 5: Access is denied. )
1/7/2015 5:37:35 AM - Warning bpbrm(pid=28808) from client : WRN - can't open file: D:\DeptData\IS\Public\Temporary\WinShuttle Installs\Runner 10.6\Program Files\Winshuttle\Winshuttle Runner\TRANSACTIONRunner\TxRunnercom.exe (WIN32 5: Access is denied. )
1/7/2015 6:01:22 AM - Warning bpbrm(pid=28808) from client : WRN - can't open file: D:\DeptData\MQ\MQ OPERATIONS\Pcsx2_0.9.1_Setup\Pcsx2_0.9.1_Setup.exe (WIN32 5: Access is denied. )
1/7/2015 8:41:50 AM - Warning bpbrm(pid=28808) from client : WRN - can't open file: D:\Drivers\Fuji Xerox Printer\Fuji Xerox 340A\EzInst\VerUp.exe (WIN32 5: Access is denied. )
1/7/2015 9:37:47 AM - Error bpbrm(pid=28808) from client ERR - failure reading file: D:\Program Files\Veritas\NetBackup\logs\nbpem\51216-116-713909151-150106-0000000000.log (WIN32 2: The system cannot find the file specified. )
1/7/2015 9:37:48 AM - Error bpbrm(pid=28808) from client .com: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy148\Program Files\Veritas\NetBackup\logs\nbpem\51216-116-713909151-150106-0000000000.log 
1/7/2015 9:37:48 AM - Critical bpbrm(pid=28808) from client FTL - Backup operation aborted!     
1/7/2015 9:37:55 AM - end writing; write time: 18:29:31
snapshot error encountered(156)

 

No error found in VSS O/P:-

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>d:

D:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {a231cb46-acb4-4b9b-8ca8-43388549f790}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {beb81556-a11d-44b6-ab1c-89b6699995e3}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {7641ecd4-fa93-43c5-a970-0535c2f07f1c}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {0f726edc-b4ae-44c3-bfbf-1bfea82c4e15}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {3ff6406f-4c87-474e-9628-040c33a0c9e4}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {c50b3e2c-9709-428c-bf1b-2b0ff5cf68ac}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {90547797-533f-4ef2-a637-1db89b16b73e}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {db8fc78b-317a-43a2-b985-0dfb1a0fac5f}
   State: [1] Stable
   Last error: No error


D:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7


 

 

  • Backup should NOT fail with 156 if Snapshot error control is set to 'Disable Snapshot and continue'.
    Ensure the Client name in Client Attributes is exactly the same as in the policy.

    Permission issues on the client should cause status 1, not 156.

    Please show us bpfis and bpbkar logs on the client. Upload logs as .txt File attachments.
    Also show us output of this command on the master:
    bpclient  -client <client_name> -L