<?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: system command data relevant for DR in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632802#M237963</link>
    <description>The sysinfo tool which is referenced in multiple threads will provide you with the info you need&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Sep 2005 15:03:53 GMT</pubDate>
    <dc:creator>DCE</dc:creator>
    <dc:date>2005-09-22T15:03:53Z</dc:date>
    <item>
      <title>system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632798#M237959</link>
      <description>Can anyone recommened relevent system commands for DR purposes?&lt;BR /&gt;Our goal is to send such data to an offsite vault and we would need pertinent system data sent to a file and then ftp'ed off.&lt;BR /&gt;&lt;BR /&gt;my commands thus far are:&lt;BR /&gt;model&lt;BR /&gt;uname -a&lt;BR /&gt;getconf KERNEL_BITS&lt;BR /&gt;vgdisplay&lt;BR /&gt;swlist&lt;BR /&gt;ioscan&lt;BR /&gt;cstm&lt;BR /&gt;cat /etc/fstab..... and so on&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;derek</description>
      <pubDate>Thu, 22 Sep 2005 14:51:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632798#M237959</guid>
      <dc:creator>derek b smith_1</dc:creator>
      <dc:date>2005-09-22T14:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632799#M237960</link>
      <description>Hi Derek,&lt;BR /&gt;&lt;BR /&gt;You could use the ignite command print_manifest.&lt;BR /&gt;&lt;BR /&gt;cfg2html is also a usefull tool.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Gideon</description>
      <pubDate>Thu, 22 Sep 2005 14:54:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632799#M237960</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2005-09-22T14:54:58Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632800#M237961</link>
      <description>I actually prefer a couple of things that gather a whole lot more data than that.&lt;BR /&gt;&lt;BR /&gt;The main two that I use are:&lt;BR /&gt;&lt;BR /&gt;CFG2HTML&lt;BR /&gt;&lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Nickel&lt;BR /&gt;&lt;A href="http://unixguide.net/cgi-bin/htsearch?words=nickel" target="_blank"&gt;http://unixguide.net/cgi-bin/htsearch?words=nickel&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can also get some information from print_manifest which is included with Ignite.&lt;BR /&gt;&lt;BR /&gt;I run CFG2HTML every week and nickel about once every 2 months or so.  I try to update the files on my laptop (which I almost always have) weekly.</description>
      <pubDate>Thu, 22 Sep 2005 14:57:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632800#M237961</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-09-22T14:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632801#M237962</link>
      <description>I have to agree with the cfg2html suggestion. If you keep that information somewhere offsite, it is all there is that you will need to rebuild a system and maybe more.</description>
      <pubDate>Thu, 22 Sep 2005 14:59:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632801#M237962</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-09-22T14:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632802#M237963</link>
      <description>The sysinfo tool which is referenced in multiple threads will provide you with the info you need&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Sep 2005 15:03:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632802#M237963</guid>
      <dc:creator>DCE</dc:creator>
      <dc:date>2005-09-22T15:03:53Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632803#M237964</link>
      <description>The cfg2html app, the print_manifest, the nickel, machinfo (if working on ia64 systems), etc...&lt;BR /&gt;&lt;BR /&gt;These will all provide the relevant info in a DR situation.&lt;BR /&gt;&lt;BR /&gt;With every Ignite you make of a system, you should also make the new hard copy output with what ever command you choose.&lt;BR /&gt;&lt;BR /&gt;Do an Ignite 1 per week, run the cfg2html once per week as well as store these 2 items together in an off-site location.</description>
      <pubDate>Thu, 22 Sep 2005 15:28:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632803#M237964</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-09-22T15:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632804#M237965</link>
      <description>To help with your DR -&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Create a directory at /DR ( assume you have adequate space in /)&lt;BR /&gt;&lt;BR /&gt;Try to capture as much info as possible in that directory, copy important system files, take print_manifest. Create mapfiles for VGs. Create output files of ioscan, lanscan, netstat, bdf, rc.log, ps -fe,  strings /etc/lvmtab, lvlnboot -v etc in that /DR&lt;BR /&gt;&lt;BR /&gt;Create an Ignite tape with -IA option. &lt;BR /&gt;&lt;BR /&gt;Go to your recovery Site with this ignite tape, use it to recover your VG00. Recreat your non-vg00 from the info you captured. &lt;BR /&gt;If you recovering on a different model/HW config system, the info captured in /DR will be very valuable. &lt;BR /&gt;&lt;BR /&gt;-Q&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Sep 2005 16:06:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632804#M237965</guid>
      <dc:creator>Q4you</dc:creator>
      <dc:date>2005-09-22T16:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: system command data relevant for DR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632805#M237966</link>
      <description>Hi Derek,&lt;BR /&gt;&lt;BR /&gt;Here is one good tool:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;./cfg2html_hpux.sh -o ~userhome/util/cfg&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;--=[ &lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt; ]=-----------------------------------------------&lt;BR /&gt;Starting          Cfg2Html/HPUX Version 2.69 on a 9000/800/N4000-55 box&lt;BR /&gt;Path to Cfg2Html  ./cfg2html_hpux.sh&lt;BR /&gt;Path to plugins   /opt/cfg2html/./plugins&lt;BR /&gt;HTML Output Problem           If cfg2html hangs on Hardware, press twice ENTER, Ctrl-D or&lt;BR /&gt;                  Crtl-\. Then check your Diagnostics (A.42++ and PHKL_29798)!&lt;BR /&gt;--=[ &lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt; ]=-----------------------------------------------&lt;BR /&gt;USE AT YOUR OWN RISK! (see /opt/cfg2html/./doc/cfg2html.html)&lt;BR /&gt;Online help: run cfg2html_hpux.sh -h for help or see ~/doc directory&lt;BR /&gt;--=[ &lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt; ]=-----------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Collecting:  HP-UX/System  .................&lt;BR /&gt;Collecting:  Hardware  ........................&lt;BR /&gt;Collecting:  Software  .......&lt;BR /&gt;Collecting:  Filesystems, Dump- and Swapconfiguration  ........&lt;BR /&gt;Collecting:  LVM  ..............&lt;BR /&gt;Collecting:  Network Settings/Network Interface Cards  .........&lt;BR /&gt;Collecting:  Network Subsystems  ..........................&lt;BR /&gt;Collecting:  Fibre Channel  .....&lt;BR /&gt;Collecting:  Kernel  ..........&lt;BR /&gt;Collecting:  Systemenhancements  ..&lt;BR /&gt;Collecting:  Applications And Subsystems  ............&lt;BR /&gt;Collecting:  Oracle  ..&lt;BR /&gt;&lt;BR /&gt;--=[ &lt;A href="http://come.to/cfg2html" target="_blank"&gt;http://come.to/cfg2html&lt;/A&gt; ]=-----------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Nickel script also very useful.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Raj.</description>
      <pubDate>Thu, 22 Sep 2005 17:34:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-data-relevant-for-dr/m-p/3632805#M237966</guid>
      <dc:creator>Raj D.</dc:creator>
      <dc:date>2005-09-22T17:34:58Z</dc:date>
    </item>
  </channel>
</rss>

