Forum Discussion

T_N's avatar
T_N
Level 6
10 years ago

backup completed with status 1

Hi All; I am seeing the errors during backup on windows 2012 client.

08/25/2015 22:04:26 - Error bpbrm (pid=3283) from client shdadc01wps: ERR - Error encountered while attempting to get additional files for System State:\
08/25/2015 22:04:26 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\VSS Express Writer Store\WriterMetadataStore (WIN32 -536832991: Unknown error)
08/25/2015 22:04:26 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\Performance Counter\PerformanceCounters (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\System Files\System Files (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\Automated System Recovery\BCD\BCD (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\Registry\Registry (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\SYSVOL\SYSVOL\6192d4f8-e618-456b-ab60f9b8d3028f06 (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\Windows Management Instrumentation\WMI (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Warning bpbrm (pid=3283) from client shdadc01wps: WRN - can't open object: System State:\Active Directory\C:_ADDB\ntds (WIN32 -536832991: Unknown error)
08/25/2015 22:04:41 - Info bpbrm (pid=3283) from client shdadc01wps: TRV - last message being suppressed after 10 occurrences

also when I run vssadmin list providers, it shows:
C:\Program Files\Veritas\NetBackup\bin>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2012 Microsoft Corp.
Provider name: 'Microsoft File Share Shadow Copy provider' Provider type: Fileshare Provider Id: {89300202-3cec-4981-9171-19f59559e0f2} Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0' Provider type: System Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} Version: 1.0.0.7

I tried to disable "Provider name: 'Microsoft File Share Shadow Copy provider' by command line
"w2koption -backup -snapshotprovidertype 1"
but it didn't work.

Can someone know how to disable that provider ? Thank you.

Backup and Recovery
NetBackup
Windows Server (2003-2008)

10 Replies

  • sdo's avatar
    sdo
    Moderator
    10 years ago

    1) Try a reboot first - this usually fixes most VSS errors.

    2) Why are you attempting to disable a VSS "provider"?  This is a fairly unusual step to take, and not normally needed nor recommended.  Please explain why you think this is an appropriate action to take?

    3) NetBackup Client version?

  • T_N's avatar
    T_N
    Level 6
    10 years ago

    I opened a case to symantec support, they recommends me to disable 'Microsoft File Share Shadow Copy provider'. Backup is running on 7.5.0.6, master server is linux server

  • rk1074's avatar
    rk1074
    Level 6
    10 years ago

    Please check the state of the VSS writers using  the command:

    vssadmin list writers

     

     

  • T_N's avatar
    T_N
    Level 6
    10 years ago
    vssadmin list writers output 1. C:\Windows\system32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2012 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: {2318fdb0-fbf4-422c-b28f-ce2e4cf5b050} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {7736dde0-35de-4059-a3e1-62344e09e25d} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {7b9aed19-8d6f-4cb2-ba0d-c395e7f99b16} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {c0349339-a66f-49bf-be1e-a5fb84469a84} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {7db59215-4a98-4fdb-bbb5-41afb63c2c83} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {f29344f6-ecb2-4727-bee6-35e536660d5f} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {a97a7847-59ca-4e30-abdf-d2d38d9bf865} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {cb0ca0f3-af0e-4c4a-bcfb-fb4ece73de92} State: [1] Stable Last error: No error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {0bbb0335-a75e-4cfc-be41-80a71adb3fa5} State: [1] Stable Last error: No error
  • sdo's avatar
    sdo
    Moderator
    10 years ago
    Writers look ok. Did Symantec support explain why disabling the VSS writer was required?
  • T_N's avatar
    T_N
    Level 6
    10 years ago
    he said the issue is likely to be being caused by an unusual provider being selected by VSS. Microsoft Software Shadow Copy provider 1.0 is usually the default, but your output shows Microsoft File Share Shadow Copy provider:
  • sdo's avatar
    sdo
    Moderator
    10 years ago

    I can't see any evidence that the presence of two MS VSS providers is causing an issue for your backups.  Can you show this?

    BTW the command "w2koption -backup -snapshotprovidertype 1" does not select which provider to use, nor does it "disable" a VSS provider - it selects a provider type for backups.  Can you show evidence of why you think this didn't work?  Can you show output from "w2koption -backup -display" ?

  • T_N's avatar
    T_N
    Level 6
    10 years ago

    Windows SA ran "w2koption -backup -snapshotprovidertype 1" and he said no output is provided

  • T_N's avatar
    T_N
    Level 6
    10 years ago

    Windows SA is not able to remove MSFT File Share Shadow copy via the registry. What is next step to troubleshoot ? Thank you.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    No response in a long time...

    I would say that the next step is to log a simultaneous call with Symantec and Microsoft.