<?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: OpenVMS I64 image backups in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356372#M93325</link>
    <description>Max,&lt;BR /&gt;&lt;BR /&gt;Indeed, a GUID is 128 bits (the Wikipedia entry for GUID is at &lt;A href="http://en.wikipedia.org/wiki/Guid" target="_blank"&gt;http://en.wikipedia.org/wiki/Guid&lt;/A&gt; , which also contains links to entries about how EFI uses GUID.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
    <pubDate>Thu, 12 Feb 2009 07:45:51 GMT</pubDate>
    <dc:creator>Robert Gezelter</dc:creator>
    <dc:date>2009-02-12T07:45:51Z</dc:date>
    <item>
      <title>OpenVMS I64 image backups</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356370#M93323</link>
      <description>&lt;!--!*#--&gt;I used BACKUP /IMAGE to make a copy of my OpenVMS I64 system disk on an Integrity server rx2660. I booted from the OpenVMS DVD to run this copy, so I wasn't trying to copy the running system disk. The copy appears to complete OK, but my problem is that the copy disk won't boot in the same way as the original.&lt;BR /&gt;&lt;BR /&gt;I can boot from the copy disk using EFI's "boot from file" option, then use the boot_options command file to "validate" (and correct) the EFI boot list entry for the copy disk, and then it works properly. Is it normal to have to do this to create a bootable copy of the system disk?&lt;BR /&gt;&lt;BR /&gt;I'm wondering whether the EFI boot list entry contains some information about the whereabouts of some file on the disk, and after the disk has been the target of BACKUP /IMAGE, that file is in a different place?&lt;BR /&gt;&lt;BR /&gt;Any help gratefully received. Thanks.</description>
      <pubDate>Wed, 11 Feb 2009 10:48:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356370#M93323</guid>
      <dc:creator>Max Bruno Jarvis</dc:creator>
      <dc:date>2009-02-11T10:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS I64 image backups</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356371#M93324</link>
      <description>Short answer - yes it is normal.&lt;BR /&gt;&lt;BR /&gt;Here is the longer answer....&lt;BR /&gt;&lt;BR /&gt;The EFI stores the GUID (Global Unique&lt;BR /&gt;Identifier) of each boot option. It is&lt;BR /&gt;a 128bit (I think!) binary number that &lt;BR /&gt;uniquely identifies the boot partition. &lt;BR /&gt;The same number is stored inside the boot&lt;BR /&gt;block on the system disk.&lt;BR /&gt;&lt;BR /&gt;When the EFI attempts to boot using a boot&lt;BR /&gt;option a check is made to compare the GUID&lt;BR /&gt;stored in the console to the one stored on &lt;BR /&gt;the disk. If there is no match, the boot option will not work.&lt;BR /&gt;&lt;BR /&gt;When restoring a BACKUP/IMAGE, the backup&lt;BR /&gt;utility calls $SETBOOT to create the boot&lt;BR /&gt;block on your new system disk. $SETBOOT&lt;BR /&gt;generates a new GUID so the one stored in&lt;BR /&gt;the console does not match the one stored&lt;BR /&gt;in the EFI and you have to re-validate&lt;BR /&gt;the boot option.&lt;BR /&gt;&lt;BR /&gt;While working in HP, I have modified BACKUP&lt;BR /&gt;to preserve the GUID inside the save-set&lt;BR /&gt;header, what is currently missing is a &lt;BR /&gt;mechanism for BACKUP to pass the GUID to&lt;BR /&gt;$SETBOOT and instruct $SETBOOT to avoid&lt;BR /&gt;creating a new GUID.&lt;BR /&gt;&lt;BR /&gt;So what you are seeing is normal behavior&lt;BR /&gt;(or at least expected).&lt;BR /&gt;&lt;BR /&gt;Guy Peleg&lt;BR /&gt;Maklee Engineering&lt;BR /&gt;&lt;A href="http://www.maklee.com" target="_blank"&gt;http://www.maklee.com&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Feb 2009 07:15:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356371#M93324</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2009-02-12T07:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS I64 image backups</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356372#M93325</link>
      <description>Max,&lt;BR /&gt;&lt;BR /&gt;Indeed, a GUID is 128 bits (the Wikipedia entry for GUID is at &lt;A href="http://en.wikipedia.org/wiki/Guid" target="_blank"&gt;http://en.wikipedia.org/wiki/Guid&lt;/A&gt; , which also contains links to entries about how EFI uses GUID.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Thu, 12 Feb 2009 07:45:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-i64-image-backups/m-p/4356372#M93325</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2009-02-12T07:45:51Z</dc:date>
    </item>
  </channel>
</rss>

