System state backup failure
Created: 28 May 2012 | 6 comments
Hi guys
client server win 2008 NBU version 6.5.6 its system state backup always fails.
volume shadow copy and microsoft software shadow copy provider service were set to auto n start but once backup starts it shows both services not running only set as auto.
eventvwr do not show any error only found this :The VSS service is shutting down due to idle timeout ????
NBU GUI :
5/29/2012 12:32:02 AM Warning bpbrm(pid=7080) from client clientbox: WRN - can't open file: System State:\Automated System Recovery\Volumes\Volume{7f838852-f192-11df-bcdc-806e6f6e6963} (WIN32 536935992: Unknown error)
5/29/2012 12:32:02 AM - Warning bpbrm(pid=7080) from client clientbox: WRN - can't open file: System State:\Automated System Recovery\Volumes\Volume{7f838853-f192-11df-bcdc-806e6f6e6963} (WIN32 536935992: Unknown error)
5/29/2012 12:32:02 AM - Error bpbrm(pid=7080) from client clientbox: ERR - Error encountered while attempting to get additional files for System State:\
created bpbkar bpfis n bpcd logs
but bpfis folder is empty ?????
C:\>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
C:\>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: {1fcb1c15-8c6c-4fe1-80ce-d358270a0dcb}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {0067f74a-a46b-4cae-bd70-bf28e4135ff8}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {a1a60187-48ae-4d7c-bcce-c57208f5212b}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {36ecd48b-ded0-47f2-98d1-38fdce83c654}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {b254d912-0d35-4151-9fd4-5e36464ce9a1}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {47d776bd-31bd-4cd8-b6c1-daf3a781cb61}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {a8fd6265-ee17-4dff-876b-b542a6286030}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {95f40947-3cdf-45e0-83da-283b34928c60}
State: [5] Waiting for completion
Last error: No error
client bpbkar of:
00:47:23.783: [4920.3284] <16> dtcp_read: TCP - failure: recv socket (272) (TCP 10058: Can't send after socket shutdown)
00:47:23.783: [4920.3284] <16> dtcp_read: TCP - failure: recv socket (324) (TCP 10058: Can't send after socket shutdown)
00:47:23.783: [4920.3284] <4> OVShutdown: INF - Closing stderr connection
00:47:23.783: [4920.3284] <2> dtcp_close: TCP - success: close socket (324)
00:47:23.783: [4920.3284] <4> OVShutdown: INF - Closing stdout connection
00:47:23.783: [4920.3284] <2> dtcp_close: TCP - success: close socket (148)
00:47:23.783: [4920.3284] <4> OVShutdown: INF - Closing stdin connection
00:47:23.783: [4920.3284] <2> dtcp_close: TCP - success: close socket (272)
00:47:23.783: [4920.3284] <4> OVShutdown: INF - Finished process
00:47:23.783: [4920.3284] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
00:47:25.783: [4920.3284] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\052912.LOG
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
R2 or not? Hotfix available for 6.5.6.
See TN: http://www.symantec.com/docs/TECH140077
http://www.symantec.com/docs/TECH140074
non-R2: http://www.symantec.com/docs/TECH144723
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
you may also need to disable windows OS firewall on Client (win2k8)
If this post has helped you, please vote or mark as solution.
Before break-up, make sure you have a good backup..... ;-)
For a Windows 2008 client, try using the backup selection directive "shadow copy components" instead of System_State.
"shadow copy components" would backup everything System_State does, and more.
RLeon
@RLeon i have ALL_LOCAL_DRIVE as backup selection so i dont think so using System_State or shadow copy components will help.
Have you checked out hotfixes as per my previous post?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
i will update the hotfix in 1 st week of of june and update this forum
Would you like to reply?
Login or Register to post your comment.