<?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: Ignite errors out on multiple servers in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104796#M503391</link>
    <description>The command used was&lt;BR /&gt;&lt;BR /&gt;make_tape_recovery -x inc_entire=vg00 -x exclude=/etc/vx&lt;BR /&gt;&lt;BR /&gt;The only device being done is vg00.  The nfs directories just happen to reside off of the / file system.  Also, this is the same command that has been previously used to write tapes that were then recovered at our DR test facility so that has not changed.</description>
    <pubDate>Tue, 22 Apr 2008 13:10:51 GMT</pubDate>
    <dc:creator>Mike Smith_33</dc:creator>
    <dc:date>2008-04-22T13:10:51Z</dc:date>
    <item>
      <title>Ignite errors out on multiple servers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104793#M503388</link>
      <description>I have two servers which are part of a Serviceguard cluster.  I am attempting to do some testing at our colocation facility and I am having a problem we have never had during our Disaster Recovery testing when loading the system from the make_tape_recovery tape of either server.  I am getting the following errors on each server, can anyone shed any light on this?  Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;       * Archive extraction from tape is beginning. Please wait.&lt;BR /&gt;pax_iux: sbin/%sh : Text file busy&lt;BR /&gt;pax_iux: sbin/%pax_iux : Text file busy&lt;BR /&gt;pax_iux: tw/ : An error occurred attempting to restore the owner and group ids.&lt;BR /&gt;pax_iux: prd_basis_rpt/ : An error occurred attempting to restore the owner and.&lt;BR /&gt;pax_iux: prd_boss_dat/ : An error occurred attempting to restore the owner and .&lt;BR /&gt;pax_iux: prd_edi_arch_in/ : An error occurred attempting to restore the owner a.&lt;BR /&gt;pax_iux: prd_edi_arch_stat/ : An error occurred attempting to restore the owner.&lt;BR /&gt;pax_iux: prd_edi_log/ : An error occurred attempting to restore the owner and g.&lt;BR /&gt;pax_iux: prd_edi_rpt/ : An error occurred attempting to restore the owner and g.&lt;BR /&gt;pax_iux: prd_ics_dat/ : An error occurred attempting to restore the owner and g.&lt;BR /&gt;pax_iux: prd_rics_dat/ : An error occurred attempting to restore the owner and .&lt;BR /&gt;pax_iux: codaprod_b10/ : An error occurred attempting to restore the owner and .&lt;BR /&gt;pax_iux: prd_edi_arch/ : An error occurred attempting to restore the owner and .&lt;BR /&gt;pax_iux: edi_archive/ : An error occurred attempting to restore the owner and g.&lt;BR /&gt;pax_iux: prd_rics_gpharmon_in/ : An error occurred attempting to restore the ow.&lt;BR /&gt;pax_iux: prd_rics_cp_in/ : An error occurred attempting to restore the owner an.&lt;BR /&gt;ERROR:   Cannot load OS archive (Recovery Archive)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The directory names listed above, with the exception of sbin of course, are all nfs directories if that makes a difference.</description>
      <pubDate>Mon, 21 Apr 2008 22:19:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104793#M503388</guid>
      <dc:creator>Mike Smith_33</dc:creator>
      <dc:date>2008-04-21T22:19:35Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite errors out on multiple servers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104794#M503389</link>
      <description>Hi Mike,&lt;BR /&gt;&lt;BR /&gt;what command do you use to take the backup?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sandy</description>
      <pubDate>Tue, 22 Apr 2008 00:54:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104794#M503389</guid>
      <dc:creator>Sandy Chen</dc:creator>
      <dc:date>2008-04-22T00:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite errors out on multiple servers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104795#M503390</link>
      <description>&amp;gt; ...are all nfs directories if that makes a difference.&lt;BR /&gt; &lt;BR /&gt;Major problem: Do not under any circumstances include NFS directories in the backup. make_tape_recovery is *only* for recovering vg00. NFS makes no sense at all since there is no HP-UX yet, much less any networking during a restore. NFS is particularly fragile and should never be enabled until networking has been completed and tested (including the NFS servers). Otherwise, very annoying hangs will occur.&lt;BR /&gt; &lt;BR /&gt;Everything else is restored with frecover or Data Protector once the volume groups are created.&lt;BR /&gt; &lt;BR /&gt;The correct command for a vg00 backup (and ideal for a DR or colocation site) is:&lt;BR /&gt; &lt;BR /&gt;make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/0mn&lt;BR /&gt; &lt;BR /&gt;where 0mn is replaced with the correct tape drive name.</description>
      <pubDate>Tue, 22 Apr 2008 01:31:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104795#M503390</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2008-04-22T01:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite errors out on multiple servers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104796#M503391</link>
      <description>The command used was&lt;BR /&gt;&lt;BR /&gt;make_tape_recovery -x inc_entire=vg00 -x exclude=/etc/vx&lt;BR /&gt;&lt;BR /&gt;The only device being done is vg00.  The nfs directories just happen to reside off of the / file system.  Also, this is the same command that has been previously used to write tapes that were then recovered at our DR test facility so that has not changed.</description>
      <pubDate>Tue, 22 Apr 2008 13:10:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104796#M503391</guid>
      <dc:creator>Mike Smith_33</dc:creator>
      <dc:date>2008-04-22T13:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite errors out on multiple servers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104797#M503392</link>
      <description>The fix to this was to just perform an exit 2 when given the opportunity to drop into a shell for troubleshooting.</description>
      <pubDate>Thu, 01 May 2008 12:44:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-errors-out-on-multiple-servers/m-p/5104797#M503392</guid>
      <dc:creator>Mike Smith_33</dc:creator>
      <dc:date>2008-05-01T12:44:40Z</dc:date>
    </item>
  </channel>
</rss>

