Forum Discussion

ankur1809's avatar
ankur1809
Level 5
10 years ago

Backup issue for shadow copy components-156

Backup for shadow copy is failing with error code 156.

C:\ on the same server is getting backed up successfully.

Master server :Linux ,
Client: Windows 2003 64Bit.
Backup selection:ALL_LOCAL_DRIVES
NBU version :7.6.0.1

Error bptm (pid=29453) system call failed - Connection reset by peer (at child.c.1306)
09/04/2014 00:24:56 - Error bptm (pid=29453) unable to perform read from client socket, connection may have been broken
09/04/2014 00:24:56 - Error bptm (pid=29449) media manager terminated by parent process
09/04/2014 00:25:07 - Error bpbrm (pid=29442) could not send server status message
09/04/2014 00:25:08 - Info bpbkar (pid=4740) done. status: 156: snapshot error encountered
09/04/2014 00:25:08 - end writing; write time: 0:00:15 snapshot error encountered (156)

  • Is this maybe the inactive node of a cluster?

    I see this in bpbkar log:

    08:52:24.617 [956.1044] <2> ov_log::V_GlobalLog: INF - Failed to resolve volume path name
    08:52:24.617 [956.1044] <2> ov_log::V_GlobalLog: INF - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) processing file path e:\fastsearch\\bin when getting file descriptors

     

    See this TN: http://www.symantec.com/docs/TECH128805

    Extract:

    Syntax:
    w2koption -backup -ignore_unresolved_volumes <volume:>
     
    Example if drive letter F is missing:
    w2koption -backup -ignore_unresolved_volumes F:
     
    Example if drive letters F and G are missing:
    w2koption -backup -ignore_unresolved_volumes F:G:
     

14 Replies