Forum Discussion

Agent47's avatar
Agent47
Level 4
12 years ago

snapshot error encountered(156)

 

Hi Team,

 

Need help here.

im encounter snapshot error.

i already search regarding the issue and tyr this one :http://www.symantec.com/business/support/index?page=content&id=TECH75214<--

but failed.

 

is that ok to enable the drive in shadow copies?

ii checked the mximum cache size :300 MB.and increase to 600MB and started manual backup but failed.

=====

heres other information:

O.S 2003 NBackup6.0MP4

 

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: {1c1354bf-b7bd-41dd-a2f2-d1dc171482b0}
   State: [5] Waiting for completion <---------------------------------------------------------------------
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {ffe7b904-a7b7-4b2c-a0a4-5bb683e5869b}
   State: [5] Waiting for completion <-----------------------------------------------
   Last error: No error
 
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {bff71257-d998-4ef3-95f1-3424d15ac8b5}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {0885858d-8389-4dee-8fda-a6efd19a3f00}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {300a7772-4efb-43ef-b676-4f88fc98c4fc}
   State: [5] Waiting for completion
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {095cbde5-0ba0-45c6-9985-8ab610a9ce99}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {2bc597b8-612b-4f7d-a0b6-2f1d7d26c4a8}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {0f2f42a4-c8e5-41ea-a2a5-c558acc06360}
   State: [5] Waiting for completion
   Last error: No error
 
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e1ae128a-4313-4287-b896-4089e68238f6}
   State: [1] Stable
   Last error: No error
=========
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 

 

7.1.x and Earlier
Backup and Recovery
NetBackup
  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    Two things you can do to resolve snapshot error:

    Install latest MS hotfixes for VSS.


    I believe this is one of the newest VSS hotfixes : http://support.microsoft.com/kb/940349 
    You may want to check MS support site to see if there is anything newer.

    Upgrade NBU to 7.1.0.4 or 7.5.0.5.
    Lots of SCC fixes in 7.x 
    NBU 6.x reached EOSL in Oct 2012

  • Dyneshia's avatar
    Dyneshia
    Level 6
    12 years ago

    If there are no backups running, all writers should be stable and NOT waiting for completion.

    In addition to Marianne's post, you can also reboot the server to clear out the writer, however the above would be a more permanent solution.

  • Agent47's avatar
    Agent47
    Level 4
    12 years ago

    thanks for the advise team,

     

    by the way, i try to enable to shadow copies on the drive. and enable the windows open files backups for this client and choose " Use microsoft volume Shadow Copy service and the back job was successful.

     

    is that ok?

     

    need advice

     

  • Agent47's avatar
    Agent47
    Level 4
    12 years ago

    guys..good news:-) i upgrade the maintenace pack to mp7 and disable the shadow on the disk.

    then, i try to start backup and it was successful...wu hu.

    right now, no more snapshot error 156..

    thanks guys.