<?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-UX backup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198956#M503822</link>
    <description>The error for lvol2 doesn't surprise me since that is your primary swap space.  That will not have a file system on it, so don't worry about it.&lt;BR /&gt;&lt;BR /&gt;lvol9 is interesting.  Is that LV mounted?  What does the line in /etc/fstab look like?  What does the following command return?&lt;BR /&gt;&lt;BR /&gt;# mkfs -m /dev/vg00/lvol9&lt;BR /&gt;&lt;BR /&gt;That command will tell you exactly how the filesystem was created on that LV.&lt;BR /&gt;</description>
    <pubDate>Thu, 15 May 2008 20:25:00 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2008-05-15T20:25:00Z</dc:date>
    <item>
      <title>IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198955#M503821</link>
      <description>We have Integrity Rx4640 , HP-UX ricr3itg B.11.23 U ia64.&lt;BR /&gt;&lt;BR /&gt;In the old Ignite version (B5725AA C.6.9.141 HP-UX Installation Utilities (Ignite-UX) &lt;BR /&gt;while doing make_tape_recovery -Av we were getting the below error.&lt;BR /&gt;&lt;BR /&gt; /opt/ignite/bin/save_config -f &lt;BR /&gt;         /var/opt/ignite/recovery/2008-05-01,13:56/system_cfg vg00&lt;BR /&gt;/opt/ignite/bin/save_config[217]: 19340 Floating exception(coredump)&lt;BR /&gt;save_config: Error - cannot determine lv "/dev/vg00/lvol9" usage via fstyp&lt;BR /&gt;ERROR:   /opt/ignite/bin/save_config failed&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Then we have upgraded the Ignite version to C.7.5.142 .While doing the backup in this version by&lt;BR /&gt;&lt;BR /&gt;make_tape_recovery -x inc_entire=vg00&lt;BR /&gt;&lt;BR /&gt;we are getting the below error &lt;BR /&gt;/var/opt/ignite/recovery/2008-05-08,10:01/system_cfg vg00&lt;BR /&gt;/opt/ignite/bin/save_config[146]: 12449 Floating exception(coredump)&lt;BR /&gt;&lt;BR /&gt;Then we did fstyp on the following logical volumes.Found all retured vxfs except lvol2 and lvol9.&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&amp;gt;ls&lt;BR /&gt;group        lvol1        lvol6        lvoracle     lvsapmnt     rlvmirrlogC  rlvol4       rlvol9       rlvoriglogC&lt;BR /&gt;lvmirrlogA   lvol2        lvol7        lvoriglogA   lvstage      rlvmirrlogD  rlvol5       rlvoraITG    rlvoriglogD&lt;BR /&gt;lvmirrlogB   lvol3        lvol8        lvoriglogB   lvusrsap     rlvol1       rlvol6       rlvoracle    rlvsapmnt&lt;BR /&gt;lvmirrlogC   lvol4        lvol9        lvoriglogC   rlvmirrlogA  rlvol2       rlvol7       rlvoriglogA  rlvstage&lt;BR /&gt;lvmirrlogD   lvol5        lvoraITG     lvoriglogD   rlvmirrlogB  rlvol3       rlvol8       rlvoriglogB  rlvusrsap&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;@/sapbasis/uxcmds&amp;gt;fstyp /dev/vg00/lvol9      &lt;BR /&gt;Floating exception(coredump)&lt;BR /&gt;&lt;BR /&gt;@/sapbasis/uxcmds&amp;gt;fstyp /dev/vg00/lvol2       &lt;BR /&gt;UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;unknown_fstyp (no matches)&lt;BR /&gt;&lt;BR /&gt;What we should do? Any help will be greaty appreciated. Thanks!</description>
      <pubDate>Thu, 15 May 2008 20:04:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198955#M503821</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-15T20:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198956#M503822</link>
      <description>The error for lvol2 doesn't surprise me since that is your primary swap space.  That will not have a file system on it, so don't worry about it.&lt;BR /&gt;&lt;BR /&gt;lvol9 is interesting.  Is that LV mounted?  What does the line in /etc/fstab look like?  What does the following command return?&lt;BR /&gt;&lt;BR /&gt;# mkfs -m /dev/vg00/lvol9&lt;BR /&gt;&lt;BR /&gt;That command will tell you exactly how the filesystem was created on that LV.&lt;BR /&gt;</description>
      <pubDate>Thu, 15 May 2008 20:25:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198956#M503822</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2008-05-15T20:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198957#M503823</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I'd say the filesystem is either not mounted or corrupted.&lt;BR /&gt;&lt;BR /&gt;If it is mounted, umount it and maybe run fsck.&lt;BR /&gt;&lt;BR /&gt;If its not mounted but in fstab, mount it.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 16 May 2008 01:13:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198957#M503823</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-05-16T01:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198958#M503824</link>
      <description>Actually lvo12 and 19 are part of SWAP.&lt;BR /&gt;&lt;BR /&gt;swapinfo -tam &lt;BR /&gt;             Mb      Mb      Mb   PCT  START/      Mb&lt;BR /&gt;TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME&lt;BR /&gt;dev        4096       0    4096    0%       0       -    1  /dev/vg00/lvol2&lt;BR /&gt;dev       16000       0   16000    0%       0       -    0  /dev/vg00/lvol9&lt;BR /&gt;reserve       -   12399  -12399&lt;BR /&gt;memory    14307    6352    7955   44%&lt;BR /&gt;total     34403   18751   15652   55%       -       0    -&lt;BR /&gt;</description>
      <pubDate>Fri, 16 May 2008 12:01:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198958#M503824</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-16T12:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198959#M503825</link>
      <description>As these are part of SWAP, can I ignore the &lt;BR /&gt;"core dump" stuff while doing make_tape_recovery backup? If not, how can I fix this? Thanks for any help on this...</description>
      <pubDate>Fri, 16 May 2008 12:08:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198959#M503825</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-16T12:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198960#M503826</link>
      <description>I meant lvol2 and lvol9 are both part of SWAP...How can I fix the ignite (make_tape_recovery) backup...Thanks!</description>
      <pubDate>Fri, 16 May 2008 17:54:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198960#M503826</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-16T17:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198961#M503827</link>
      <description>As these are swap space and there are no real file system on it, can I just ignore core dump error (seems like root case is fetyp check only). Please help. Thanks!</description>
      <pubDate>Mon, 19 May 2008 11:53:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198961#M503827</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-19T11:53:30Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198962#M503828</link>
      <description>Dear all,I am looking forward to any help or suggestion on this...Thanks!</description>
      <pubDate>Mon, 19 May 2008 19:14:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198962#M503828</guid>
      <dc:creator>HPquestion</dc:creator>
      <dc:date>2008-05-19T19:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: IGNITE-UX backup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198963#M503829</link>
      <description>Refer following threads and check the patches installed on the system:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1246502" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1246502&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1173451" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1173451&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1112641" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1112641&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1109369" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1109369&lt;/A&gt;</description>
      <pubDate>Fri, 04 Jul 2008 03:07:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-ux-backup/m-p/4198963#M503829</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2008-07-04T03:07:54Z</dc:date>
    </item>
  </channel>
</rss>

