Partial backup for shadow copies

[Rithesh]

HI All,

My daily backup has nearly 45 partial success.
Most of these partial backup is for shadow copies.
I currently using VSS for snapshot.

Following are the details

ERR - failure reading file: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE000FEDF: A failure occurred reading an object.)
4/22/2009 12:04:04 AM - Warning bpbrm(pid=4768) from client : WRN - can't open object: Shadow Copy Components:\System State\Registry\Registry (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
4/22/2009 12:04:04 AM - Warning bpbrm(pid=4768) from client : WRN - can't open object: Shadow Copy Components:\System State\COM+ Class Registration Database\COM+ REGDB (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
4/22/2009 12:04:05 AM - Warning bpbrm(pid=4768) from client  WRN - can't open object: Shadow Copy Components:\System State\Internet Information Services\IISMETABASE (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
4/22/2009 12:04:05 AM - Warning bpbrm(pid=4768) from client : WRN - can't open object: Shadow Copy Components:\System Service\Windows Management Instrumentation\WMI (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
4/22/2009 12:04:05 AM - Warning bpbrm(pid=4768) from client  WRN - can't open object: Shadow Copy Components:\System Service\Event Logs\Event Logs (BEDS 0xE000FEDD: A failure occurred accessing the object list.)

Nbu server is 6.5.2
agent is 6.5.2a.
Os- win 2k3

Please advice how to reduce the partial success.

Thanks in advance

Ritz

[Anton_Panyushki]

There are a number of reasons that might cause these errors:

1) Windows Registry on the client is corrupted. Please check Windows System Log for more information.
2) New patched have been recently installed on a client and host was not rebooted. Reebot host.
3) Hard disk problems on a client.   

[quebek]

Has this OS installed at least Service Pack 1???
Please check this out, this is important to have this pack in place.

[Rithesh]

Almost all servers are with SP1 win 2k3.
I also tried to register back VSS with MS specified commands.
But no luck.


Regards
Ritz

[rj_nbu]

HI

can you post the output of these commands

vssadmin list writers
vssadmin list providers

Also, are there any errors in the event viewer logs ?

Check this technote
http://seer.entsupport.symantec.com/docs/280671.htm



-Rajeev

[Rithesh]

Hi,

Thanks for the input

Most of the partials occurs for the following one's

WRN - can't open object: Shadow Copy Components:\System Service\Removable Storage Manager\Removable Storage Manager (BEDS 0xE000FED1: A failure occurred querying the Writer status.)

Eventhough i added an exclusion, still this coming up.

Following are the vss output.

C:\>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


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

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {7623e97a-b449-48ae-a1b6-890fbdab9d3c}
State: [7] Failed
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {5e821691-5a50-4e39-b775-a793e22b4ec5}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {67cf55d0-d328-4a6e-a91f-51e81f6fe8be}
State: [1] Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {eec624da-33ab-4050-b567-d423921219f4}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {2263670a-e0ee-4e50-9ea1-39c9375c1b89}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {91213e7e-8668-4d07-ba72-c9c936547d36}
State: [7] Failed
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {e5496aed-48b0-4877-bebe-bcc765b051da}
State: [7] Failed
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {de0cbbed-9fda-4b99-8768-7293c3cff578}
State: [1] Stable
Last error: No error


Please advice

Ritz

[rj_nbu]

 It is just a warning and can be ignored. This service is installed on windows 2000 and 2003 servers by default and is used in device management (Tape drives).

it is recommended to disable this service on the media server.

http://seer.entsupport.symantec.com/docs/245559.htm


-Rajeev