make_net_recovery

[whiz_kid911]

hello xperts

NODE-A -> Ignite Server
NODE-B -> Server Client

I want to do a make_net_recovery for NODE-B on NODE-A, which is the ignite server.

Qn:

a. What are the folders to be exported from ignite server
b. What would be the command to be executed in NODE-B to get its ignite image in NODE-A

[whiz_kid911]

AND I AM GETTING THIS ERROR NOW. I CAN SEE THAT THE DIRECTORY AND FILE CAN BE EXCLUDED BUT WHAT ABOUT A VG?

NODE-B#/opt/ignite/bin/make_net_recovery -s 10.0.6.60 -a 10.0.6.60:/var/opt/ignite/archives/qrhqsd50 -x inc_entire=/dev/vg00
* Creating NFS mount directories for configuration files.

======= 04/15/08 01:35:43 WAT Started /opt/ignite/bin/make_net_recove
Apr 15 01:35:43 WAT 2008)
@(#)Ignite-UX Revision C.7.3.144
@(#)ignite/net_recovery (opt) Revision:
/tags/IUX_RA0709w_IC312c/ignite/src@71072 Last Modified: 2007-
08:55:30 -0600 (Wed, 25 Jul 2007)

* Testing for necessary pax patch.
* Checking Versions of Recovery Tools
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client
019DEBAB3D94/recovery/2008-04-15,01:35/system_cfg vg00
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vglock".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg01".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg02".
save_config: Error - lvlnboot command returns above complaints.
ERROR: /opt/ignite/bin/save_config failed

======= 04/15/08 01:35:45 WAT make_net_recovery completed unsuccessfu
NODE-B#

[Avinash20]

######--cut--######
- Fixes for the following Change Requests:

* JAGag46613 fix. save_config, make_net_recovery, and make_tape_recovery would fail on systems that have inactive volume groups (which is typical on ServiceGuard clusters). This issue was introduced with the C.7.3.144 Ignite-UX release.
######--paste--######


Update to the latest Ignite Version
http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB