Forum Discussion

RamNagalla's avatar
RamNagalla
Moderator
13 years ago

Windows snapshot failure for shadow copy components

 

Hello,

 

I have a windows 2008 client .. were I am getting 156 error when trying to take the shadow copy comonents... I have see the error in the bpbbkar log.. 

5:03:35.855 AM: [1764.2020] <16> dos_backup::V_InitializeSystemState: ERR - FS_AddToSnapshotSet() Failed! (System State:\System Files\System Files) 0xE0000352:The specified volume does not exist. Recreate the volume, and then try the job again.

 

and find the T/N http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=en_US&id=TECH164712

 .. where its asking me to check the Windows backup using WBAdmin.. but some reasons.. SA was not able to enable the windows backup.. .. as per the SA... he need to dedicate the new local Drive for the backup as the 2008 backup style has been chaged , and he can not do that.. so I have no option to check the WBAdmin backup..

do i have any anoter way to find and isolate and troubleshoot the issue....

.

 

Detail log:-

 

5:03:16.178 AM: [1764.2020] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'Shadow Copy Components:\' --> 10020027
5:03:17.599 AM: [1764.2020] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'System State:\' --> 1002002d
5:03:17.599 AM: [1764.2020] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '_BACKUP_SPECIAL_OBJECTS AFTER System State:' --> 1002002d
5:03:18.839 AM: [1764.2020] <4> VssSnapshot::V_VssSetMetadata(): INF - Unable to locate DFSR metadata
5:03:19.489 AM: [1764.2020] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
5:03:19.489 AM: [1764.2020] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: Begin
5:03:21.475 AM: [1764.2020] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - Drive 'C:' added to VSS Volume Set
5:03:28.106 AM: [1764.2020] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - VSS Volume Set snapped
5:03:28.106 AM: [1764.2020] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - About to commence post-snap unbounded association checks
5:03:28.106 AM: [1764.2020] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: End
5:03:28.106 AM: [1764.2020] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
5:03:28.106 AM: [1764.2020] <4> VssSnapshot::V_VssSetMetadata(): INF - Unable to locate DFSR metadata
5:03:35.855 AM: [1764.2020] <16> dos_backup::V_InitializeSystemState: ERR - FS_AddToSnapshotSet() Failed! (System State:\System Files\System Files) 0xE0000352:The specified volume does not exist. Recreate the volume, and then try the job again.
 
5:03:35.855 AM: [1764.2020] <2> tar_base::V_vTarMsgW: ERR - Volume resolution error for (System State:\System Files\System Files)
5:03:35.858 AM: [1764.2020] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encountered
5:03:35.858 AM: [1764.2020] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
5:03:38.112 AM: [1764.2020] <4> tar_backup::SetExcludeFileList: INF - exclude list is ignored
5:03:38.112 AM: [1764.2020] <4> tar_backup_tfi::UpdateExcludeListWithVHD: INF - UpdateExludeListWithVHD begin
5:03:47.979 AM: [1764.2020] <4> OVStopCmd: INF - EXIT - status = 0
5:03:47.979 AM: [1764.2020] <2> tar_base::V_Close: closing...
5:03:47.979 AM: [1764.2020] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
5:03:48.179 AM: [1764.2020] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000001
5:03:48.188 AM: [1764.2020] <16> dtcp_read: TCP - failure: recv socket (500) (TCP 10053: Software caused connection abort)
5:03:48.188 AM: [1764.2020] <4> OVShutdown: INF - Finished process
5:03:48.202 AM: [1764.2020] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
5:03:50.202 AM: [1764.2020] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\032412.LOG
  • hi 

     

    these windows clients have the cluster drives, when the drives are avaliable in the node1 , node 2 is also trying to take the backup of the drives and its getting failed..as the drives are avaliable in node2

     

    w2koption -backup -ignore_unresolved_volumes <volume:>

     

    is the T/N related that..

    http://www.symantec.com/business/support/index?page=content&id=TECH128805

     

    Thank you very much all for your valualbe suggestions..

     

    Ram

8 Replies

  • Unable to locate DFSR metadata

    Do you have DFS Replication in place on this client?

    Please let us know NBU version on master, media server and W2008 client.

  • its 7.1 on all master media and client... and how to check...DFS replications......
  • I am trying to ingore the -ignore_unresolved_volumes for the system state... 

    with below tech Note...

    http://www.symantec.com/business/support/index?page=content&id=TECH128805

     

    any idea.. how I can provide the system state as argument.. in this tech note.. they given example for the drives..

     

     

     
    C:\Program Files\Veritas\NetBackup\bin>w2koption -backup -ignore_unresolved_volu
    mes System State:
     
    ERROR - invalid parameter: State:
  • This does say "volume resolution error"

    I saw this a while ago and was caused in that case by the server ebing built from the OEM 2008 CD.

    This created the reserved system drive, which has no drive letter but is the active partition.

    In that case it was resolevd by just giving it a drive letter - worth a try?

  • hi 

     

    these windows clients have the cluster drives, when the drives are avaliable in the node1 , node 2 is also trying to take the backup of the drives and its getting failed..as the drives are avaliable in node2

     

    w2koption -backup -ignore_unresolved_volumes <volume:>

     

    is the T/N related that..

    http://www.symantec.com/business/support/index?page=content&id=TECH128805

     

    Thank you very much all for your valualbe suggestions..

     

    Ram