<?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: VMS Backup on v7.3-2 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763702#M75431</link>
    <description>J,&lt;BR /&gt;&lt;BR /&gt;This error will happen when you backup a file that then gets deleted off the disk before the backup date is weritten to the file.  This is nor a problem to worry about.  It is for information only.&lt;BR /&gt;&lt;BR /&gt;Phil</description>
    <pubDate>Sat, 01 Apr 2006 00:17:06 GMT</pubDate>
    <dc:creator>Phillip Thayer</dc:creator>
    <dc:date>2006-04-01T00:17:06Z</dc:date>
    <item>
      <title>VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763701#M75430</link>
      <description>Greetings,&lt;BR /&gt;&lt;BR /&gt;My backup log displayed an error for writing toward the end of my backup for one of the disk volumes.  Does anyone know what's the cause of this error and should I worry about this error?  This is a backup com procedure that backs up 3 disk volumes within a single procedure.&lt;BR /&gt;&lt;BR /&gt;This is a VMS backup procedure.&lt;BR /&gt;&lt;BR /&gt;%BACKUP-I-WRITEBACK, error writing backup date for DISK31: file ID (20449,109,0)&lt;BR /&gt;-SYSTEM-W-NOSUCHFILE, no such file&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Fri, 31 Mar 2006 23:45:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763701#M75430</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2006-03-31T23:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763702#M75431</link>
      <description>J,&lt;BR /&gt;&lt;BR /&gt;This error will happen when you backup a file that then gets deleted off the disk before the backup date is weritten to the file.  This is nor a problem to worry about.  It is for information only.&lt;BR /&gt;&lt;BR /&gt;Phil</description>
      <pubDate>Sat, 01 Apr 2006 00:17:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763702#M75431</guid>
      <dc:creator>Phillip Thayer</dc:creator>
      <dc:date>2006-04-01T00:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763703#M75432</link>
      <description>Jorge,&lt;BR /&gt;&lt;BR /&gt;specifically, this error can only occur when you have /RECORD in your BACKUP command, and there is activity on the target disk.&lt;BR /&gt;If you check your backup report ( if you did /LOG or /LIS ), then you WILL find this file backed up, but a DIR will NOT find the file.&lt;BR /&gt;Backup first does a full inventory, then writes it all to tape (or any target saveset), and only then writes the BACKUP DATE. Files might be deleted in between. &lt;BR /&gt;(a related error is "Error reading file ...etc, if the file was deleted after inventory, before including in the saveset)&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;</description>
      <pubDate>Sat, 01 Apr 2006 11:36:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763703#M75432</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-04-01T11:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763704#M75433</link>
      <description>Gentlemen - Thanks so much for your response.  One quick question, what should I do if I'm going to backup the target drive with open files?  I have used command such as, "/ignore=(inter, label)" with my image backup.&lt;BR /&gt;&lt;BR /&gt;Yes, I do have 2-3 target drives that possibly have open files.  I did a set file mark "nobackup" for the log files that I didn't want to backup during my backup procedure.&lt;BR /&gt;&lt;BR /&gt;I am very gracious for your feedback.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Sat, 01 Apr 2006 22:00:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763704#M75433</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2006-04-01T22:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763705#M75434</link>
      <description>As the HELP (V7.3-2) says:&lt;BR /&gt;&lt;BR /&gt;                                    NOTE&lt;BR /&gt;&lt;BR /&gt;        File system interlocks are expressly designed to prevent&lt;BR /&gt;        data corruptions, and to allow applications to detect and&lt;BR /&gt;        report data access conflicts.&lt;BR /&gt;&lt;BR /&gt;        Use of the INTERLOCK keyword overrides these file data&lt;BR /&gt;        integrity interlocks. The data that BACKUP subsequently&lt;BR /&gt;        transfers can then contain corrupted data for open files.&lt;BR /&gt;        Also, all cases in which these data corruptions can occur in&lt;BR /&gt;        the data that BACKUP transfers are not be reliably reported&lt;BR /&gt;        to you; in other words, silent data corruptions are possible&lt;BR /&gt;        within the transferred data.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If the buffers have all been flushed, and if&lt;BR /&gt;the files are idle, then the results should&lt;BR /&gt;be good.  If not, then the data will not be&lt;BR /&gt;perfect.  How stable, and how important, are&lt;BR /&gt;the data in the open files?</description>
      <pubDate>Sat, 01 Apr 2006 22:10:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763705#M75434</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2006-04-01T22:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763706#M75435</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;These files are mostly log files.  They are not that important.  However, I just hate see these errors that's all.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;J</description>
      <pubDate>Sat, 01 Apr 2006 23:32:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763706#M75435</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2006-04-01T23:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763707#M75436</link>
      <description>If you hate them enough, you boot in a more&lt;BR /&gt;minimal way, and/or from another device&lt;BR /&gt;and/or [SYSn] directory.  That is, Standalone&lt;BR /&gt;BACKUP (VAX), or a CD-ROM, or something like&lt;BR /&gt;that.&lt;BR /&gt;&lt;BR /&gt;If you don't hate them that much, then you&lt;BR /&gt;probably have to live with them.</description>
      <pubDate>Sun, 02 Apr 2006 03:04:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763707#M75436</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2006-04-02T03:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Backup on v7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763708#M75437</link>
      <description>Jorge,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;However, I just hate see these errors that's all.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;Well, they ARE not errors!&lt;BR /&gt;Look at that single letter betrween the two "-" :  "I" means Informational.&lt;BR /&gt;The slightly more serious messages are -W- , for Warning. Next comes -E-, those ARE errors. And finally there is -F-, for Fatal (or Severe) error.&lt;BR /&gt;The difference between -E- and -F- is for instance: -E- : a file that BACKUP found in the inventory phase got deleted before it was its turn to be read: -E- FNF, file not found. But the Backup can continue. -F-: the tape has "lost position" and cannot recover. Now the whole Backup has to be stopped.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Sun, 02 Apr 2006 03:27:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-backup-on-v7-3-2/m-p/3763708#M75437</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-04-02T03:27:43Z</dc:date>
    </item>
  </channel>
</rss>

