kernel configuration at DR site

[RPC WHQ UNIX Team]

At our D.R. site, want to gen a kernel with the same parms as the production kernel. Want to run a cron job periodically to gen the current state of the kernel. What is my best bet? sysdef? /stand/system? getkinfo?

[Victor BERRIDGE]

Hi,
I would use /stand/system, but thats because Im sure /stand/system IS the one used for the current kernel, that means if you generate a kernel with sam you will have to be sure to update /stand/system...

All the best

Victor

[Steven Sim Kok Leong]

Hi,

To generate a list of current kernel parameter values, use kmtune. sysdef misses out kernel parameters such as most of the shmxxx and semxxx kernel parameters. kmtune is more reliable.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com

[James R. Ferguson]

Hi Joe:

The Ignite manifest is another good source of the very information you need during a D/R setup. For Ignite 3.2 you will find the manifest here:

/var/opt/ignite/recovery/latest/manifest

...JRF...

[Andrew Byrne]

You don't really need to cron job or document the changes. Just make a copy of the /stand/system file on the DR machine before restoring. Restore /stand/system file from tape (probably during main restore of everything else) and then cut and paste the variables section from the bottom of the restored file to the DR system file. My policy is always to leave the highest value if there are any duplicates. Once the system file looks OK, you basically have the hardware config of the new machine with the variables from the old and you can do a mk_kernel to create the kernel.