Operating System - HP-UX
1834826 Members
2755 Online
110070 Solutions
New Discussion

Re: Ignite fails to backup diffrent version LVM volumes.

 
Nischal Tiwari
Occasional Advisor

Ignite fails to backup diffrent version LVM volumes.

Hi All,

I am getting the following error.

======= 09/21/10 14:40:52 BST Started /opt/ignite/bin/make_net_recovery. (Tue
Sep 21 14:40:52 BST 2010)
@(#)Ignite-UX Revision C.7.11.439
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA1009/ignite/src@81482 Last Modified: 2010-06-10
11:10:03 -0600 (Thu, 10 Jun 2010)


* User interface starting.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x0013215B45DE/recovery/defaults.

NOTE: '' is not an absolute path
* User interface completed successfully.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x0013215B45DE/recovery/defaults.

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/1/1/0.0x0.0x0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
013215B45DE/recovery/2010-09-21,14:40/system_cfg vg00 vg05 vg04 vg03
System is configured with one or more LVM volume groups having volume group version 2.0 or 2.1. These volume groups must eith
er be excluded from selection or converted to volume group version 2.2 using vgversion command.

Below is the list of LVM volume groups with volume group versions 2.0 or 2.1:
vg05
vg04
vg03

save_config: Error - Unable to save the hardware configuration of the system.
ERROR: /opt/ignite/bin/save_config failed


======= 09/21/10 14:43:41 BST make_net_recovery completed unsuccessfully


Ignite-UX version C.7.11.439 HP-UX System Installation Services
9 REPLIES 9
James R. Ferguson
Acclaimed Contributor

Re: Ignite fails to backup diffrent version LVM volumes.

Hi:

> System is configured with one or more LVM volume groups having volume group version 2.0 or 2.1. These volume groups must eith
er be excluded from selection or converted to volume group version 2.2 using vgversion command.

Well, that seems self-explanatory. Either convert the volume groups in question (enumerated below this message) or *better yet*, exclude them.

Best practices confine an Ignite recovery image to vg00. This allows the simplest, most straightforward system recovery and/or cloning.

Regards!

...JRF...
Torsten.
Acclaimed Contributor

Re: Ignite fails to backup diffrent version LVM volumes.

Why not follow the advise and convert the VGs?

I hope you don't want to save the content of all VGs with ignite ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Nischal Tiwari
Occasional Advisor

Re: Ignite fails to backup diffrent version LVM volumes.

I have already consider the suggestion.

$ lvmadm -l
--- Version 1.0 volume groups ---
VG Name /dev/vg00
PV Name /dev/disk/disk6_p2
/dev/disk/disk7_p2

--- Version 2.0 volume groups ---
VG Name /dev/vg05
PV Name /dev/disk/disk10

VG Name /dev/vg04
PV Name /dev/disk/disk9

VG Name /dev/vg03
PV Name /dev/disk/disk8

I canâ t convert the VG00 to version 2
Man page
Volume group versions 2.0 and higher do not support root, boot, swap, or dump. If the volume group version of vg_name is 1.0 and is configured with any of the above, the vgversion command fails the migration of such volume groups to version 2.0 or higher.

Any other way around
Torsten.
Acclaimed Contributor

Re: Ignite fails to backup diffrent version LVM volumes.

Ignite does not complain about the version 1.0 group, but about version 2.0 and 2.1 groups.


The current hp-ux 11.31 does also support layout version 2.2 for boot.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
James R. Ferguson
Acclaimed Contributor

Re: Ignite fails to backup diffrent version LVM volumes.

Hi (again):

> I have already consider the suggestion.
I can't convert the VG00 to version 2 Man page
Volume group versions 2.0 and higher do not support root, boot, swap, or dump.

So why would you want to convert vg00? For that matter, as I said, why are you trying to include non-vg00 volume groups in your Ignite?

Exclude the non-vg00 volume groups and you should be "good-to-go".

Regards!

...JRF...
Nischal Tiwari
Occasional Advisor

Re: Ignite fails to backup diffrent version LVM volumes.

I have already taken the ignite backup of the vg00 but i was trying to backup the entire system.
James R. Ferguson
Acclaimed Contributor

Re: Ignite fails to backup diffrent version LVM volumes.

Hi:

> but i was trying to backup the entire system.

Ignite is *not* a backup tool. It is designed to allow you to create an operating system image for recovery and cloning. You need to use the tool as intended. Non-vg00 volume groups and their data should be backed up independently so that they can be recovered independently.

For that matter, if you did use Ignite to backup non-vg00 volume data, you would be using a very slow, sequential recovery method to recover individual files or non-vg00 data. You need to reassess your thinking.

Regards!

...JRF...
Nischal Tiwari
Occasional Advisor

Re: Ignite fails to backup diffrent version LVM volumes.

Thanks for your views.I also know its not a backup tool.
Nischal Tiwari
Occasional Advisor

Re: Ignite fails to backup diffrent version LVM volumes.

Thanks to all.