system command data relevant for DR

[derek b smith_1]

Can anyone recommened relevent system commands for DR purposes?
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.

my commands thus far are:
model
uname -a
getconf KERNEL_BITS
vgdisplay
swlist
ioscan
cstm
cat /etc/fstab..... and so on


thanks
derek

[G. Vrijhoeven · Accepted solution]

Hi Derek,

You could use the ignite command print_manifest.

cfg2html is also a usefull tool.

Regards,

Gideon

[Patrick Wallek]

I actually prefer a couple of things that gather a whole lot more data than that.

The main two that I use are:

CFG2HTML
http://come.to/cfg2html

Nickel
http://unixguide.net/cgi-bin/htsearch?words=nickel

You can also get some information from print_manifest which is included with Ignite.

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.

[Mel Burslan]

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.

[DCE]

The sysinfo tool which is referenced in multiple threads will provide you with the info you need

[Rick Garland]

The cfg2html app, the print_manifest, the nickel, machinfo (if working on ia64 systems), etc...

These will all provide the relevant info in a DR situation.

With every Ignite you make of a system, you should also make the new hard copy output with what ever command you choose.

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.

[Q4you]

To help with your DR ->

Create a directory at /DR ( assume you have adequate space in /)

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

Create an Ignite tape with -IA option.

Go to your recovery Site with this ignite tape, use it to recover your VG00. Recreat your non-vg00 from the info you captured.
If you recovering on a different model/HW config system, the info captured in /DR will be very valuable.

-Q

[Raj D.]

Hi Derek,

Here is one good tool:

http://come.to/cfg2html

./cfg2html_hpux.sh -o ~userhome/util/cfg


--=[ http://come.to/cfg2html ]=-----------------------------------------------
Starting Cfg2Html/HPUX Version 2.69 on a 9000/800/N4000-55 box
Path to Cfg2Html ./cfg2html_hpux.sh
Path to plugins /opt/cfg2html/./plugins
HTML Output Problem If cfg2html hangs on Hardware, press twice ENTER, Ctrl-D or
Crtl-\. Then check your Diagnostics (A.42++ and PHKL_29798)!
--=[ http://come.to/cfg2html ]=-----------------------------------------------
USE AT YOUR OWN RISK! (see /opt/cfg2html/./doc/cfg2html.html)
Online help: run cfg2html_hpux.sh -h for help or see ~/doc directory
--=[ http://come.to/cfg2html ]=-----------------------------------------------

Collecting: HP-UX/System .................
Collecting: Hardware ........................
Collecting: Software .......
Collecting: Filesystems, Dump- and Swapconfiguration ........
Collecting: LVM ..............
Collecting: Network Settings/Network Interface Cards .........
Collecting: Network Subsystems ..........................
Collecting: Fibre Channel .....
Collecting: Kernel ..........
Collecting: Systemenhancements ..
Collecting: Applications And Subsystems ............
Collecting: Oracle ..

--=[ http://come.to/cfg2html ]=-----------------------------------------------

Nickel script also very useful.

Cheers,
Raj.