12-02-2010 03:09 AM
The client have got local drive and SQL backups. SQL backups are running fine, local drive backups are failing with 42. Find below errors on job details;
Dec 1, 2010 11:43:38 PM - Error bpbrm (pid=23515) from client pbnawldbl801-b: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:35630777 58069
Dec 1, 2010 11:43:38 PM - Error bptm (pid=23526) system call failed - Connection reset by peer (at child.c.1296)
Dec 1, 2010 11:43:39 PM - Error bptm (pid=23526) unable to perform read from client socket, connection may have been broken
Dec 1, 2010 11:43:39 PM - Error bpbrm (pid=23515) from client pbnawldbl801-b: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
Dec 1, 2010 11:43:41 PM - Critical bpbrm (pid=23515) unexpected termination of client pbnawldbl801-b
Dec 1, 2010 11:49:41 PM - end writing; write time: 0:06:28
network read failed (42)
If we took a backup of all the local drives individually, backup is running fine. Shadow copy creates problems.
Enabled logging on client side and bpbkar logs talks as below
3:35:27.384 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - Looking for esebcli2.dll in sysetm path
3:35:27.384 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - never found EseBcli2.dll
3:35:27.384 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - esebcli2.dll not loaded
3:35:27.384 AM: [5624.4540] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = Shadow Copy Components:\
3:35:27.400 AM: [5624.4540] <2> tar_backup_vxbsa::add: INF - called with 'Shadow Copy Components:\'
3:35:27.400 AM: [5624.4540] <4> dos_backup::V_VerifyFileSystem: INF - Verifying: Shadow Copy Components:\
3:35:27.400 AM: [5624.4540] <4> dos_backup::V_VerifyFileSystem: INF - Added: System State:\
3:35:27.431 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) returned gathering Writer metadata when initializing shadow copy
3:35:27.431 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - AD:Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) attaching 'Shadow?Copy?Components' in SystemState::InitializeShadowCopy:275
3:35:27.431 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - AD:Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) initializing Shadow Copy in SystemState::AttachToDLE:470
3:35:27.431 AM: [5624.4540] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x1 Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata.)
3:35:27.431 AM: [5624.4540] <2> ov_log::V_GlobalLog: INF - v_beds::V_FindFirst() EXIT Name: bRC:false LastError:0xFFFFFEC9:0xa000fec9 (2684419785)
3:35:27.462 AM: [5624.4540] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:Shadow Copy Components:
3:35:27.462 AM: [5624.4540] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'Shadow Copy Components:\' --> 00000000
3:35:28.259 AM: [5624.4540] <2> tar_base::V_vTarMsgW: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.3:35:28.259 AM: [5624.4540] <4> tar_backup_tfi::determineEstimate: INF - job tracking estimate: stop
I am not sure, we need to start concentrate on dll missing errors or check the VSS state on client.
The dll missing (never found EseBcli2.dll & VirtApi DLL WAS NOT LOADED), are these related to backup ??
Master Server Version :- RS6000 AIX5, NetBackup 6.5.4
Client Version :- Windows2003 5, NetBackup 6.5.4
Solved! Go to Solution.
12-03-2010 07:45 AM
On the client....
Use:
vssadmin create shadow /FOR=C:\
Then:
vssadmin list shadow /FOR=C:\
Then if it exsits and its worked use:
vssadmin delete shadows /FOR=C:\
Check its gone:
vssadmin list shadow /FOR=C:\
Make sure the cleint has the VSS option selected in the Master server properties and not VSP.
Apply SP2 to the winodws server.
Make sure this service is disabled: Veritas VSS Provider
Try and make a shadow copy of all drives at once, does that work or do you run out of space?
Post how you get on........
12-02-2010 06:18 AM
VSS is a Windows components Netbackup is calling. Backup of Shadow Copy Components is perfromed by VSS only. I am not a Windows admin but I would check the state of the VSS writer as one of the first things.
What does "vssadmin list writers" return ?
12-02-2010 06:25 AM
I checked this, it looks fine
C:\Documents and Settings\mk>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {c38a3084-e020-4cc4-b4c2-e20b0d6653dc}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {83042e18-e1a8-4aee-a24f-a8d2b8b2c9ee}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {967dd3fa-44c9-4726-9924-5ac8a474f578}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {974be027-4644-4b3d-95ba-c86419c836b7}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {14fe4ec5-7732-4607-b498-e1166cb0978a}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {026d1c03-ffb4-473f-8a6a-70ec26952534}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {86d2351f-1a11-4a45-ab90-c2e74204876c}
State: [1] Stable
Last error: No error
C:\Documents and Settings\mk>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 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
12-03-2010 01:51 AM
You first try to take snapshot of Drive from windows .
12-03-2010 07:45 AM
On the client....
Use:
vssadmin create shadow /FOR=C:\
Then:
vssadmin list shadow /FOR=C:\
Then if it exsits and its worked use:
vssadmin delete shadows /FOR=C:\
Check its gone:
vssadmin list shadow /FOR=C:\
Make sure the cleint has the VSS option selected in the Master server properties and not VSP.
Apply SP2 to the winodws server.
Make sure this service is disabled: Veritas VSS Provider
Try and make a shadow copy of all drives at once, does that work or do you run out of space?
Post how you get on........
01-15-2011 08:12 AM
Hi, I am also have the same problem of can't create a snapshot problem.
When the system restart, I can create a snapshot in Shadow Copies in drive properties. But after a while (using Netbackup and BESR backup), it will fail to create a snapshot. I am not sure Netbackup or BESR to make this problem.
It is no error in the "vssadmin list writers", and the "vssadmin list providers" is shows:
vssadmin 1.1 - Volume Shadow Copy Service administartive command - line tool
<C> Copyright 2001 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provdier Id: <XXXX>
Version: 1.0.0.7
I will try to disable the Veritas VSS Provdier service and create snapshot...
01-16-2011 12:24 AM
Crossverify the below mentioned services , this sould be in manual state .
"Microsoft Software Shadow Copy Provider"
"Volume Shadow Copy"
01-16-2011 12:43 AM
It's make sense to check if you have enough cache space on your disks allocated for Shadow Copies
02-25-2011 12:23 PM
thanks all