<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error 51: Socket failure in Automated Backup</title>
    <link>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/5306587#M1278</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the same issue with DPX 4.01 32 bit running on the primary server (SLES 10 SP1).&lt;/P&gt;&lt;P&gt;The agent (64 bit) on the remote server (SLES 10 SP3) completes about &amp;nbsp;85GB out of 300GB then Socket Failure (51).&lt;/P&gt;&lt;P&gt;The server works fine otherwise and users report no access issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like a comms issue of some sort.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone troubleshot this before. &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 20 Aug 2011 07:27:38 GMT</pubDate>
    <dc:creator>GMZ</dc:creator>
    <dc:date>2011-08-20T07:27:38Z</dc:date>
    <item>
      <title>Error 51: Socket failure</title>
      <link>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/4702009#M1277</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I'm having trouble backing up the message that occurs is: &lt;BR /&gt;&lt;BR /&gt;Error 51: Socket failure &lt;BR /&gt;&lt;BR /&gt;A network error has occurred while transferring data. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;My backup is in 90% and this error occurs I can do to solve the problem. &lt;BR /&gt;  &lt;BR /&gt;</description>
      <pubDate>Wed, 20 Oct 2010 09:17:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/4702009#M1277</guid>
      <dc:creator>Leandro Favretto</dc:creator>
      <dc:date>2010-10-20T09:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: Error 51: Socket failure</title>
      <link>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/5306587#M1278</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the same issue with DPX 4.01 32 bit running on the primary server (SLES 10 SP1).&lt;/P&gt;&lt;P&gt;The agent (64 bit) on the remote server (SLES 10 SP3) completes about &amp;nbsp;85GB out of 300GB then Socket Failure (51).&lt;/P&gt;&lt;P&gt;The server works fine otherwise and users report no access issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like a comms issue of some sort.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone troubleshot this before. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Aug 2011 07:27:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/5306587#M1278</guid>
      <dc:creator>GMZ</dc:creator>
      <dc:date>2011-08-20T07:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: Error 51: Socket failure</title>
      <link>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/5563189#M1279</link>
      <description>&lt;P&gt;I am constantly getting these errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tried removing and reinstalling the software and&amp;nbsp;creating new D2D libraries with no change. The issue has spanned across various servers, and is prolific with all DPX versions I've tried. I also get library not initialized quite frequently, but only use D2D virtual tapes with the wizard that created everything.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Needless to say, i am using this software to provide a lever of redundancy, but cannot trust that the backups are ever being performed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any solutions out there?&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2012 20:07:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/automated-backup/error-51-socket-failure/m-p/5563189#M1279</guid>
      <dc:creator>decstewartje</dc:creator>
      <dc:date>2012-02-24T20:07:42Z</dc:date>
    </item>
  </channel>
</rss>

