<?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 How to create an ignite tape from specific drives in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330613#M342004</link>
    <description>Our configuration is that we have san-attached os disks, but also have the original os internal drives on the server. The local disks are retained if something happens to the san and the server needs to be rebooted to a minimal os. I created an ignite tape (make_tape_recovery -I -x inc_entire=vg00) to boot a DR server, but the ignition process failed with an fatal configuration. The DR server has the standard local os disks, and is not attached to the SAN. My guess is the ignite tape created an image of the SAN-based disks and the DR server doesnt have that hardware configuration so it failed. Is there a way to create an ignite tape that can be "directed" copy the os image of an internal boot disk, even though the local server is booted off the SAN. My system is rp7400/11.i</description>
    <pubDate>Wed, 31 Dec 2008 14:59:15 GMT</pubDate>
    <dc:creator>frederick hannah</dc:creator>
    <dc:date>2008-12-31T14:59:15Z</dc:date>
    <item>
      <title>How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330613#M342004</link>
      <description>Our configuration is that we have san-attached os disks, but also have the original os internal drives on the server. The local disks are retained if something happens to the san and the server needs to be rebooted to a minimal os. I created an ignite tape (make_tape_recovery -I -x inc_entire=vg00) to boot a DR server, but the ignition process failed with an fatal configuration. The DR server has the standard local os disks, and is not attached to the SAN. My guess is the ignite tape created an image of the SAN-based disks and the DR server doesnt have that hardware configuration so it failed. Is there a way to create an ignite tape that can be "directed" copy the os image of an internal boot disk, even though the local server is booted off the SAN. My system is rp7400/11.i</description>
      <pubDate>Wed, 31 Dec 2008 14:59:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330613#M342004</guid>
      <dc:creator>frederick hannah</dc:creator>
      <dc:date>2008-12-31T14:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330614#M342005</link>
      <description>HI Frederick:&lt;BR /&gt;&lt;BR /&gt;The 'make_tape_recovery' command supports '-x inc_entire=/dev/dsk/name|vg_name'.  See the manpages for more details.&lt;BR /&gt;&lt;BR /&gt;That said, you say the "ignition process failed with a fatal configuration".  Did you specify an "Advanced Installation" when you Ignited and set "cloning to different hardware=yes".  If not, I think that this would cause your failure.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 15:10:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330614#M342005</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-12-31T15:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330615#M342006</link>
      <description>it will be helpful ifu can give the #ioscan -fn #ioscan -fnCdisk and vgdisplay -v O/ps for the both the server.&lt;BR /&gt;&lt;BR /&gt;#make_tape_recovery -v -x inc_entire=vg00 /dev/rmt/0mn is the basic command that will include whole of the vg VG00.&lt;BR /&gt;&lt;BR /&gt;#make_tape_recovery -v -x inc_entire=vg00 -x inc_entire=/dev/dsk/c0t1d0 --- this shall ibclude both entire VG00 and also contents of the disk as /dev/dsk/c0t1d0.&lt;BR /&gt;&lt;BR /&gt;u can take ignite and restore Ignite etc Immaterial the OS disks are local or on the SAN unless and until u can identify the disks properly at taking and restoring ignite archive.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 15:50:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330615#M342006</guid>
      <dc:creator>sujit kumar singh</dc:creator>
      <dc:date>2008-12-31T15:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330616#M342007</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you can go for ignite golden image &lt;BR /&gt;&lt;BR /&gt;Javed</description>
      <pubDate>Wed, 31 Dec 2008 19:34:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330616#M342007</guid>
      <dc:creator>Javed Khan_1</dc:creator>
      <dc:date>2008-12-31T19:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330617#M342008</link>
      <description>Restoring this Ignite archive to an internal disk shouldn't be a problem, since one is allowed to specify the target disk when installing the image from the itool interface. The problem is when you are trying to restore more than one volume group, so it's recommended to specify one.&lt;BR /&gt;&lt;BR /&gt;It will be useful to see the fatal error message.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 21:16:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330617#M342008</guid>
      <dc:creator>Ricardo Soto</dc:creator>
      <dc:date>2008-12-31T21:16:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an ignite tape from specific drives</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330618#M342009</link>
      <description>Hi Frederick,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; I created an ignite tape (make_tape_recovery -I -x inc_entire=vg00) to boot a DR server,&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;the ignition process failed with an fatal configuration&amp;lt;&amp;lt;&lt;BR /&gt;&lt;BR /&gt;what fatal error message..?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;The DR server has the standard local os disks, and is not attached to the SAN. My guess is the ignite tape created an image of the SAN-based disks and the DR server doesnt have that hardware configuration&amp;lt;&amp;lt;&lt;BR /&gt;&lt;BR /&gt;Could be unless you boot disk is from "SAN disk" which you performed the Ignite backup&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Johnson&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Jan 2009 14:22:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-create-an-ignite-tape-from-specific-drives/m-p/4330618#M342009</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2009-01-01T14:22:44Z</dc:date>
    </item>
  </channel>
</rss>

