<?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 Backup to NFS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976603#M60775</link>
    <description>We are running OpenVMS V7.3-1. We tried to back up about 160 GB to a saveset on a very large mount point (terabytes) on a Sun NFS server. &lt;BR /&gt;&lt;BR /&gt;The initial attempt used defaults for blocksize, groupsize, CRC, etc. This try aborted with an file I/O related error. Unfortunately I didn't jot it down.&lt;BR /&gt;&lt;BR /&gt;The second attempt used a smaller blocksize of about 13000 and completed without errors. But upon restore, we found that BACKUP reported an error (oops, again no notes) on the first file (a very large one), then appeared to copy the remaining files (according to the log messages). However, it turned out that only roughly 40 to 50 percent of the files were actually retrieved--there was no trace of the remaining files.&lt;BR /&gt;&lt;BR /&gt;I've read a bit about problems with /CRC and also some suggestions for about using small blocksizes when the saveset is being created over NFS.&lt;BR /&gt;&lt;BR /&gt;Any further information or suggestions will be much appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Galen</description>
    <pubDate>Mon, 19 May 2003 15:52:17 GMT</pubDate>
    <dc:creator>Galen Tackett</dc:creator>
    <dc:date>2003-05-19T15:52:17Z</dc:date>
    <item>
      <title>Backup to NFS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976603#M60775</link>
      <description>We are running OpenVMS V7.3-1. We tried to back up about 160 GB to a saveset on a very large mount point (terabytes) on a Sun NFS server. &lt;BR /&gt;&lt;BR /&gt;The initial attempt used defaults for blocksize, groupsize, CRC, etc. This try aborted with an file I/O related error. Unfortunately I didn't jot it down.&lt;BR /&gt;&lt;BR /&gt;The second attempt used a smaller blocksize of about 13000 and completed without errors. But upon restore, we found that BACKUP reported an error (oops, again no notes) on the first file (a very large one), then appeared to copy the remaining files (according to the log messages). However, it turned out that only roughly 40 to 50 percent of the files were actually retrieved--there was no trace of the remaining files.&lt;BR /&gt;&lt;BR /&gt;I've read a bit about problems with /CRC and also some suggestions for about using small blocksizes when the saveset is being created over NFS.&lt;BR /&gt;&lt;BR /&gt;Any further information or suggestions will be much appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Galen</description>
      <pubDate>Mon, 19 May 2003 15:52:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976603#M60775</guid>
      <dc:creator>Galen Tackett</dc:creator>
      <dc:date>2003-05-19T15:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: Backup to NFS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976604#M60776</link>
      <description>Galen,&lt;BR /&gt;&lt;BR /&gt;You did not mention what version of TCPIP&lt;BR /&gt;you are using. If you are using HP's TCPIP&lt;BR /&gt;V5.3 you need a mandatory ECO to fix data&lt;BR /&gt;corruption problems related to NFS. This&lt;BR /&gt;may have something to do with your problem.&lt;BR /&gt;&lt;BR /&gt;                                               The name of the latest TCPIP kit is :       AXPVMS-TCPIP_ECO-V0503-182-4&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Guy</description>
      <pubDate>Wed, 21 May 2003 03:15:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976604#M60776</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2003-05-21T03:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: Backup to NFS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976605#M60777</link>
      <description>Not sure if this applies in your case or not, but several years ago, we had problems with a user creating save sets on a development system that would not restore on the production system.  The save set contained a rather large executable and some other files.  Using the system account, there was no problem creating the save set.  It turned out that there was a process quota that was too low (unfortunately, it has been too long and I don't remember the quota that had to be changed), but the original backup did not complain.  You might want to try the /Verify qualifier if you are not currently using it.</description>
      <pubDate>Wed, 21 May 2003 15:00:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976605#M60777</guid>
      <dc:creator>Dale A. Marcy</dc:creator>
      <dc:date>2003-05-21T15:00:15Z</dc:date>
    </item>
    <item>
      <title>Re: Backup to NFS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976606#M60778</link>
      <description>Have you verified that your NFS serve can handle large files? On 32 bit OSs, 2 GBs is the largest file size. On most 64 bit machines, the file system needs to be set to handle files larger than 2GBs.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Marty</description>
      <pubDate>Fri, 23 May 2003 19:51:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-to-nfs/m-p/2976606#M60778</guid>
      <dc:creator>Martin Johnson</dc:creator>
      <dc:date>2003-05-23T19:51:59Z</dc:date>
    </item>
  </channel>
</rss>

