topic Re: make_net_recovery problem in Operating System - HP-UX

make_net_recovery problem

钱飞 — Sat, 15 Mar 2008 00:59:08 GMT

Hi,
I am using Ignite server to make_net_recovey a 11.23 machine.But when saving the system configuration,errors appear show that there are some VG not activated.However it is a alternate NODE in a failover cluster,and I only include the vg00.
Can anyone help me?

Re: make_net_recovery problem

Mridul Shrivastava — Sat, 15 Mar 2008 01:03:59 GMT

Hi,

I understand those would be warnings, not errors. And those warnings can be ignored since they are for non-root vg.

make_net_recovery is used to take OS backup i.e. vg00 which includes root, stand, var, opt, var, /var/adm/crash etc.

These warning appears always and If you don't want to see those warning execute tha backup by specifying -P s option.

I see that you are new to this forum so welcome to the forum communitiy and njoy foruming ;)

Do remember to assign points so the person replying gets the credit.

Regards,

Mridul

Re: make_net_recovery problem

钱飞 — Sat, 15 Mar 2008 01:49:21 GMT

Hi Mridul,
Thank you for your reply.
I specified only include vg00,but from the log it will check the output of lvlnboot -v when saving the system configeration,which I think cause the error.
And it's not warning message,it unsuccessfully completed.

below is the log:
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vgsap".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vgdata".
save_config: Error - lvlnboot command returns above complaints.
ERROR: /opt/ignite/bin/save_config failed

Regards,

Fei

Re: make_net_recovery problem

Mridul Shrivastava — Sat, 15 Mar 2008 01:59:14 GMT

What's the ignite version release on the system ?

The vglock LVM volume group contains logical volumes, and is in fact inactive. Previously Ignite-UX used to just print a warning about inactive volume groups.

For C.7.3.X, the save_config script was modified to prevent cases where the lvnlboot command encountered an error, but still returned a return code of 0. Unfortunately, these modifications resulted in the undesirable behavior you're seeing now. They have already fixed the issue in C.7.3.148.

Here an excerpt from the Release Notes:

######--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--######

Go on upgrade to C.7.3.148.

Re: make_net_recovery problem

钱飞 — Sat, 15 Mar 2008 02:47:17 GMT

Thank Mridul's answer.

Re: make_net_recovery problem

UVA — Thu, 11 Sep 2008 11:02:05 GMT

Hi,

Thx to all, the same has helped me too.