backup failing w/ code 13 on shadow copy components - Veritas Net Backup

This is a discussion on backup failing w/ code 13 on shadow copy components - Veritas Net Backup ; Has anyone seen this before? I have a windows 2003 client with Netbackup 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The backup fails with status code 13 when it tries to back up Shadow Copy ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: backup failing w/ code 13 on shadow copy components

  1. backup failing w/ code 13 on shadow copy components


    Has anyone seen this before? I have a windows 2003 client with Netbackup
    5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The backup
    fails with status code 13 when it tries to back up Shadow Copy Components:\.
    All other directories are backing up fine. Any suggestions? Please advise.


  2. Re: backup failing w/ code 13 on shadow copy components

    Hi mflores,

    i think error 13 is "file read failed". But it may be, that the error on
    shadow copy components isn't the origin of the error.
    I have seen somtimes this error (shadow copy components) and the logfiles
    aren't allways absolutely good to read.
    Maybe its an another problem.

    Could you post the Log-Output of one errorjob?

    bye
    Zmiley


    "mflores" schrieb im Newsbeitrag
    news:468226ef@ROSASTDMZ05....
    >
    > Has anyone seen this before? I have a windows 2003 client with Netbackup
    > 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The

    backup
    > fails with status code 13 when it tries to back up Shadow Copy

    Components:\.
    > All other directories are backing up fine. Any suggestions? Please

    advise.
    >




  3. Re: backup failing w/ code 13 on shadow copy components

    Hi mflores,

    it looks more like a connection problem. Maybe caused from a firewall or an
    another configuration.

    The Master Server cant connect to the right socket or someting. You should
    watch out for the firewall configuration on the masterserver and/or the
    client. There you can set the connection to the one specific port and not
    random/multiple ports.

    bye
    Zmiley


    "mflores" schrieb im Newsbeitrag
    news:4682c385@ROSASTDMZ05....
    >
    > Hi,
    >
    > Here's what the log shows:
    >
    > 6/27/2007 12:01:25 AM - started process bptm (766100)
    > 6/27/2007 12:01:25 AM - started process bpbrm (634892)
    > 6/27/2007 12:01:25 AM - connecting
    > 6/27/2007 12:01:25 AM - connected; connect time: 00:00:00
    > 6/27/2007 12:01:27 AM - mounting 230376
    > 6/27/2007 12:01:28 AM - Error bptm(pid=438306) system call failed - A

    connection
    > with a remote socket was reset by that socket. (at child.c.1137)
    > 6/27/2007 12:01:28 AM - Error bptm(pid=438306) unable to perform read from
    > client socket, connection may have been broken
    > 6/27/2007 12:01:29 AM - Error bpbrm(pid=634892) socket read failed: errno
    > = 73 - A connection with a remote socket was reset by that socket.
    > 6/27/2007 12:01:29 AM - Error bptm(pid=766100) media manager terminated

    during
    > mount of media id 230376, possible media mount timeout
    > 6/27/2007 12:01:31 AM - Error bptm(pid=766100) media manager terminated by
    > parent process
    > 6/27/2007 12:01:32 AM - end writing
    > file read failed(13)
    > 6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) suspending further

    backup
    > attempts for client ds008, policy ds008-zone3-host, schedule incremental
    > because it has exceeded the configured number of tries
    > 6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) backup of client ds008
    > exited with status 13 (file read failed)
    > 6/27/2007 3:03:06 AM - Error bpsched(pid=704616) Cancel incomplete job

    <7558>.
    > Job exceeded maximum incomplete time.
    > file read failed(13)
    >
    > "Paradoxin" wrote:
    > >Hi mflores,
    > >
    > >i think error 13 is "file read failed". But it may be, that the error on
    > >shadow copy components isn't the origin of the error.
    > >I have seen somtimes this error (shadow copy components) and the logfiles
    > >aren't allways absolutely good to read.
    > >Maybe its an another problem.
    > >
    > >Could you post the Log-Output of one errorjob?
    > >
    > >bye
    > >Zmiley
    > >
    > >
    > >"mflores" schrieb im Newsbeitrag
    > >news:468226ef@ROSASTDMZ05....
    > >>
    > >> Has anyone seen this before? I have a windows 2003 client with

    Netbackup
    > >> 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The

    > >backup
    > >> fails with status code 13 when it tries to back up Shadow Copy

    > >Components:\.
    > >> All other directories are backing up fine. Any suggestions? Please

    > >advise.
    > >>

    > >
    > >

    >




  4. Re: backup failing w/ code 13 on shadow copy components


    Hi,

    Here's what the log shows:

    6/27/2007 12:01:25 AM - started process bptm (766100)
    6/27/2007 12:01:25 AM - started process bpbrm (634892)
    6/27/2007 12:01:25 AM - connecting
    6/27/2007 12:01:25 AM - connected; connect time: 00:00:00
    6/27/2007 12:01:27 AM - mounting 230376
    6/27/2007 12:01:28 AM - Error bptm(pid=438306) system call failed - A connection
    with a remote socket was reset by that socket. (at child.c.1137)
    6/27/2007 12:01:28 AM - Error bptm(pid=438306) unable to perform read from
    client socket, connection may have been broken
    6/27/2007 12:01:29 AM - Error bpbrm(pid=634892) socket read failed: errno
    = 73 - A connection with a remote socket was reset by that socket.
    6/27/2007 12:01:29 AM - Error bptm(pid=766100) media manager terminated during
    mount of media id 230376, possible media mount timeout
    6/27/2007 12:01:31 AM - Error bptm(pid=766100) media manager terminated by
    parent process
    6/27/2007 12:01:32 AM - end writing
    file read failed(13)
    6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) suspending further backup
    attempts for client ds008, policy ds008-zone3-host, schedule incremental
    because it has exceeded the configured number of tries
    6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) backup of client ds008
    exited with status 13 (file read failed)
    6/27/2007 3:03:06 AM - Error bpsched(pid=704616) Cancel incomplete job <7558>.
    Job exceeded maximum incomplete time.
    file read failed(13)

    "Paradoxin" wrote:
    >Hi mflores,
    >
    >i think error 13 is "file read failed". But it may be, that the error on
    >shadow copy components isn't the origin of the error.
    >I have seen somtimes this error (shadow copy components) and the logfiles
    >aren't allways absolutely good to read.
    >Maybe its an another problem.
    >
    >Could you post the Log-Output of one errorjob?
    >
    >bye
    >Zmiley
    >
    >
    >"mflores" schrieb im Newsbeitrag
    >news:468226ef@ROSASTDMZ05....
    >>
    >> Has anyone seen this before? I have a windows 2003 client with Netbackup
    >> 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The

    >backup
    >> fails with status code 13 when it tries to back up Shadow Copy

    >Components:\.
    >> All other directories are backing up fine. Any suggestions? Please

    >advise.
    >>

    >
    >



  5. Re: backup failing w/ code 13 on shadow copy components


    Hi Paradoxin,

    That was my first thought but all the other directories from the same policy,
    same host are completing successfully. We have the policy set to use multiple
    streams for reporting purpose.

    --mflores

    "Paradoxin" wrote:
    >Hi mflores,
    >
    >it looks more like a connection problem. Maybe caused from a firewall or

    an
    >another configuration.
    >
    >The Master Server cant connect to the right socket or someting. You should
    >watch out for the firewall configuration on the masterserver and/or the
    >client. There you can set the connection to the one specific port and not
    >random/multiple ports.
    >
    >bye
    >Zmiley
    >
    >
    >"mflores" schrieb im Newsbeitrag
    >news:4682c385@ROSASTDMZ05....
    >>
    >> Hi,
    >>
    >> Here's what the log shows:
    >>
    >> 6/27/2007 12:01:25 AM - started process bptm (766100)
    >> 6/27/2007 12:01:25 AM - started process bpbrm (634892)
    >> 6/27/2007 12:01:25 AM - connecting
    >> 6/27/2007 12:01:25 AM - connected; connect time: 00:00:00
    >> 6/27/2007 12:01:27 AM - mounting 230376
    >> 6/27/2007 12:01:28 AM - Error bptm(pid=438306) system call failed - A

    >connection
    >> with a remote socket was reset by that socket. (at child.c.1137)
    >> 6/27/2007 12:01:28 AM - Error bptm(pid=438306) unable to perform read

    from
    >> client socket, connection may have been broken
    >> 6/27/2007 12:01:29 AM - Error bpbrm(pid=634892) socket read failed: errno
    >> = 73 - A connection with a remote socket was reset by that socket.
    >> 6/27/2007 12:01:29 AM - Error bptm(pid=766100) media manager terminated

    >during
    >> mount of media id 230376, possible media mount timeout
    >> 6/27/2007 12:01:31 AM - Error bptm(pid=766100) media manager terminated

    by
    >> parent process
    >> 6/27/2007 12:01:32 AM - end writing
    >> file read failed(13)
    >> 6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) suspending further

    >backup
    >> attempts for client ds008, policy ds008-zone3-host, schedule incremental
    >> because it has exceeded the configured number of tries
    >> 6/27/2007 12:01:34 AM - Error bpsched(pid=1060944) backup of client ds008
    >> exited with status 13 (file read failed)
    >> 6/27/2007 3:03:06 AM - Error bpsched(pid=704616) Cancel incomplete job

    ><7558>.
    >> Job exceeded maximum incomplete time.
    >> file read failed(13)
    >>
    >> "Paradoxin" wrote:
    >> >Hi mflores,
    >> >
    >> >i think error 13 is "file read failed". But it may be, that the error

    on
    >> >shadow copy components isn't the origin of the error.
    >> >I have seen somtimes this error (shadow copy components) and the logfiles
    >> >aren't allways absolutely good to read.
    >> >Maybe its an another problem.
    >> >
    >> >Could you post the Log-Output of one errorjob?
    >> >
    >> >bye
    >> >Zmiley
    >> >
    >> >
    >> >"mflores" schrieb im Newsbeitrag
    >> >news:468226ef@ROSASTDMZ05....
    >> >>
    >> >> Has anyone seen this before? I have a windows 2003 client with

    >Netbackup
    >> >> 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The
    >> >backup
    >> >> fails with status code 13 when it tries to back up Shadow Copy
    >> >Components:\.
    >> >> All other directories are backing up fine. Any suggestions? Please
    >> >advise.
    >> >>
    >> >
    >> >

    >>

    >
    >



  6. Re: backup failing w/ code 13 on shadow copy components

    mflores wrote, in part, on 2007-06-27 4:59 AM:
    > Has anyone seen this before? I have a windows 2003 client with Netbackup
    > 5.1 MP5. Master and media server are also at Netbackup 5.1 MP5. The backup
    > fails with status code 13 when it tries to back up Shadow Copy Components:\.
    > All other directories are backing up fine. Any suggestions? Please advise.


    I get this sometimes. I see one from this week on one of my Exchange
    servers. It happens so quickly that it can't be a timeout problem. The
    client end decides to close the socket. You might try turning on some
    client-side logging to see what's going on.

    I've seen something similar to this on machines that have an old ".VSP"
    file left from a previous failed backup. You might verify this is not
    the problem.

    Let us know what you find, please!

    cheers, wayne

+ Reply to Thread